Blog Sections Open
Choosing Between ShopModx, miniShop2, and Shopkeeper
Store architecture choices are never just about features. They are about ecosystem fit, extensibility, and how much custom work a team is prepared to own.
This old comparison asked a question many teams still face in some form: which store stack should power the next project?
The Three Options in the Original Discussion
- ShopModx as a more direct custom-PHP style solution
- miniShop2 in the Revo ecosystem, with stronger integration into newer tooling
- Shopkeeper as the familiar Evolution-oriented path
What the Choice Really Depends On
- whether the project belongs on Evo or Revo in the first place
- how much catalog complexity, filtering, and account logic is needed
- how much of the stack should be reusable instead of custom
- what the team already knows how to maintain
Why This Still Matters
The old thread reflected a broader truth: ecommerce decisions are architectural, not merely plugin-level. A small store, a heavily customized portal, and a reusable product platform do not need the same foundation.
That is why comparisons like this fit best in Ecosystem. They are less about a one-line answer and more about choosing the right platform direction for the project you actually have.
Source: original community announcement. Related docs: modern Evolution commerce docs.
MODx Testing 1.b3: A Feature-Focused Community Build
A historical ecosystem snapshot of a testing build that bundled manager, SEO, and workflow improvements for wider evaluation.
`sizeof`: A Small Evolution CMS Snippet for Human-Readable File Sizes
A tiny helper snippet that reads a file path and outputs a readable file size such as KB or MB instead of raw bytes.