ARc (Atomic React) is a React starter kit based on the Atomic Design methodology. It's progressive, which means that you can start with the basic boilerplate and try the other features when you are comfortable.
See the demo.
The basic stack with React, Webpack, react-router and Jest.
Master plus redux, redux-saga and redux-form.
Redux plus Server Side Rendering (everything works with javascript disabled, even the forms).
Universal plus REST API.
Generate components, containers, redux stores and the entire project through a CLI utility.
Did you fork this repo and made something different? Add it to this section and send a PR.
I've been a web developer for the past 14 years, and after dealing with IE vs. Netscape wars, <table> layouts and flash websites I can say we live now the best moment in web development. Web components are awesome and React makes it better.
React stimulates you to create very small and pure components. However, as your project grows, you will have an increasing components folder. At some point, this will be really huge and hard to maintain.
I had a React project with more than 100 components in the components folder. The first approach I tried to organize it was separating the components by domain (described here), but I did realize that most of my components didn't belong to any domain, they were shared, so my problems were just moved to the commons folder.
The Atomic Design approach comes handy to solve this problem because it considers the reusability through composition, which is actually what React is. You will have your minimal/stylish components in one folder, pages in another and so on.
Just clone the repository and remove the .git folder:
$ git clone https://github.com/diegohaz/arc my-app
$ cd my-app
$ rm -rf .git
$ npm install # or yarnOnce you have installed the dependencies, you can use npm start to run a development server.
Use npm run build to transpile the code into the dist folder. Then, you can deploy it everywhere.
The source code should be placed in src; public/static files should be placed in public so they can be included in the build process.
Because of webpack's config, we can import our source modules without relative paths.
import { Button, HomePage } from 'components' // src/components
import App from 'components/App' // src/components/App
import routes from 'routes' // src/routesIf you want to start with a clean and minimal source code without the predefined components and tests, just use the src-clean folder instead by renaming it to src (and removing or renaming the older one to something like src-example).
Also, you might want to remove unnecessary dependencies:
npm u -S react-modal # used by src/components/molecules/ModalThis project leverages the Atomic Design methodology to create a scalable and easy to maintain component folder structure. See why.
However, Atomic Design should be a solution, not another problem. If you want to create a component and don't know where to put it (atoms, molecules, organisms etc.), do not worry, do not think too much, just put it anywhere. After you realize what it is, just move the component folder to the right place. Everything else should work.
This is possible because all components are dynamically exported on src/components/index.js and imported in a way that Atomic Design structure doesn't matter:
import { Button, Hero, HomePage, PageTemplate } from 'components'To understand better the Atomic Design methodology, you can refer to the src/components folder here and the Pattern Lab Demo, which this project is based on. Basically, you can think this way:
- An atom is a native html tag or a React Component that renders an html tag (e.g
Input); - A molecule is a group of atoms (e.g.
Field); - An organism is a group of atoms, molecules and/or other organisms (e.g.
Form); - A page is... a page, where you will put mostly organisms (e.g.
HomePage); - A template is a layout to be used on pages, see why templates are good practice.
I highly recommend you to incorporate react-storybook on your development process. It really improves productivity and developer experience. Actually, most of the time you can just use the storybook instead of the real webapp while creating components.
This already comes with the boilerplate and you can simply use npm run storybook to get it running. But, if you don't want that, just run:
rm -rf .storybook # remove .storybook folder
npm u -S @kadira/storybook # remove storybook dependencyWhen issuing, use the following patterns in the title for better understanding:
[v0.3.1-redux] Something wrong is not right # the v0.3.1 release of the redux branch
[redux] Something wrong is not right # the actual code of the redux branch
Something wrong is right # general, related to master or not directly related to any branchPRs are very appreciated. For bugs/features consider creating an issue before sending a PR. But there're other things you can contribute directly:
- I'm not a native english speaker. If you find any typo or some text that could be written in a better way, please send a PR, even if it is only a punctuation;
- If you forked or created another boilerplate based on this one with another features (using
css-modulesinstead ofstyled-components, for example), add that to the Forks section with the following pattern:- arc-css-modules - A short description
Built something cool with ARc? Send a PR adding it to this list:
- replace-this - A short description
Thanks goes to these wonderful people (emoji key):
 Prabhat Sharma 💻 |
 Sven Schmidt 🐛 💻 |
 Sebastian |
 Steven Haddix 💻 |
 Ruslan Kyba 🐛 💻 |
 Abhishek Shende 💻 |
|---|
This project follows the all-contributors specification. Contributions of any kind welcome!
The MIT License (MIT)
Copyright (c) 2016 Diego Haz
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.