Conversation
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
Description
Prototype the docs site with Trident tokens while keeping builds independent of the internal npm registry. Vendors the generated CSS from
@docker/trident-tokens@2.0.0-beta.3, adds locally served Manrope fonts, and maps the existing header, navigation, article typography, cards, buttons, tabs, and callouts to semantic tokens in light and dark mode.Article text uses Trident's primary foreground on a white light-mode reading surface and a dark reading surface that matches the sidebar. Subtle dividers separate navigation, inactive table-of-contents links are neutral, and inline code has quieter backgrounds and compact padding. Long inline paths wrap on mobile. The neutral header is a docs-specific adaptation of Trident's blue-gradient AppHeader; its logo remains visible after production minification. Trident's separate high-contrast mode stays inactive.
Home, Get started, Guides featured cards, and Manuals use one shared navigation-card partial, with page-specific grids and optional audience labels. Guides search results remain list rows. Navigation cards use compact 16px titles, 14px supporting descriptions, Trident's paper elevation 0 surface, and full-area links. Card borders and shadows follow Trident's surface material: a semantic border in both themes, a faint inset top-edge highlight in dark mode, and no visible shadow in light mode. Mixed decorative icons are removed so destinations share a consistent text layout. Tabs retain defined component surfaces, semantic borders, and hover/focus states. Article and Gordon code share Trident syntax roles, with theme-specific code surfaces. Gordon uses the header gradient and semantic input, message, feedback, and alert colors. Pagefind uses the same typeface, modal surface, result text, highlights, and focus colors.
The homepage uses a unified Trident canvas for the Gordon form, suggested questions, navigation cards, and release feed. The decorative background and scaling effects are removed, the input has an accessible label and submit button, and the cards and feed align to one content width. Existing Gordon question submission and release expansion behavior are preserved.
Includes snapshot checksums, a maintainer update script, and integration notes. This is a draft for visual review; components outside the documented mappings remain open for review.
The minified production Hugo build and scoped lint checks pass. Browser checks covered light/dark desktop and mobile layouts, tab switching, keyboard focus, homepage question/suggestion submission and release expansion, real Pagefind results, and Gordon message/code/rate-limit rendering. The six mapped syntax color roles exceed 4.5:1 on their code surfaces in both themes. Local Pagefind indexing fails with a native allocator error, so local browser checks used the deployed preview's index. Gordon responses were intercepted test data; live backend behavior was not tested.
Preview
Once Netlify finishes deploying:
Generated by Codex