Distrobuilder docs #697
Merged
Distrobuilder docs #697
Conversation
This file contains 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
|
@ru-fu can you rebase the branch? I believe I fixed the other GH actions issues. |
Signed-off-by: Ruth Fuchss <ruth.fuchss@canonical.com>
Move the pages into a Diataxis structure and add a documentation start page. Signed-off-by: Ruth Fuchss <ruth.fuchss@canonical.com>
Signed-off-by: Ruth Fuchss <ruth.fuchss@canonical.com>
Signed-off-by: Ruth Fuchss <ruth.fuchss@canonical.com>
Signed-off-by: Ruth Fuchss <ruth.fuchss@canonical.com>
ru-fu
force-pushed
the
LXD-298-distrobuilder-docs
branch
from
b3ad665
to
4a4a8d2
Compare
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.
This PR adds a standard Sphinx setup for the docs and organises the pages in a basic Diataxis structure.
No content changes to the docs except for the text on the index page, plus some very minor changes when moving content to different files.
After merging this PR, we need to set up the docs preview and publishing (same as for the LXD docs), update the links to the documentation output, and retire the docs on readthedocs.io.