tony/phoenix_storybook — explained in plain English
Analysis updated 2026-07-18 · repo last pushed 2023-11-11
Generate a searchable catalog of every UI component in your Phoenix app so designers and developers can browse them in one place.
Write story files describing a component's options and states so teammates can see all its variations without reading code.
Use the built-in playground to interactively test a component's inputs and see how it responds live.
Organize stories as standalone guideline pages or full example pages showing components working together.
| tony/phoenix_storybook | 0verflowme/alarm-clock | 0verflowme/seclists | |
|---|---|---|---|
| Language | — | CSS | — |
| Last pushed | 2023-11-11 | 2022-10-03 | 2020-05-03 |
| Maintenance | Dormant | Dormant | Dormant |
| Setup difficulty | easy | easy | easy |
| Complexity | 2/5 | 2/5 | 1/5 |
| Audience | developer | vibe coder | ops devops |
Figures from each repo's GitHub metadata at analysis time.
Add the dependency and run a generator command, integrates into an existing Phoenix router.
PhoenixStorybook builds a browsable visual catalog of the reusable UI components in a Phoenix web app, so teams can see and test every component in one place.
Dormant — no commits in 2+ years (last push 2023-11-11).
License is not stated in the available content.
Setup difficulty is rated easy, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.