You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Summary
Currently, the complete react-blog-github is being rendered client side which results in low performance and no SEO.
My plan is to move the complete project to Static Site Generation in a short move the client side to a static site. We might have problems with rendering real-time comments
We can also move to Gatsby but I am not sure about the support currently I have built two projects next and it's a lot more stable.
What's new?
We will be moving to static sites nothing would change in jsx. The API call to GitHub for GitHub issues and other things might change. This would be a pretty big change and I am not sure how we would do it without affecting our current code. We will keep building a new version of it moving one piece one by one and then when it's done we will make it live.
Motivation
First, static sites are much faster and more performant than client-side rendered applications. This is because the content is pre-rendered and served directly from the server, rather than being generated on the client side. This means that the pages will load much faster for users, which is especially important for a project like developerFolio which may be used by developers for their portfolios.
Second, static sites are more secure than client-side rendered applications. Since the content is pre-rendered, there is no risk of user input being injected into the page and potentially causing security vulnerabilities. This is an important consideration for any open-source project that may have a large user base.
Overall, moving react-blog-github to a static site using Next.js would likely provide numerous benefits for users
The text was updated successfully, but these errors were encountered:
@GroovierHen Would you like to compare Nextjs and Astro and what do you think would be perfect for our usecase. We wanna fetch the issue from the GitHub and also include comments in realtime
Summary
Currently, the complete react-blog-github is being rendered client side which results in low performance and no SEO.
My plan is to move the complete project to Static Site Generation in a short move the client side to a static site. We might have problems with rendering real-time comments
I have NextJs in mind with ISR.
We can also move to Gatsby but I am not sure about the support currently I have built two projects next and it's a lot more stable.
What's new?
We will be moving to static sites nothing would change in jsx. The API call to GitHub for GitHub issues and other things might change. This would be a pretty big change and I am not sure how we would do it without affecting our current code. We will keep building a new version of it moving one piece one by one and then when it's done we will make it live.
Motivation
First, static sites are much faster and more performant than client-side rendered applications. This is because the content is pre-rendered and served directly from the server, rather than being generated on the client side. This means that the pages will load much faster for users, which is especially important for a project like developerFolio which may be used by developers for their portfolios.
Second, static sites are more secure than client-side rendered applications. Since the content is pre-rendered, there is no risk of user input being injected into the page and potentially causing security vulnerabilities. This is an important consideration for any open-source project that may have a large user base.
Overall, moving react-blog-github to a static site using Next.js would likely provide numerous benefits for users
The text was updated successfully, but these errors were encountered: