[Brainstorming] Decouple token names and themes
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13k
- Forks
- 1.4k
- Avg merge
- 15h 36m
- Merged PRs (30d)
- 3
Description
I know this is a tough one, but I'm opening this thread for an initial discussion. How do other highlighters deal with this? We currently have over 100 languages, and it's becoming harder and harder to have meaningful names, which was one of Prism's advantages. For example, see #1044.
Perhaps languages could associate with a palette (color1, color2, etc) instead of token names, and then have the stylesheet built automatically? But then what do we do for npm?
Anyways, feel free to throw your ideas in here! Even if you don't think they're good ideas, they might give someone a good idea!
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
This is an initial discussion rather than an implementation task, and it names no files, tests, or entry points. Read the ideas in this issue and the referenced #1044, compare how other highlighters separate token names from themes, and define a concrete scope and acceptance criteria before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100