// the find
phenixdigital/phoenix_storybook
A pluggable storybook for your Phoenix components.
A Storybook-style component browser for Phoenix/LiveView apps, mounted directly into your router as a plug. You write `.story.exs` files describing your components' variations and attributes, and the library auto-discovers them and renders a navigable UI. Aimed at Phoenix teams who want isolated component development and documentation without leaving the Elixir stack.
Auto-discovery of story files via filesystem scanning means zero registration boilerplate — drop a `.story.exs` file in the right folder and it appears in the sidebar. The interactive playground is genuinely useful: it lets you tweak assigns live without writing code. The iframe sandboxing for components that need isolated CSS is a real design decision, not an afterthought. The generator (`mix phx.gen.storybook`) produces working stories for Phoenix core_components out of the box, so you're not starting from a blank slate.
Single maintainer working in free time — the Ko-fi button in the README is honest about the sustainability situation; a v1.2 library with 861 stars and one person behind it is a bus-factor risk for production teams. Story files are `.exs` scripts compiled at runtime, which means a syntax error in one story crashes the whole storybook process in eager mode — error boundaries are thin. There's no snapshot/visual regression testing built in; the `visual_test_live` module exists but you're essentially writing your own diffing. Theme support requires passing a `theme` assign through to every component manually, so components that don't already accept a theme assign need wrapper stories.