4 ms·
You should consider Storybook. It has really changed my team's thought around frontend components -- they think in much more of an atomic design mentality now,
by frio 3y ago
You should consider Storybook. It has really changed my team's thought around frontend components -- they think in much more of an atomic design mentality now, build little stories out of their atoms, and then assemble those onto our existing pages. The APIs they're building are cleaner and less ad-hoc, which contributes to building more reusable, understandable and refactorable code.
I'm mainly saying this because I had a similar mentality to you -- I didn't see the point -- but I now use it even on personal projects. It's nice to be able to easily see my various widgets isolated, on their own and tweakable without needing to navigate five layers deep into my application to alter them.
- Solvency 3y agoThis nomenclature is so cringey to me. Building "stories" out of "atoms". It's like a mishmash of random childlike words appropriated together.
- stevage 3y agoYeah, agreed. I find when some tech embraces a metaphor too enthusiastically it can just become exhausting. SaltStack was like that, full of its "pillars" (pillars of salt? get it? some biblical reference) and "grains" etc etc. Or Homebrew with its "taps" and "kegs". I'm fine with just the standard most appropriate generic word, whether it be module, component, database, etc.
- tobr 3y agoIt comes from a desire to turn something simple - a dedicated place in your project to try and document your reusable components - into a product. Then, much like Twitter has tweets, Codepen has pens, Reddit has subreddits etc, so Storybook has stories. It should probably never have been so productized, because it is way more complex than it needs to be. Again, it’s a very simple idea, and in my experience, many teams use only the most basic setup, and have never really considered why they took on a VC-funded dependency just to render some components.
- frio 3y agoThat's a shame. You can find documentation at https://bradfrost.com/blog/post/atomic-web-design/ https://bradfrost.com/blog/post/atomic-web-design/ on the methodology -- it's pretty lightweight, and is really just a vocabulary for discussing different groups of UI elements. When you have to build a consistent style for your application, this kind of tool is really useful -- it helps you build more reusable components and keep them documented somewhere.