-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
React Rewrite #40
React Rewrite #40
Conversation
Closes #42 |
Got busy and didn't finish this, but I also have some un-pushed changes locally (lockpick is almost done). I'll work on this in the upcoming days, probably. |
I've published my fork to vercel, and it is currently deployed from the |
That is great. Do you think it is beneficial to transition over to Vercel compared to Github Pages in general? |
@MaximilianAdF Yeah, I'd say so. Next.js is created by vercel, so their platform is totally optimized for it. Additionally, the free plan includes edge network, so some server-side JS code can run. A couple other things:
|
@BobDotCom I will merge this pull request |
@MaximilianAdF I'll take a look at it, and I also added/messaged you on discord. I'll send you some other info on the configuration though there. |
React Rewrite
Discussed in #38, this PR rewrites the site in react.
I chose Next.js because it's a very well known framework for react with a lot of nice features. Additionally, it's used on countless websites for major companies including Netflix, TikTok, Twitch, Hulu, Notion, Target, etc. (Next.js Showcase)
I also used tailwind CSS, another extremely widely used framework featured on the websites of ChatGPT / OpenAI, Netflix, and even NASA. (Tailwind CSS Showcase)
Currently, upon creating this PR, I only implemented the index page. The other pages are currently served through Next.js as static files, so they still work as previously but haven't been migrated yet.
For development instructions, see
README-nextjs.md
.TODO
Before/After
Index
Repair Kit