Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Migration to Next.js

See original GitHub issue

Hello everyone,

We’re migrating the site from Metalsmith to Next.js.

Before this goes live, we would like to get your feedback.

What problems are we solving with this release?

Removes technical debt since Metalsmith is no longer maintained
Moves the install instructions from the site to theme each repository (see example)
Moves the screenshots from the site to each theme repository (see example)
Fixes the fetching of GitHub contributors which was broken after the WeDeploy shutdown

What problems are we not solving with this release?

The overall design has not been updated
The landing page is not dinamically generated
The theme icons and colors are still manually defined

Want to see for yourself?

Clone the 3.x branch and follow the instructions on the README.

If you’re curious, you can see the full commit here: https://github.com/dracula/dracula.github.io/commit/46c42a7f46ae35684ed9e835e36a7c7108715d6c

@dracula/maintainers

Issue Analytics

State:
Created 4 years ago
Reactions:4
Comments:10 (10 by maintainers)

Top GitHub Comments

2reactions

oswaldoacauancommented, Dec 26, 2019

GitHub Actions to trigger a rebuild/deploy each time a PR is merged? 🙃

On Thu 26. Dec 2019 at 19:18, Zeno Rocha notifications@github.com wrote:

What I meant is that every theme page is dynamically generated (see [theme.js]) and the landing page is hard-coded with each theme link.

In terms of the instructions being fetched from the repo, we would still need to go through a process of updating the site 😕

The GitHub API has a limit of requests (5000 per hour) and to avoid hitting this limit we would have the site static exported on build time.

— You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub https://github.com/dracula/dracula.github.io/issues/96?email_source=notifications&email_token=AAJVWJRJC5VPLTXN6MWUHH3Q2TYONA5CNFSM4J7LOILKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHV6G6Q#issuecomment-569107322, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJVWJS6OLPPA6R3PMKM6V3Q2TYONANCNFSM4J7LOILA .

1reaction

zenorochacommented, Jan 2, 2020

Ohh, I see that it was merged 3 hours ago, so let me clarify.

The screenshots are always fetched directly from the master branch, so regardless of deploying a new version of the site or not, it will always be the latest.

https://github.com/dracula/dracula.github.io/blob/site/pages/[theme].js#L42

Only the contributor list and the install instructions will depend on a new deployment of the site.

Top Results From Across the Web

Migrating from Create React App - Next.js

If you want to move your existing Create React App to Next.js and keep a Single-Page App, you can move your old application's...

Migrating to Next.js: Incrementally Adopting Next.js

The second strategy is to create a new Next.js app that points to the root URL of your domain. Then, you can use...

Next.js 13 Upgrade Guide

Migrating from pages to app · Step 1: Creating the app directory · Step 2: Creating a Root Layout · Step 3: Migrating...

Migrating from React Router - Next.js

Migrating from React Router ; Decrease bundle size by removing React Router as a dependency. Define your application routes through the file system....

Migrating from Gatsby - Next.js

Let's walk through a series of steps to complete the migration. ... The first step towards migrating to Next.js is to update package.json...