Why "layouts" and "pages"? about react-starter-kit HOT 5 CLOSED

I don't want to mix templating engines. The reasoning behind "layouts", "pages" and "components" folders is to organize React.js components. For example you may have a StoreLayout React.js component with OnlineStore menu on it, the list of recently viewed products. Also you may have a few pages which will be nested inside this "layout" - CheckoutPage, ProductInfoPage etc. and you may also have small React components reused across many pages of the site like ShoppingCartStatus, CheckoutButton etc.

Do you have a better idea how to organize React components?

from react-starter-kit.

I think that purely components is more straightforward. Also, my page is a one-page app, I only have one layout and one page, that are in the same file. Everthing else is components (some of which could be considered layouts). But one html file.

from react-starter-kit.

I prefer Layouts and Pages as I want to have many virtual pages inside the application, each page gives a part of the application flow with components, which are only a small area of the page.
Layouts are good as some of the pages looks in a way, others in a different way, and combines some of the common components.
For me is a good separation of concern and helps me to focus only on some areas and reuse a lot of code.
I have no other explanation why I prefer to not have the pages and layouts in components than personal taste (and maybe because I don't like SPAs with only one virtual page)
Anyway, I think is very easy to remove that extra functionality if you don't need it.

from react-starter-kit.

Maybe supporting multiple layouts is an overkill.. How many layouts do your web applications usually have? Probably just a two or three. If so, a single layout component (top-level React component) can easily support multiple rendering options, for example with or without header & footer.

from react-starter-kit.

In the latest version there is no concepts of layouts and pages. There is now a single top-level component, see ./src/components/App. So, I guess this issue is no longer relevant.

from react-starter-kit.