Feedback on trailingSlash option + GH Pages about trailing-slash-guide HOT 4 CLOSED

from trailing-slash-guide.

Hi!

This project is not directly related to Docusaurus so can you re-open this issue on Docusaurus instead?

I'll look at this on Monday anyway
It makes me think about another issue opened recently (facebook/docusaurus#5055)

├── react-native-render-html.html

I don't understand, Docusaurus does not create an index.html file anymore in beta.2, while it did before?

Can you deploy your site with the bug somewhere (a fork?), so that I can see the live site + have the ability to inspect the gh-branch?

Ideally, the sitemap generated for gh-pages would add a trailing slash to the root URL to avoid redirects, or there could be an option to deal with the root.

I don't think, we don't want to hardcode special cases per host.

GH pages should be able to serve files without needing/redirecting a trailing slash, cf https://slorber.github.io/trailing-slash-guide/file

from trailing-slash-guide.

@slorber All right, I'll try to make a reproduction and file a report. I didn't report on Docusaurus because I wasn't sure it's really a bug...

I don't think, we don't want to hardcode special cases per host.

Sure hardcoding is bad, however there could be an actionable solution for all those who're using GH pages and don't want to suffer from degraded SEO. Perhaps trailingSlash: 'root' meaning, one trailing slash is expected for the top level route, no trailing slash for other routes. That would match per-repository GH Pages deployments.

from trailing-slash-guide.

Closing in favor of facebook/docusaurus#5077

from trailing-slash-guide.