{"action":"opened","issue":{"url":"https://api.github.com/repos/mxstbr/react-boilerplate/issues/877","repository_url":"https://api.github.com/repos/mxstbr/react-boilerplate","labels_url":"https://api.github.com/repos/mxstbr/react-boilerplate/issues/877/labels{/name}","comments_url":"https://api.github.com/repos/mxstbr/react-boilerplate/issues/877/comments","events_url":"https://api.github.com/repos/mxstbr/react-boilerplate/issues/877/events","html_url":"https://github.com/mxstbr/react-boilerplate/issues/877","id":171431971,"number":877,"title":"Suggestions for folder structure in a large app","user":{"login":"loicginoux","id":824936,"avatar_url":"https://avatars.githubusercontent.com/u/824936?v=3","gravatar_id":"","url":"https://api.github.com/users/loicginoux","html_url":"https://github.com/loicginoux","followers_url":"https://api.github.com/users/loicginoux/followers","following_url":"https://api.github.com/users/loicginoux/following{/other_user}","gists_url":"https://api.github.com/users/loicginoux/gists{/gist_id}","starred_url":"https://api.github.com/users/loicginoux/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/loicginoux/subscriptions","organizations_url":"https://api.github.com/users/loicginoux/orgs","repos_url":"https://api.github.com/users/loicginoux/repos","events_url":"https://api.github.com/users/loicginoux/events{/privacy}","received_events_url":"https://api.github.com/users/loicginoux/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-08-16T14:41:16Z","updated_at":"2016-08-16T14:41:16Z","closed_at":null,"body":"Hello,\r\nFirst, thank you for this boilerplate which is really solid and it's saving us a lot of work for the setup.\r\nI am starting with this boilerplate and after few hours of development, I already have about 20 containers and components and few pages. it seems like using just a separation between containers and components is not enough and too flat. I am thinking ahead and I guess, when the app will be finished, this file structure will be hard to use.\r\n\r\nI wanted to know if anyone has adopted a different structure when dealing with an app with hundreds of containers and components.\r\nI read few issues talking about the subject (the major one being #27, I guess) and people seems to go with the stucture described in [this gist](https://gist.github.com/ryanflorence/daafb1e3cb8ad740b346) which seems to be cleaner and easier to manage.\r\n\r\nI wanted to know if people working with larger apps have used this structure, what do you think of it ? any downside ? Did you try another organization ?\r\n\r\nnote: I put this here as well, the [LIFT structure principle](https://github.com/johnpapa/angular-styleguide/blob/master/a1/README.md#application-structure-lift-principle) which is from angular but can be applied to any file structure."}}
{"actor":{"display_login":"loicginoux"}}