spa-github-pages VS Gatsby

I tried adding a 404.html file to my public dir in the client and then changing the index.html file with the additions here: https://github.com/rafgraph/spa-github-pages

just follow this guide its a 10 min fix https://github.com/rafgraph/spa-github-pages

There actually is a way to do it, I just haven’t played around with it enough to get it to work.

Last night before posting this, I tried following this solution (which is very similar to yours) but couldn't get it to work.

This is possibly a react router issue. I recently had the same problem where my Header showed but everything else in the routing was blank. This helped solve my problem using GitHub pages. https://github.com/rafgraph/spa-github-pages You can also just Google “react router blank page after hosting” and you might find some useful resources.

Now there's no bash script, all commands are using trunk hooks. and rewrite all readme. also i add 404.html to use router.

Try this https://github.com/rafgraph/spa-github-pages "Basic instructions" part should be enough

But unfortunately, in 2019 Google adjusted crawler algorithm, so this kind of redirection scheme is not conducive to SEO at the moment. The author of spa-github-pages also stated that if SEO is required, use the SSG plan or the paid plan Netlify.

A Gatsby site uses Gatsby, which leverages React and GraphQL to create fast and optimized web experiences. Gatsby is often used for building static websites, progressive web apps (PWAs), and even full-blown dynamic web applications.

While Next.js is a powerful framework for building server-rendered React applications, it's not the only option for developers looking to create high-performance websites. One notable alternative is Gatsby, a static site generator that leverages React and GraphQL.

The other piece of important information to acknowledge here is that when we say RSCs need a framework, “framework” effectively just means “Next.js.” There are some smaller frameworks (like Waku) that support RSCs. There are also some larger and more established frameworks (like Redwood) that have plans to support RSCs or (like Gatsby) only support RSCs in beta. We will likely see this change once we get React 19 and RSCs are part of the Stable version. However, for now, Next.js is currently the only framework recommended in the official React docs that supports server components.

GatsbyjsCMS - Gatsby is the fast and flexible framework that makes building websites with any CMS, API, or database fun again. Build and deploy headless websites that drive more traffic, convert better, and earn more revenue!

GatsbyJS

Babel plugins are everywhere. From being used to remove unwanted exports from files in Gatsby to being used to disallow users from doing re-exports in Nextjs.

In terms of GitHub stars, SSGs like Next.js, Hugo, Gatsby, Docusaurus, Nuxt.js, and Jekyll top the list. Some popular SSGs even host conferences and workshops, providing resources and networking opportunities for those looking to explore more advanced topics in depth.

Flexibility : Developers have complete control over the frontend so they can use their preferred tools and frameworks like React, Next.js, Gatsby, or Remix.

Both Chakra UI and Shadcn supports reusable components and can be used with different frameworks like React, Gatsby, Next etc.