Add a deeper, auto generated ToC for easier, faster navigation #155
+142
−12
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
…uto gen via https://atom.io/packages/atom-mdtoc). Signed-off-by: Sam Pinkus <sgpinkus@gmail.com>
|
Potentially conflicts with #147 |
|
Would be nice we get a script/automation to generate this ToC |
|
If we consider GitHub-produced pages, then ToC is already generated from the content (see https://compose-spec.github.io/compose-spec/spec.html). |
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.
What this PR does / why we need it:
Add a deeper auto generated ToC to spec. It's very much needed for such a large spec IMO: faster navigation, and as a good general overview of what's in the spec.
I auto generated this with Atom editor. Can use this is or use preferred auto generator next time you have to update.
Which issue(s) this PR fixes:
No open issue.