All topics

Components

Classify components, centralize usage, remove duplicates — Button and Modal up next.

Components

Four categories, five rules, pragmatic migration, and Storybook to close the visibility gap.

  1. 01

    Sorted, not piled

    • Four categories — Primitive, Complex, Layout, Context-specific
    • Every component has an obvious shelf
    • "Where does this go?" stops being a debate
  2. 02

    Rules that break duplication

    • Location · responsibilities · composition · naming
    • Check before you create — the one that matters most
    • JSX = display, hooks = logic
  3. 03

    Migrate where it hurts

    • Refactor for pain, not for fun
    • Already done: VideoThumbnail, Dropdown, PaddedContainer
    • One PR swaps an implementation everywhere
  4. 04

    Storybook = the catalog

    • One place to see every component and its variants
    • Shared vocabulary with design
    • Makes "check before you create" actually possible

Fewer Legos, better organized — so the next piece you need is already there, and it actually fits.

References

Jira

Confluence