Open 0ME9A opened 10 months ago
How is this going @0ME9A I don't see a branch for this if you want I can give it a go
Hi @DavidKozdra,
I know you've been eagerly awaiting the new website for the Password. I've made significant progress, but due to personal reasons, I've had to put it on hold. Rest assured, I aim to deploy the new site this month. Thank you for your enthusiasm!
I totally understand work has been alot so I have not been able to do enough either, I use this app to generate all my passwords so I can't wait, lmk if there is anything else I can help with
Thanks for understanding! I really appreciate your patience and support. I'll definitely let you know if I need any assistance. Looking forward to getting the new site up and running soon!
Description: As the maintainer of the Password website, I propose upgrading our current implementation from Pure React to Next.js. Here are the reasons behind this proposal:
Improved SEO: Next.js provides built-in support for server-side rendering (SSR), which can enhance search engine optimization (SEO) by delivering fully-rendered HTML pages to crawlers.
Enhanced Performance: Next.js optimizes the performance of web applications through features like automatic code splitting and pre-fetching. This can lead to faster page loads and a better user experience.
Simplified Routing: Next.js simplifies the routing process with its file-system-based routing system, making it easier to organize and manage routes.
Static Site Generation (SSG): Next.js supports static site generation, allowing us to pre-render pages at build time. This can further improve performance and reduce the load on servers.
Community and Ecosystem: Next.js has a vibrant community and a rich ecosystem of plugins and tools that can benefit the development and maintenance of our Password website.
Steps to Upgrade:
Additional Notes: Please feel free to share your thoughts and feedback on this proposal. If there are specific concerns or considerations, let's discuss them collaboratively.
References: