doc: remove duplicate /microcloud in URL path#1335
Draft
minaelee wants to merge 1 commit intocanonical:mainfrom
Draft
doc: remove duplicate /microcloud in URL path#1335minaelee wants to merge 1 commit intocanonical:mainfrom
minaelee wants to merge 1 commit intocanonical:mainfrom
Conversation
Signed-off-by: Minae Lee <minae.lee@canonical.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR updates the path for the MicroCloud part of the integrated docs so that the second duplicate /microcloud is removed from the docs path. For example:
https://documentation.ubuntu.com/microcloud/latest/microcloud/reference/
becomes
https://documentation.ubuntu.com/microcloud/latest/reference
Per request from the Web team before we can migrate MicroCloud docs to canonical.com/microcloud/docs.
Note: A RTD redirect (not in Sphinx configuration but in RTD settings) needs to be put in place at the same time this update is merged, and again when the update is backported to the v2-edge branch. I will set up the redirects in RTD and disable it for now, so that it's easy to enable them at merge time.
Checklist