This project acts as a template for front-end application's using React and Redux, along with several other tools and technologies.

It embodies a rather extensive amount of research into this style of architecture and attempts to create an opinionated structure for building on. Additionally, our hope is that this can act as a kicking off point for beginners of React or as a solid base to those who already have some experience.

• React for managing the presentation logic of your application.
• Redux for generating and managing your state model.
• Portals for making AJAX calls to a server.
• Stylus + Helpful UI for stylesheet compilation.
• Gulp for handling automated tasks.
• Babel for compiling ES2015+ down to ES5 compatible code. Additionally, this project is set up to support type checking using Flow syntax.
• WebPack for bundling code down to a single file and enabling hot module reloading.
• Express for serving up the development server.
• Mocha + Chai for testing.

In order to get started developing, you'll need to do a few things first.

1. Install all of the node_modules required for the package. Depending on your computer's configuration, you may need to prefix this command with a sudo.

npm install

or

sudo npm install

2. Create your .env environment file by making a duplicate of the .env-example and remove the -example. In the .env file, you can set environment related variables like your API_HOST or APP_ENV.

APP_ENV=local
API_HOST=http://localhost:9700/fake-api

3. Lastly, run the start command to get the project off the ground. This command will not only build your JS files using the Webpack dev-server, but it will also auto-compile your Stylus files on every .styl file save.

npm start

4. Head over to http://localhost:9700 to see your app live!

This is where your application will be compiled. Assets, like images and fonts, should be placed directly within this folder. Also in this folder is a default index.html file for serving up the application.

The client folder houses the client application for your project. This is where your client-side Javascript components (and their directly accompanying styles) live.

Your unit and integration tests for components, reducers and services. It is not really necessary to test action creators or contexts (unless you really want to).

These are your Redux action creators. There are 2 styles of action creators: direct and deferred.

export function directAction (/* params */) {
  return { type: 'ACTION_NAME', ... };
}

export function deferredAction (/* params */) {
  return function (dispatch) {
    dispatch({ type: 'ACTION_NAME', ... });
  };
}

Your React components along with their accompanying Stylus files. React components should be kept "dumb" and have no knowledge of the Redux state model. Build your React components to accept "hook" methods that can be passed in externally.

For example, if your component needs to dispatch an action when the user clicks a button, simply write this method to invoke a property that can be passed in.

render () {
  return (
    <button onClick={this.props.onButtonClick}>Fire Some Action</button>
  );
}

Contexts allow you to hook up "dumb" components to your Redux state model. This is essentially the glue between your state model and presentation logic.

Your Redux reducers that will generate your state model.

Singletons, classes and utilities that can be used by any part of your application.