Understanding the Example Storefront
In the past, one developed for Reaction Commerce by creating
plugins and working with the main Reaction repo. This had advantages and disadvantages but some of the main disadvantages were:
- Very slow reload times, especially for making styling changes
- Limited ability to customize without modifying core
- Using Meteor pub/sub, a technology that was unfamiliar to most developers
- Ultra-fast restarts
- Ability to completely customize the look, feel, and layout using standard web devlopment practices
Nothing says that you cannot build your implementation in Angular or Vue or PHP for that matter. However, if you want a head start, the Example Storefront can do that.
On upstream changes
You may or may not care about upstream changes because you are going to throw a lot of it away and start from scratch. Or you may only want to keep the logic part of the code (the containers) and change all the presentation components. How completely you want customize is totally up to you and there is no limit to how you can customize.
The only issue is if you want to bring in upstream changes (bug fixes or new features that get added to the example storefront) This is still always possible but the more you customize the more difficult this will be.
We are doing our best to structure the code so that you can customize some simple things but the more you customize, the harder it will be to update with each release. This tutorial assumes you want to make merging in upstream changes as easy as possible, and we will use techniques that make that easier, and point out where doing something will make that harder.