feat: canonicals(7.18) -- correctly fix sitemap & apply rel=canonical strategy to 7.18 branch #1345
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Merging this sans feedback so we can get it out there, but happy to come back and address any. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Part of https://github.com/camunda/product-hub/issues/232.
This is a second attempt at #1336.
link rel=canonicalcamunda-docs-theme#33canonicalBasePathconfig setting for proper sitemap & rel=canonical generationProof that the sitemap gets generated with absolute URLs
I ran a build locally and this is the generated sitemap:
Proof that pages are generated with a versionless rel=canonical
I ran a build locally and this is the generated page for
/manual/7.18/user-guide/security/: