Table of Contents
Introduction
Some General Rules
Base Component Names
Tightly Coupled Component Names
Order of Words in Component N...
For further actions, you may consider blocking this person and/or reporting abuse
Although my 'organization' is small (just me) most of my projects are monoliths developed with Vue, Laravel and Inertia, and I prefer the feature sliced design structure for always thinking about scalability of projects and ease of maintenance.
Excellent post, thanks for sharing it!
Seeing those example file structures is extremely helpful! In a way, I already used the Atomic Design approach without the molecules level. Depending on the project size, I guess it's fine to skip one level.
Thank you for this post!
Great article!
Had not seen Feature-Sliced Design before, but I really like what I see.
So much so I've linked to this post from my recent Nuxt Layers article:
Thanks!
Awesome, thank you! Yeah, Feature-Sliced Design is not very popular, but it looks really interesting. In general, the frontend world lacks good content about structure and architecture.
Thanks so much for this!
A truly remarkable blog
Good article, thanks for share!
The Atomic Design is very powerful and amazing, I will try it in the future project :)
this is article give very gain for me!
Thanks so much for this! It was extremely insightful.
One of the amazing blogs
This is so helpful.
Thanks for sharing!