Repository navigation
docs(demos): point the theme-variant section at the real asset paths and palette file - #4068
Merged
Merged
Conversation
worktrunk-bot
added
the
nightly-cleanup
This was referenced Sep 12, 2026
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
2 participants
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.
Two references in
docs/demos/CLAUDE.mdpoint at files and directories that do not exist, so anyone following them to change a demo's colors or find a recorded GIF lands nowhere.docs/light/wt-core.gifand friends. The build writes them todocs/public/assets/<target>/<theme>/<name>.gif(OUT_DIRindocs/demos/build), which is exactly what the directory-structure block at the top of the same file already says — the two sections contradicted each other._variables.htmlas the palette source. That file was removed in docs: rebuild the site with Astro and Starlight #3866 when the site moved to Astro and Starlight; the--wt-*custom properties now live indocs/src/styles/custom.css, which is also whatdocs/demos/shared/themes.pynames in its own docstring.Documentation-only, so there is no regression test to add; the claims are verified against
docs/demos/buildand against the file's own structure block.