tiny-pilot / tiny-pilot/tinypilot
Refactor naming of CSS color variables
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.5k
- Forks
- 291
- PR merge metrics
- No merged PRs in 30d
Description
Currently, we use “meaningful” / descriptive names for the colour shades, like --brand-blue-light, or --brand-red-bright.
The downside of this naming approach is that it doesn’t scale well, the more colours we add. So we could consider changing it to something number-based, e.g. --brand-blue-1 through --brand-blue-5.
(I still, btw., believe that it’s worthwhile to have an explicit catalogue/inventory of all colours that we use, just to force ourselves to keep track of them, and add new ones only deliberately.)
Contributor guide
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 with app/static/css/style.css and inspect the linked colour-variable definitions. Search the repository for each --brand-* variable to identify all references, then apply a consistent numbered naming scheme and verify that the colour inventory remains explicit and all usages are updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100