[POC] Inline external #92
Closed
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
|
@booxter fyi |
|
I am now not sure inlining would be helpful. It would mean that we need to inline complete examples into docs. The examples may be quite long and loose the right focus on specific field described in a particular place of the document. |
|
That's true - good perspective on the matter. Well - maybe they can extend each other: Shortened snippets (extensive use of ellipsis) and links to working exampples (which live in the kubevirt repo). But this means that this issue is not needed. |
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 is an example how an external file can be inlined:
Can be previewed here:
https://fabiand.github.io/user-guide/#/workloads/virtual-machines/README
Described here:
https://docsify.js.org/#/embed-files
Relates to #91 (comment)