Draft
Conversation
Member
|
My immediate gut feeling is that it's too nested. Why is there a user manual index under a user manual heading? Why can't all of the contents be elevated up so it's all directly under the user manual heading? At the same time, too much information all at once can be problematic, but I wonder if this also hurts discoverability. |
Member
Author
Contributor
|
I think the headings should match the paths to be consistent unless its something that should be called out separate. |
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.

initial restructure according to documentation template: https://docs.google.com/document/d/1hfguBWJAnKySKMACouyjNGWFuWJTAfZ_YTXg_Djp714/edit?tab=t.0
I marked this as a draft pull request because it is no where near ready to merge. I just wanted to get something on paper to hopefully stir "criticism"