documentation VS reference-architecture

Have you heard about Feature-Sliced Design? I have personally found it extremely helpful as the project grows larger, though it can have a bit of a learning curve

In our case, the current folder structure resembles Feature-Sliced Design:

Feature-slice design is the one and only correct solution imho

(https://feature-sliced.design/)

for large spa I recommend https://feature-sliced.design/

There are many more benefits of using feature sliced design which are well documented in the docs. I highly recommend you to check it out and learn new ways of organizing your frontend project.

Hi, I use feature-sliced design for big or middle spa. Excellent solution for scalability! https://feature-sliced.design/

Ссылка на офф сайт.

You can also see a way around this restriction in "DDD, Hexagonal, Onion, Clean, CQRS, ... How I put it all together" and Feature Sliced.

Adopt an architecture or design patterns (e.g. client-side reference architecture) that help you determine which parts should be stable. Patterns and consistent architecture help to create imaginary boundaries between functions and modules as well.

The above image is coming from a reference architecture from client-side applications. It is only used to visualize the different types.