Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[discussion] Switch to next.js #96

Open
jasonLaster opened this issue Mar 9, 2020 · 0 comments
Open

[discussion] Switch to next.js #96

jasonLaster opened this issue Mar 9, 2020 · 0 comments
Labels
dev Related to developing, building, depoying the site P2 Should be fixed, time and resource permitting.

Comments

@jasonLaster
Copy link
Collaborator

Gatsby offers us a lot, but with next.js release today, it is now possible to consider the move.

Let's treat this issue as a discussion of the merits and technical requirements. We can discuss scope and planning offline. although, i definitely think the redesign and client side search efforts take priority in the short term.
@bloudermilk bloudermilk added the dev Related to developing, building, depoying the site label Mar 28, 2020
@bloudermilk bloudermilk added the P2 Should be fixed, time and resource permitting. label May 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
dev Related to developing, building, depoying the site P2 Should be fixed, time and resource permitting.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bloudermilk @jasonLaster