Repository navigation
🎨 Bring the dyno brand to the docs site - #36
Merged
Merged
Conversation
The docs now share the reporter's look through one brand.css: tokens as light-dark() pairs, the wordmark, roller, tach, and dyno sheet. The homepage hero draws an example pull that you can run again to see the ghost of the last one, the wordmark roller turns as you scroll, the current page sits on a roller in the sidebar, and the 404 shows a tach that never left zero. The reporter, control room, and saved reports load the same brand.css, so the palette lives in one place.
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.
The reporter got its dyno brand in #34, and now the docs site matches. Same cell, same instruments, a bit more room to play.
What changed
12 tests @ 2.39 s. It uses the realdyno-chart.js, so it's the same sheet you see in the reporter. The flat stretch is one slow import test.One brand, one file
The /simplify pass caught that the docs had copied the reporter's palette and instrument CSS. That's now a shared
src/browser/brand.css:light-dark()pairs. Each page picks a theme withcolor-scheme: the reporter follows the system, the control room stays dark, and the docs follow Starlight's theme toggle. The palette lives in exactly one place.brand.css. It holds the wordmark, roller, tach, sheet, sheet notes, and legend styles.docs.cssjust maps Starlight's variable names onto it.dyno-chart.jsnow hastestCount,sheetNote, andsheetSpan, andsheetHeadreturns which side the note goes on. The reporter, saved reports, and the docs hero share them, so labels can't drift.Smaller cleanups:
generate.jswrites it as JSON (valid YAML) instead of hand-built YAML strings.src/browser, which is enough to load the shared font.docs/design.mdcovers the docs site andbrand.css.Screenshots
Homepage

After Run it again

Homepage, light

A guide page

A guide page, light

404

Phone width

Testing
npm test: 262 passed, 2 skipped. The reporter now loadsbrand.css, and I compared the reporter and saved report screenshots with the earlier ones; they look the same.npm --prefix site test: 7 passed, including the docs browser tests and the link checker.npm --prefix site run build. It still warns that[...slug]also lists the 404 entry; Starlight's/404route wins and renders it.A few things I left alone: