This is horrendously bad advice. The article is basically recommending organizing by type as the first layer, instead of subject. But this is precisely the reason modern large codebases are so difficult to maintain and are bugy and insecure and cost insaine inappropriate quantities of cash to maintain.
My main advice would be this:
generally, 2 top level folders under src, common and pages or routes depending on whether it's front or backend.
common folder can be organized by type as the article describes, pages get ordered by page subject and complex pages can have layers of type and subject folder structure. Login is simple, stock trader will be nested deep.
ensure that ALL subject based folders (login, email, etc) have only one file in it, referred to as the [subject] container and subfolders for its children and subject specific support files; one must make smart decisions about chosing the substructure here, by type or subject. This tells the dev the root file, instead of having to open 20 flat files and reverse engineering something that was assembled but not engineered. Also ensure all type folders are broken down by subject and generally avoid flat structure here unless it makes sense (e.g. if you have 1000 related forms, flat might be appropriate, until they have their own reducers, css, etc).
I would also strongly consider adding another layer: common/data and common/view as well as pages(or routes on backend)/login/(data and view). This significantly improves code in react applications because view should be data independant in react, react has no support for data it is view and layout control only... so data often suffers from the learning curve of react and the view does as well because data ends up encapsulated in the view by those new to react.
When designing architectural structure one must know what one is building. This is rarely the case in the web world were iteration is king, unfortunately. This is why it is key to refactoring and refactoring often with iterative architectural solutions.
But be warned, you do it like this app suggests, and it's a huge complicated app used by millions, it will be a costly nightmare in the long term.
This is horrendously bad advice. The article is basically recommending organizing by type as the first layer, instead of subject. But this is precisely the reason modern large codebases are so difficult to maintain and are bugy and insecure and cost insaine inappropriate quantities of cash to maintain.
My main advice would be this:
When designing architectural structure one must know what one is building. This is rarely the case in the web world were iteration is king, unfortunately. This is why it is key to refactoring and refactoring often with iterative architectural solutions.
But be warned, you do it like this app suggests, and it's a huge complicated app used by millions, it will be a costly nightmare in the long term.
Thanks for your comment, I really appreciate it. I will use your advice on web projects from now on 👍🏾.