Concepts

cacheOptimizer as a targeted solution for a MODX architectural limitation that manifested on websites with tens and hundreds of thousands of resources.

modImporter as a universal import layer focused not on a specific store, but on standard MODX objects and processors.

modMonitor as a diagnostic tool for complex MODX projects and troubleshooting based on actual system behavior.

History and philosophy of shopModx: compact business logic, extension of standard MODX mechanisms, and gradual code base simplification as it evolved.

modxSite as a logical layer between MODX data and a replaceable frontend, suitable for invocation from PHP, templates, and external requests.

modxSmarty as a replaceable presentation layer over MODX and an evolution of the phpTemplates ideas.

How phpTemplates separated developers from the internal MODX parser and paved the way for the transition to modxSmarty.

Gradual and controlled migration of an existing website from MODX to a modern tech stack.

Why MODX should be viewed as a legacy platform today: release history, MODX 3, architectural stagnation, and the consequences for website owners.

How Nikolay Savin's public image relates to his actual role in modx.pro, MiniShop, and the Russian-speaking MODX community — and why this matters not only to developers, but also to end-business owners.

Why modx.pro today serves its own commercial ecosystem first and foremost, rather than strong programmers and end businesses.

What we fundamentally do not offer to MODX site owners and why.