Closed lettertwo closed 5 years ago
Seems our generated docz site is all client-side routing, which in retrospect, i guess should have been obvious.
For example: going to https://hz-core.netlify.com and clicking on PageGesture takes you to https://hz-core.netlify.com/page-gesture, which works while routing in the client, but 404s on refresh or direct link.
I think we have two options here:
Since Netlify is tuned for static sites, I think the second option might be better, but the first option might be faster.
Fixed in https://github.com/hzdg/hz-core/pull/21. And verified on production
Seems our generated docz site is all client-side routing, which in retrospect, i guess should have been obvious.
For example: going to https://hz-core.netlify.com and clicking on PageGesture takes you to https://hz-core.netlify.com/page-gesture, which works while routing in the client, but 404s on refresh or direct link.
I think we have two options here:
Since Netlify is tuned for static sites, I think the second option might be better, but the first option might be faster.