{"action":"closed","issue":{"url":"https://api.github.com/repos/meteor/guide/issues/274","repository_url":"https://api.github.com/repos/meteor/guide","labels_url":"https://api.github.com/repos/meteor/guide/issues/274/labels{/name}","comments_url":"https://api.github.com/repos/meteor/guide/issues/274/comments","events_url":"https://api.github.com/repos/meteor/guide/issues/274/events","html_url":"https://github.com/meteor/guide/issues/274","id":141182590,"number":274,"title":"[React] Containers vs pages","user":{"login":"ffxsam","id":12532733,"avatar_url":"https://avatars.githubusercontent.com/u/12532733?v=3","gravatar_id":"","url":"https://api.github.com/users/ffxsam","html_url":"https://github.com/ffxsam","followers_url":"https://api.github.com/users/ffxsam/followers","following_url":"https://api.github.com/users/ffxsam/following{/other_user}","gists_url":"https://api.github.com/users/ffxsam/gists{/gist_id}","starred_url":"https://api.github.com/users/ffxsam/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ffxsam/subscriptions","organizations_url":"https://api.github.com/users/ffxsam/orgs","repos_url":"https://api.github.com/users/ffxsam/repos","events_url":"https://api.github.com/users/ffxsam/events{/privacy}","received_events_url":"https://api.github.com/users/ffxsam/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":14,"created_at":"2016-03-16T06:08:49Z","updated_at":"2016-04-06T23:29:56Z","closed_at":"2016-04-06T23:29:56Z","body":"http://guide.meteor.com/v1.3/react.html#using-createContainer\r\n\r\n>Then we create a ListsShowPage container component which wraps it and provides a data source\r\n\r\nIf I may offer some thoughts on this:\r\n\r\nWhat if we just have a page be a regular component or stateless function? In my projects, I usually have four folders under `client` that are responsible for the layout and structure of the app: layouts, pages, containers, and components. The reasoning for not making a page a container is that it may not even care about data that high up, and only be concerned with laying out the page. Not to mention, a page can contain multiple containers. You could have a structure like this, where containers are far down along the tree:\r\n\r\n    P > C1 > S1 > S3 > C4 > S5\r\n           > S2 > C2 > S4\r\n\r\n(P = page, C = container, S = stateless func)\r\n\r\nWhat do you all think?"}}