Repository navigation
Improve Topic sidebar with Quiet hierarchy - #131
Merged
Merged
Conversation
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.
Long nested Topic titles are hard to scan when roots, branches, and leaves have similar weight. Apply the accepted Quiet hierarchy design with a slightly wider sidebar, shallower indentation, clearer type weights, and a restrained current-row highlight. Compact three-column gaps preserve the existing dense-content width guarantee.
Closes #130.
Only the three sidebar presentation files and the corresponding visual-design documentation are included. JavaScript/RxJS topics and all other pending local changes remain separate.
Verification
npm run checkwas attempted; Firefox stalled at browser startup after the other projects completed. A separate clean run of the three available browser projects passes. Full unmodified GitHub Actions, including Firefox, must pass before merge.Review and acceptance
AI-assisted implementation, verification, and deliberate review of the complete four-file diff. No independent agent review was used for this bounded presentation change. Gabriel selected and approved the rendered design and explicitly delegated issue/PR delivery and merge after successful checks.