Skip to content

Feat/theme aware logo#262

Merged
btravers merged 3 commits into
mainfrom
feat/theme-aware-logo
Jun 26, 2026
Merged

Feat/theme aware logo#262
btravers merged 3 commits into
mainfrom
feat/theme-aware-logo

Conversation

@btravers

Copy link
Copy Markdown
Collaborator

No description provided.

btravers and others added 2 commits June 26, 2026 12:54
Use the beetroot hourglass mark in both color schemes: VitePress per-theme nav
logo (logo-light/dark.svg) plus an adaptive prefers-color-scheme favicon
(logo.svg). These variants were finalized after the design-system PR was
already squash-merged, so they land here in a follow-up.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
custom.css pinned the jsDelivr import to an old landing commit
(7ad5679) whose vitepress.css predates the dark-mode fix, so dark mode
fell back to VitePress's default indigo brand and Inter font. Repoint to
the immutable @v1.0.0 tag, which serves the corrected adapter
(theme-aware brand/surfaces/fonts via raised-specificity selectors).
Copilot AI review requested due to automatic review settings June 26, 2026 12:53

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the VitePress docs theme stylesheet import to reference a new upstream design-system version, presumably to pick up theme-related visual changes (e.g., for a theme-aware logo) without forking local tokens/styles.

Changes:

  • Switched the shared design-system CSS import from a pinned commit SHA to the v1.0.0 ref on jsDelivr.

Comment thread docs/.vitepress/theme/custom.css
@btravers btravers merged commit 755d550 into main Jun 26, 2026
10 checks passed
@btravers btravers deleted the feat/theme-aware-logo branch June 26, 2026 12:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants