ADR: theme distribution — built-in vs cherry theme.install
- Dominant language
- CSS
- Stars
- 1
- Forks
- 0
- Avg merge
- 26m
- Merged PRs (30d)
- 62
Description
Part of #112. Ten built-in themes is real binary weight (fonts, icon masks, islands; orbit alone would vendor three.js at ~600 KB uncompressed). Decide, as an ADR, at the point prism lands:
- Option A: everything built in; accept the weight.
- Option B: clinical lane built in (CSS-only, cheap after #114); cutting-edge lane in `holsee/cherry-themes`, installed by a new `cherry theme.install NAME` — checksum-verified against the release, the `cherry upgrade` trust model.
- Option C: only orbit externalised.
Measure real binary deltas per theme before choosing.
Contributor guide
No contributing guide indexed for this repository
Research direction
Read the context in #112 and #114, then inspect how the prism theme and existing cherry upgrade trust model are defined. Measure real binary-size deltas for each theme and compare the three distribution options. Done means recording the selected approach in an ADR at the prism landing point, including whether cherry theme.install is required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- build-system, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100