Reaction is an event-driven, real-time reactive commerce platform built with JavaScript (ES6). It plays nicely with npm, Docker, and React.
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.
reaction-cli installation
npm install -g reaction-cli
reaction init
cd reaction
reactionReaction requires Meteor, Git, MongoDB, OS Specific Build Tools, and (optionally) ImageMagick.
See our Requirements Docs to learn more about requirements for installing Reaction.
For more on setup and configuration, check out the Installation and Configuration docs.
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.
Release documentation across multiple branches can be found at https://docs.reactioncommerce.com.
The Reaction documentation source is located in the reaction-docs repository, while the documentation site is in the reactioncommerce/redoc application.
API Documentation can also be generated locally, use npm run docs to output documentation to /tmp/reaction-jsdocs/
There are many ways to get connected with the Reaction core team and community:
- Reaction Commerce Gitter chat
- Reaction Commerce forum
- Reaction Community calls: Join our biweekly community calls every other Wednesday at 7AM PST/10AM EST. Subscribe to our Reaction Community Google Calendar to RSVP to the next call and check out the agenda.
- Reaction Action: RSVP for the monthly Reaction Action livestreams.
Our community guidelines can be found in our documentation.
Star us on GitHub — it helps!
Interested in participating in the development of Reaction? That's really great! Before you get started, please review our Community Guidelines.
The Reaction Gitter room and forum are good places to engage with core contributors, the community, and to get familiar with Reaction.
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. PRs with smaller scopes are easier 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 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.
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. We also offer Reaction Platform, a managed deployment platform integrated with the Reaction command line.
Copyright © GNU General Public License v3.0