Theme system
Open
Nobody has claimed this yet.
plot building
reader
syntax
writer
- Dominant language
- Rust
- Stars
- 554
- Forks
- 30
- Avg merge
- 17h 27m
- Merged PRs (30d)
- 8
Description
This is just an issue to keep track of the notion that we need a theme system.
We've yet to crystallise a nice syntax for this.
To write down a few thoughts we've not yet commited to:
- Potentially we could have a file-backed theme system, wherein the theme is defined by a
brand.yml-like file (hence tagging reader). - A lesson from ggplot2 is that a monolithic theme is a recipe for chaos. I'd be better to have granular bits of theme for particular components.
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
The issue names no files, tests, or entry points; begin by clarifying the theme syntax and whether themes are file-backed. Compare the proposed granular component themes with the existing project structure, and consider the work complete only when the scope and design are agreed.
Written by the indexing model from the issue text.
Assessment
- Domain
- design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100