Blog Sections Open
Planning a Revo Commerce Stack with miniShop2 and mSklad
As projects became more commerce-heavy, teams increasingly looked beyond simple CMS-only stores and toward integrated stacks.
The original note described a planned stack around MODX Revo, miniShop2, and an external inventory or ERP-like system such as mSklad. That combination captured a broader shift in project thinking: once commerce gets operationally serious, stock, catalog, and sales workflows stop fitting neatly inside one CMS-only layer.
Why this matters historically
- miniShop2 represented a more application-like commerce direction
- inventory integration meant the CMS no longer owned every business datum
- the project architecture had to account for synchronization and operational source-of-truth rules
Even for Evolution-focused readers, this kind of post matters because it shows how the broader ecosystem was evolving: content management, commerce logic, and external business systems were becoming separate concerns that needed to work together.
Source: original community announcement.
Shopkeeper vs miniShop2 for Large Catalog Projects
How to think about Shopkeeper versus miniShop2 when a catalog grows large and the project needs more structured commerce workflows.
Understanding modUser and extUser in MODX Projects
A short ecosystem-oriented explanation of why MODX projects distinguish between modUser and extUser style models and what that means for custom account workflows.