Blog Sections Open
Choosing an E-commerce Module for MODX Evolution
An ecosystem decision note for teams choosing an Evolution CMS commerce stack instead of defaulting to the first familiar package.
There has never been one universal commerce answer for every Evo site. The right module depends on what the business actually needs: simple checkout, complex catalog structure, accounting integration, or a heavier synchronization workflow.
What to evaluate
- How large and dynamic the catalog is.
- Whether 1C or another back-office system must be integrated.
- How much pricing and option logic lives on the frontend.
- How much control editors need over product presentation.
The main lesson is to choose the commerce stack from the workflow outward. A tool that feels fine for a small store may become the wrong fit once external sync, variant logic, or richer product data enters the picture.
bDebug: A Lightweight Debugging Tool for Evolution CMS Projects
Why bDebug mattered as a lightweight debugging aid for Evolution CMS teams who wanted quick visibility into arrays, session data, and query behavior.
eFilter and the Shift Toward Automatic TV-Based Filtering
Why eFilter mattered as an Evolution CMS approach to automatic filtering over TV-driven product data and richer catalog parameters.