3 ms·
This nomenclature is so cringey to me. Building "stories" out of "atoms". It's like a mishmash of random childlike words appropriated together.
by Solvency 3y ago
This 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.