You can start here:
http://marmelab.com/blog/2015/12/17/react-directory-structure.html
I may go multiple levels deep, but in essence it's about keeping structure based on the feature/section you're working on. Not every feature will contain controls and/or other models. Some may be one or the other.
In this way, you are less likely to need to scroll back and forth to keep your smart and dumb components and/or reducers etc in your project, as related items should be in proximity.
The same goes for tests... the .(test|spec).js file should be right next to the .js file... It serves nobody to have to trek through several layers of identical directory structure to get to them.
You can start here: http://marmelab.com/blog/2015/12/17/react-directory-structure.html I may go multiple levels deep, but in essence it's about keeping structure based on the feature/section you're working on. Not every feature will contain controls and/or other models. Some may be one or the other. In this way, you are less likely to need to scroll back and forth to keep your smart and dumb components and/or reducers etc in your project, as related items should be in proximity. The same goes for tests... the .(test|spec).js file should be right next to the .js file... It serves nobody to have to trek through several layers of identical directory structure to get to them.