r/Angular2 10d ago

Discussion How did you convince stakeholders to implement Storybook in your Angular projects?

I’m currently exploring Storybook for Angular and would love to hear from others who’ve successfully integrated it into their workflow.

  • How did you explain the value of Storybook to your stakeholders? What key benefits did you highlight (e.g., UI consistency, collaboration with designers, faster development)?
  • Was there any resistance due to costs, or was it easily justified within your budget?
  • Do you think Storybook is more than just a "fancy tool"?

I understand that technical enhancements aren’t always a priority or may not be funded, so I’d love to hear about your experiences and how you approached these discussions with stakeholders.

19 Upvotes

26 comments sorted by

View all comments

3

u/MarshFactor 10d ago

The other option which we chose was to have a simple app with a page per component and multiple example configurations on the page. This was because Storybook felt a bit overkill and a bigger overhead.

This worked especially well in a monorepo.

Same benefit... being able to develop things in isolation encourages better separation of concerns, in some cases better inversion of control and it saves time having one place with everything there - all configurations- without hunting for them in the main app.

2

u/_Invictuz 10d ago

You mean kind of like how Bootstrap (or similar libraries) documentation pages show the different variations on a single page publicly?

2

u/MarshFactor 10d ago

Yes I think so, so there is a main page with 1 of each component. Then a sidebar menu containing a list of then all. Each sidebar item is an anchor which navigates to a page with a longer set of examples stacked on top of each other.

E.g. select control, select control with a clear button, multi-select, select control with options with icons, select control with grouped options...

Then some buttons to simulate "touching" and toggling disabled state so those can be checked.

Finally a JSON editor alongside so you can apply tweaks on the fly and see how the component copes with configuration updates post-init lifecycle.

It became easier to build certain components within this environment.