Component playground (embedded Storybook) + design token surface

Aperta
#60 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
20/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go, react, storybook, typescript

Direzione di ricerca

The payload names no files, so start from the grit CLI command registration and the package that exports the React primitives (CurrencyField, SearchableSelect, DateField, StatusBadge, FilterChips). Decide how the separately shipped playground is embedded and where design tokens are defined before adding stories. Done means grit playground serves localhost:6006 in a scaffolded app, every primitive has at least one story, and tokens are importable from @grit/tokens.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement

Problem

A framework's UI primitives are only useful if developers can find them. Today, "what components ship with Grit?" is answered by reading the source. New devs keep re-inventing existing components because they don't know they exist.

Proposal

`grit playground` opens an embedded Storybook (or Ladle / Histoire) at `localhost:6006` showing:

  • Every framework UI primitive (CurrencyField, SearchableSelect, DateField, StatusBadge, FilterChips, …) with live editable props
  • Design tokens (colours, spacing, type ramp) on one screen with copy-to-clipboard
  • Layout primitives (TwoPane, AppShell) demoed with toggles for empty state, loading, error
  • Form patterns (drawer + grid + actions) demoed end-to-end

The playground ships separately so it doesn't bloat production builds. Updated stories ship with every framework release.

Why this is differentiating

Mantine, Chakra, Radix all owe their adoption partly to phenomenal docs / playground experiences. A Go framework with a first-class playground is a category-of-one offering.

Acceptance

  • `grit playground` works in any Grit app with zero setup
  • Every primitive has at least one story
  • Design tokens are programmatically exposed (`@grit/tokens`) so apps can override consistently
Lingua principale
Go
Stelle
152
Fork
20
Merge medio
1g 49m
PR unite (30g)
5

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di MUKE-coder/grit

Tutte le issue di MUKE-coder/grit

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.