Closed
Conversation
Contributor
|
Hey @cjcenizal , cool for the trial. For me, having one giant file is not a good solution, both for the reader and the DX, but I was going to suggest it to @snide when integrating. We should keep small, scoped files that are much easier to handle, reason about and review. |
This file contains hidden or 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
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.
Direct conversion of content added via #78654 to a format compatible with our new docs system.
@sebelga I created this just to try it out. Pinging you in case you wanted to give the new docs system a whirl, so that we don't duplicate effort. Note that I had to massage the headings significantly, which was fairly tedious grepping.
This can be added to a locally running version of the docs site by adding it as a source:
And then creating a new nav file and adding it to
nav.ts:Here's what it looks like: