trevato/mitosis

Public: anyone can read this; nobody can change it.

More
Mapg aCommitsg mBranchesg bRunsg rEventsFlows

Proposal: The wardrobe — themes you pick, not tokens you fork #238

benjivers opened this view on origin

Check · Review · Land · Live — No review yet. Next: reviewer, no review yet.

ConversationFiles
Merges on the origin

Adds `docs/proposals/the-wardrobe.md`.

1 file · +33 −0

waiting checks and the preview wait for a writer to approve this head

Check on open-platform/mitosis: passing, as of

Checks and the preview wait for a writer to approve this head

A guest

This pull comes from a guest: its preview runs without the app's variables or a forge token until a person who can write here approves it.

This pull waits for a person who can write here to review it; it never lands on its own.

benjivers opened this view on origin

Adds docs/proposals/the-wardrobe.md.

The idea (proven on a sovereign fork, git.benjivers.com): make platform themes a catalog you pick from instead of token files each app/operator forks and hand-edits.

  • Each theme is a small brand.json (a few seed decisions) that a generator expands into the full W3C token set — adding a look is one file, not hundreds of values.
  • One brand renders two surfaces: the app design tokens and the forge (Forgejo) chrome — so a single look covers the whole platform, not just apps.
  • Picking a look is a reviewable one-line reference, not a fork of the token vocabulary.
  • Stock looks ship in the box (slate, dune, contrast, open-platform, plus electric/neon-grid).

Prior art: neon-grid and electric already re-skin a live Forgejo UI from a generated CSS bundle on the benjivers fork. This proposal upstreams that pattern. Proposal only — no code, no repo migration.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs