. ____                                             _        _             _     _ _            _                  
 / ___|___  _ __ ___  _ __   ___  _ __   ___ _ __ | |_     / \   _ __ ___| |__ (_) |_ ___  ___| |_ _   _ _ __ ___
| |   / _ \| '_ ` _ \| '_ \ / _ \| '_ \ / _ \ '_ \| __|   / _ \ | '__/ __| '_ \| | __/ _ \/ __| __| | | | '__/ _ \
| |__| (_) | | | | | | |_) | (_) | | | |  __/ | | | |_   / ___ \| | | (__| | | | | ||  __/ (__| |_| |_| | | |  __/
 \____\___/|_| |_| |_| .__/ \___/|_| |_|\___|_| |_|\__| /_/   \_\_|  \___|_| |_|_|\__\___|\___|\__|\__,_|_|  \___|
                      |_|                                                                                          

Appendix

Other Proposed Architectures

• react-conf-app/app/scenes at master · Thinkmill/react-conf-app is really similar
• Grouped by component complexity - like Atomic Design
• Dan Abramov tweets
  • People ask about Redux app file structure very often. Here’s what I think might be sensible:
  • I’m out of this debate 😂 . I dislike feature folders because they introduce artificial limitations into an already decoupled system.
• How to better organize your React applications? — Medium
• Rules For Structuring (Redux) Applications — Jack Hsu
• Node Hero - Node.js Project Structure Tutorial | @RisingStack
• Ember Module unification - dgeb
• How OkCupid organizes its multi-page React app