Polish Aliki documentation theme#1742
Open
st0012 wants to merge 11 commits into
Open
Conversation
Document Aliki's visual design language as a single source of truth for the css/rdoc.css stylesheet, in the Stitch DESIGN.md nine-section format: theme/atmosphere, color palette and roles (light + dark), typography, component stylings, layout, depth/elevation, do's and don'ts, responsive behavior, and an agent quick reference. Visual scope only; all token and component values are transcribed from css/rdoc.css.
st0012
requested a deployment
to
fork-preview-protection
GitHub Actions
Waiting
Collaborator
|
🚀 Preview deployment available at: https://f2e71367.rdoc-6cd.pages.dev (commit: cd2b3a1) |
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.
Problem
The Aliki HTML theme has several small visual inconsistencies that add up when browsing generated documentation: method cards and source toggles compete for attention, selected and nested navigation states create uneven spacing, page titles do not clearly distinguish object kind from object name, section dividers are visually heavy, the footer can sit awkwardly against the sidebar at narrower desktop widths, and the desktop search field is not aligned with the main reading column.
These issues make the default generated docs feel less polished than the underlying content warrants, especially on method-heavy pages and wide layouts with both side navigation and the table of contents visible.
Solution
Screenshots
Before
After