Reaction

Reaction is an event-driven, real-time reactive commerce platform built with JavaScript (ES6). It plays nicely with npm and Docker, and is based entirely on JavaScript, CSS, and HTML.

Features

Reaction’s out-of-the-box core features include:

Drag-and-drop merchandising
Order processing
Payments
Shipping
Taxes
Discounts
Analytics
Integration with dozens of third-party apps

Since anything in our codebase can be extended, overwritten, or installed as a package, you may also develop, scale, and customize anything on our platform.

Installation

reaction-cli installation

npm install -g reaction-cli
reaction init
cd reaction
reaction

Reaction requires Meteor, Git, MongoDB, OS Specific Build Tools, and (optionally) ImageMagick.

See our Requirements Docs for requirements that you may need to install for Reaction.

For more information on setup and configuration, check out the installation and configuration docs.

Planning

For an overview of our roadmap, visit our Features & Roadmap page.

You will find the roadmap defined as projects on the Reaction repository's project page.

Specific features in progress are found on the Reaction repository's milestones page.

Documentation

Multiple branches, release documentation is found at https://docs.reactioncommerce.com

The Reaction documentation source is located in the reaction-docs repository, while the documentation site is the reactioncommerce/redoc application.

Contributing

Star us on GitHub, it helps!

If you are interested in participating in the development of Reaction, that's really great!

The Reaction Gitter channel and forum are good places to engage with core contributors, the community, and to get familiar with Reaction. Our community guidelines can be found in our documentation.

Check out the issues page, and if you find something you want to work on, let us know in the comments. If you're interested in a particular project and you aren’t sure where to begin, feel free to ask. Start small!

If your contribution doesn't fit with an existing issue, go ahead and create an issue before submitting a Pull Request. This will allow the Reaction team to give feedback if necessary.

Pull Requests should:

Be very focused in scope. Smaller scopes are easier for us to digest and approve.
Note any existing associated issues.
Lint and adhere to the Reaction style guide.
Pass both acceptance tests and unit testing.

Testing

Testing is another great way to contribute. If you do discover a bug, create an issue to report it.

Integration tests can be run at the command line with reaction test.

Deployment

We ensure that all releases are deployable as Docker containers. While we don't regularly test other methods of deployment, our community has documented deployment strategies for AWS, Digital Ocean, and Galaxy.

For an introduction to Docker deployment, the Reaction deployment guide has detailed examples. Reaction Commerce also offers a managed deployment platform integrated with the Reaction command line.

lex4vn/reaction