Consistent use of CSS variables for themeing
Nobody has claimed this yet.
- Dominant language
- Lean
- Stars
- 384
- Forks
- 124
- Avg merge
- 22h 28m
- Merged PRs (30d)
- 10
Description
All genres that output highlighted Lean code should use a consistent set of CSS variables to control all of the following:
- Font families, weights, colors, and styles (italic/upright) for each token that Verso emits
- Colors used for information, warning, and error indications
- Background colors for inline code, block code, hovers, "what you're pointing at indicators", and proof states
There should also be a guide as to what the "safe" properties are to set in local CSS (e.g. for controlling overflow, indentation, and the like for rendered code)
Right now it's a bit chaotic, leading to inconsistencies.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the genres that output highlighted Lean code and inventory their current CSS. Then identify the existing styling for token fonts, indicators, backgrounds, and local code properties. Done means these outputs use a consistent CSS-variable set and include a guide to safe local CSS properties.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- design, documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100