spa-github-pages VS create-react-doc

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.

After the above analysis of the SSG scheme, at this time the key to optimization of the SPA site is already on paper —— static routing. Compared with frameworks such as nuxt and Gatsby, which have the limitation of conventional routing, create-react-doc has flexible and free organization in the directory structure. Its website building concept is File is Site, and it is also very convenient to migrate existing markdown documents.