Split documentation into two categories #33
Merged
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
Signed-off-by: Guillaume Fontorbe <[email protected]>
gfontorbe
temporarily deployed
to
pull-request-preview
GitHub Actions
Inactive
|
jbicker
reviewed
Feb 13, 2024
There was a problem hiding this comment.
User Interaction - Creating Custom Interaction should be part of the documentation not the reference.
Signed-off-by: Guillaume Fontorbe <[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.
Splits the documentation into a "Documentation" and "Reference" section.
The documentation part consist mainly of "how to" documents while the "reference" section is more API focused.
Adds a yaml file to deal with the order of documentation files (remove the needs of using
weightmetadata in each markdown file)