Organizing a directory structure is important because it affects the way we think. Especially it affects how you treat components and Redux stores. And it influences the complexity and redundancy of the entire app. So, think carefully and communicate with colleagues!
/src /atoms # atom components /button /typography /components # components /PostList /PostDropdown /pages /paperShow /signUp /hooks /reducers /actions /helpers /typings /api
This directory is for
atomic components which is the smallest component. If your project’s
atomic components are entirely depends on external library(such as Bootstrap), this directory can be omitted.
This directory is for the common component which knows about our business logic.
This directory is for the
Redux reducers & slices. Redux reducers should be functional, data-driven, feature-based. Making reducer following by Page or Component is an anti-pattern. I’ll explain it later.
API requests and data models
Custom type definitions