3 ms·
In my experience, Atomic Design's interesting principle is that of separating Atoms and Molecules. Between Molecules and Organisms it gets fuzzy and arbitrary,
by beaconstudios 8y ago
In my experience, Atomic Design's interesting principle is that of separating Atoms and Molecules. Between Molecules and Organisms it gets fuzzy and arbitrary, and Pages/Page Templates are not a new concept. It's a cool-sounding design language tool and Atoms are really useful, but that's the only positive innovation I've experienced from using it at a previous workplace.
- deltron3030 8y agoI can't find justifications for going beyond App -> Page -> Components, and introduce lower levels. You can rule out Atoms as layer if you work with a style guide and define them globally at the app level. You'd override or modify "Atoms" values at the component level if you need to. Even just a word or text can be regarded as component if you include the surrounding whitespace. Whitespace matters! The conclusion is that the highest and lowest levels are actually the same! You build your components from the global style guide/CSS stylesheet!
- beaconstudios 8y agoThe benefit of atoms at the company I was at, was to force developers to build reusable micro-components (the type of thing you'd put in your "components" directory in react/redux apps). Otherwise, I agree if that job is already being done properly.
- Izkata 8y agoWe use it for React+Redux, and the molecule/organism split is actually the best defined one for us: Organisms are connected to the Redux store, molecules and below are not. Organisms are for specific parts of the site, and tend to be tied to that part, while molecules and below are all much more reusable and so we have to avoid tying them to specific data from Redux. (Mostly at least, there has been some leakage where we broke this pattern, but it's true for like 95% of our components)