Move all themes into `prism-themes`?
Open
Nobody has claimed this yet.
themes
- Dominant language
- JavaScript
- Stars
- 13k
- Forks
- 1.4k
- Avg merge
- 15h 36m
- Merged PRs (30d)
- 3
Description
Should we move all themes into prism-themes?
Right now, our collection of themes is split into two repositories. This is sorta suboptimal.
@LeaVerou @Golmote @mAAdhaTTah
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 comparing where themes currently live in the PrismJS repository and in prism-themes, since the issue identifies no files or tests. Define the repository boundary and migration scope with the maintainers; done means the theme collection has one agreed, working home without regressions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100