While I am a fan of applying atomic design to components, I have to disagree with you about it helping with code organisation - at least in the manner you propose.
At first it does help, when the application is small. However, down the road - when the application is larger and you get back to a feature after 6 months - not having the related components together creates mental overhead.
For our next project we will keep using atomic design, but we're looking into better ways to organise our components. We'll probably go back to feature folders and depending on the size of the feature the components will be either prefixed or put in subfolders according to their atomic type.
An added benefit is that it's a step closer to breaking a feature out into a separate npm package.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
While I am a fan of applying atomic design to components, I have to disagree with you about it helping with code organisation - at least in the manner you propose.
At first it does help, when the application is small. However, down the road - when the application is larger and you get back to a feature after 6 months - not having the related components together creates mental overhead.
For our next project we will keep using atomic design, but we're looking into better ways to organise our components. We'll probably go back to feature folders and depending on the size of the feature the components will be either prefixed or put in subfolders according to their atomic type.
An added benefit is that it's a step closer to breaking a feature out into a separate npm package.