#Reaction A commerce platform developed with Meteor and following a reactive design pattern that puts usability and conversions first.
Reaction is a project of Ongo Works. We also have some light reading on our blog, for those curious about who we are. We welcome contributors, issues, comments.
If you are interested in joining our alpha+ testing rounds - please contact us
###Core ideas:
- Fast, clean, and easy to use for end users as well as store owners.
- Full functionality / matching feature sets that you would expect from Magento, Shopify, Spree, etc.
- A focus on marketing - it's easy to have products, order processing and customer records. Translating that to conversions and traffic are often the difficult component.
- Leveraging data from social networks, and Reaction itself to present actionable merchandising data
- Limited separation of administrative functionality and "front end". Same template should be used to edit/create/read views.
- Statistics / event tracking should be built in from the beginning throughout, and provide actionable information.
- As modular as possible so that any package can be customized/overwritten - i.e.: need a special order processing process, then override/extend the default
- Core packages to enable site should be a simple and generic as possible, layering complexity by adding packages through a package store ('app store') approach
- Common marketing and SEO practices should be fundamental core features
- UI/UX should be as intuitive as possible, rethinking traditional methods (adding a product should be as easy as buying one)
- Pages/routes only used when user would potentially share/bookmark
- Realtime synchronization across platforms/browsers
- Cross platform, responsive focus - should work well natively, without native apps.
- Migration paths from existing commerce platforms (Magento, Shopify, BigCommerce)
- reaction-commerce package can be used as a package in any meteor application
- Designer and developer friendly!
- HTML/CSS/Javascript or CoffeeScript knowledge should be sufficient for customization.
- Commercial package and theme development encouraged.
- All contributors should be rewarded. please contact us
###Roadmap & Status: Current status: Unstable, with HEAVY ongoing development! We're now within a few weeks of a point release for testing.
Currently good for contributing/observing progress, testing. It goes without saying that we're constantly refactoring, even things that are functionally done. We will start releasing point versions here when we feel we have reached a reasonable amount of stability for at least the bleeding edge users.
As with all development, some items are ahead of schedule, and some are not.
Our **estimated **timeline:
- Catalog/Product Management - functional
- Cart - functional
- Checkout- functional Milestone 1: Completed (flat-rate shipping calc, paypal pro )
- In progress:
- Milestone 2: Late March 2014 (alpha/point release w/order mgmt workflow, multiple shipping/payment methods,transactional emails)
- Milestone 3: Early Q2 (promotions, hero, cms, search, test cases, stable beta)
- Milestone 4: Late Q2 2014 (migration tools, multiple themes, theme editor, PaaS)
- Goal: PaaS Solution Q2/Q3 2014
Please check our Trello board for current progress
Demo, playground at: Demo/test site
- Use **admin1@ongoworks.com / ongo1 **to test dashboard/admin/editing.
##Prerequisites Install git command line and node.js
##Installation curl https://install.meteor.com | /bin/sh sudo -H npm install -g meteorite git clone https://github.com/ongoworks/reaction.git cd reaction mrt update
##Startup ./bin/run
To reset data and give you a fresh test dataset from private/data
./bin/reset
Browse to http://localhost:3000 and you should see Reaction running (sample data same as on demo site)
Note: Optionally you can run and reset with "meteor" and "meteor reset", but you will not load settings data from configuration files. You would need to save them in your data, or create your own private/data
##Deploying An example of a deployment with password to a meteor.com hosted site using config from settings/prod.json
meteor deploy -P --settings settings/prod.json yourdemosite.meteor.com
If you will be doing any development or deployment, it's best to configure a configuration file so you aren't typing all your account information in every time..
Create settings/dev.json and populate, or copy dev.sample.json (will work with empty configuration values)
cp settings/dev.sample.json settings/dev.json
Example configuration file
{
"baseUrl": "http://localhost:3000",
"filepickerApiKey": "__KEY__",
"googleAnalyticsProperty": "__KEY__",
"facebook": {
"secret": "__SECRET__"
},
"public": {
"isDebug": true,
"facebook": {
"appId": "__APP_ID__"
}
}
}
##Developer Docs Developer docs for new packages at packages/reaction-commerce/README.md