Refactor Asciidoc documentation and remove Markdown #78
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
markspolakovs
approved these changes
Nov 10, 2021
Co-authored-by: Marks Polakovs <[email protected]>
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.
Switching now to all user documentation must be in Asciidoc. Dev documentation still in Markdown as not part of the CMOS generation.
Refactored current auto-generated documentation to split it up into more appropriate pages - still some work to do for duplication and updates of examples/config.
Image links work in the generated HTML, Github rendering seems to not support an Antora folder structure, e.g. asciidoctor/asciidoctor-vscode#230
Landing page for repo is simplified now just to reference to the Asciidoc pages.