feat(website): docs chrome polish (sidebar marks, page header, prev/next)#573
Open
blove wants to merge 8 commits into
Open
feat(website): docs chrome polish (sidebar marks, page header, prev/next)#573blove wants to merge 8 commits into
blove wants to merge 8 commits into
Conversation
Carry the landing's visual language into the docs reading chrome via a shared LibraryMark: sidebar switcher marks + nav cleanup (background-only active/hover, no left bar), a branded page header with a reserved actions slot, and hover-lift prev/next cards. First of two specs; the LLM markdown export lands separately. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Inline color/background on the links beat the scoped :hover rule (inline styles win over stylesheet selectors). Move resting + active + hover states fully into the scoped stylesheet so the cascade governs hover. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
Summary
Carry the branded landing visual language into the docs reading chrome (first of two specs; the LLM markdown export lands separately):
LibraryMark— one shared component mapping all 7 libraries to a logo chip (langgraph/ag-ui/a2ui/render →/logos/*.svg) or an in-house glyph chip (chat/licensing/telemetry).DocsPageHeaderwith the library mark + a monoLIBRARY · SECTIONeyebrow above the existing MDX title (no duplication), with a reserved right-side actions slot for the upcoming per-page LLM actions.← PREVIOUS/NEXT →direction labels.Includes a follow-up fix: the sidebar nav-link hover was initially defeated by inline-style precedence; resting/active/hover are now all driven by the scoped stylesheet so hover actually applies (verified in-browser).
Spec:
docs/superpowers/specs/2026-06-04-docs-chrome-polish-design.mdPlan:
docs/superpowers/plans/2026-06-04-docs-chrome-polish.mdKnown follow-up (spawned separately)
Cardsetsborder/box-shadowinline, so thedata-ui="docs-card"hover only appliestranslateY(the accent border + elevated shadow don't render) — affects both the landing fork cards and these prev/next cards. To be fixed at theCardlevel, with the duplicateddocs-card<style>blocks consolidated.Test Plan
LibraryMark.spec.tsx— 3/3e2e/docs.spec.ts— 8/8 (sidebar mark, page-header eyebrow, prev/next direction)eslinton changed files — clean🤖 Generated with Claude Code