-
Notifications
You must be signed in to change notification settings - Fork 452
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
Migration to Next.js #307
Comments
Hey bro, it's sounds pretty good~😊 |
Is this project still alive I can help you guys on migrating to nextjs |
Hey @AugustinMauroy , I'm a little curious about this issue and wanted to check if there has been any progress or if any initial steps have been taken to address it. I have a suggestion that could take the project to the next level. Have you considered using a framework like Next.js, similar to Docasaurus? It's incredibly user-friendly, and practical, and can provide a lot of helpful features. I'd love to hear your thoughts on this idea. Let me know what you think! |
|
Oh, okay. I believe it’s quite simple. Docusaurus is flexible in terms of implementing small documentation like we have on the first-contribution repository. It also has features for implementing blogs and we can make a separate page for listing projects. On top of that, it makes things even easier with GitHub integration for CI/CD, unit testing, and more. From my experience, I find it easy to use because you don’t have to worry about handling routing. They’ve made it simple to manage. And I think for this repository, it’s enough. In terms of infrastructure, we can even make smaller fragments of docs to manage each file, which makes life easier for maintainers and reviewers. And even Docusaursdoes does provide a solution for i18n. This is my thought and suggestion. However, 😊 I am open to further discussion and welcome any ideas. |
This app loads data about projects from a json file and renders it. What does it need Typescript and SASS support for? What architectural problem is fixed by using Nextjs?
How does this statement apply to this app? |
hey !
In general Nextjs app is more easy to maintain than CRA. Also use nextjs increase DX. And simplify coding. So it's allow more poeple to contribue. Other point, we can i18n website esalier. to continue we will have an better SEO |
Not in general, specific to this project. When you have a hammer, everything might look like a nail. We should be wise to use right tools for respective scenarios. I like Nextjs a lot. For the last 3 years, I have preferred it over CRA.
This is a generic statement that can be said about a lot of things. Like for Docker or Kubernetes Do the benefits of such a refactor justify the effort of people doing it? Maintainers reviewing the changes? |
This comment was marked as outdated.
This comment was marked as outdated.
Doesn't answer any of the questions @AugustinMauroy. Question is not if we can do it. It's if we should do it |
Yeah I'm 100% sure.
As I said above, I think so. Thanks to nextjs lots of possibilities are opening up. Like i18n, several pages that give advice (which would be written in markdown/mdx) |
🐞 Problem
Simple CRA it's difficult to maintain.
🎯 Goal
Add this feat:
📋 Steps to solve the problem
The text was updated successfully, but these errors were encountered: