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.

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

Research possible framework replacements for Gatsby #585

Open
4 tasks
travjenkins opened this issue Dec 4, 2024 · 0 comments
Open
4 tasks

Research possible framework replacements for Gatsby #585

travjenkins opened this issue Dec 4, 2024 · 0 comments
Labels
ongoing Work that is happening over a longer period of time / side effects of other work. tech debt This is a task that really only the engineers notice

Comments

@travjenkins
Copy link
Member

travjenkins commented Dec 4, 2024

Description

There are some issues we have with Gatsby and it seems like it is not getting as much support/attention these days. Would like to look into replacing this with a more active project.

Two main ideas are standing out right now - Next.JS or React Router

We should view this comparison as "Should we use React Router instead of Next?" and not "Should we use Next or React Router?"

Work required

  • Research on migrating to Next.JS
  • Research on migrating to React Router
  • Shootout on the two
  • Document a list of what we want to accomplish with new framework. Build time, performance, security, etc.

Thoughts

Things to think about

@travjenkins travjenkins added tech debt This is a task that really only the engineers notice ongoing Work that is happening over a longer period of time / side effects of other work. labels Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ongoing Work that is happening over a longer period of time / side effects of other work. tech debt This is a task that really only the engineers notice
Projects
None yet
Development

No branches or pull requests

1 participant