docs: set trailingSlash: false
to fix refresh issues on GitHub pages
#14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue number of the reported bug or feature request: #13
Describe your changes
It's said (and as I tested) that if GitHub Pages detects that the URL points to a directory on the server, it will add a trailing slash to the URL when refreshing.
https://stackoverflow.com/a/33271505/2302258
Per Docusaurus's default configuration,
docs/getting-started/overview.mdx
would emitdocs/getting-started/overview/index.html
, therefore GitHub Pages would takedocs/getting-started/overview/
as the canonical URL.However, the relative links in the document are not touched by default, so
./alternatives
remains./alternatives
, which isdocs/getting-started/alternatives
on the original web page, anddocs/getting-started/overview/alternatives
after refreshing. The latter would lead to a 404 page.To fix this, we have to enforce a
trailingSlash
style.trailingSlash: true
requires fixing quite a few links across the docs, so I chosetrailingSlash: false
to keep as many links untouched as possible.