RoboGen: Generating a robots.txt File from Real Site Data During Cleanup Work
Why generating robots rules from known site aliases can be useful during post-hack cleanup, and where that idea becomes risky.
Laravel, AI, MCP, APIs, integrations, and external tooling that matters in modern Evolution CMS work.
Why generating robots rules from known site aliases can be useful during post-hack cleanup, and where that idea becomes risky.
A short ecosystem note on the need for a more convenient filter stack in Evolution-era catalog projects.
A compatibility note on older resource helper libraries that stopped saving documents correctly after upgrading to 1.0.13.
How the aDate snippet evolved to support richer date formatting patterns in Evolution CMS output templates.
An early look at integrating shopModx with 1C for large product imports and future two-way synchronization.
The second practical ElasticSearch note: how to index records, update documents, and think about bulk import workflows when syncing MODX data into search storage.
A practical ecosystem-oriented note on product option grids in miniShop2 and why richer commerce data pushes teams toward more structured product models.
A short ecosystem note on Bootstrap Generator and why layout tooling mattered when teams were assembling Bootstrap-based frontends for MODX projects.
A release-oriented note on ddYMap 1.2 and the improvements it made to map defaults, jQuery integration, and document field handling.
A practical introduction to using ElasticSearch with MODX data, including index creation, mappings, JSON handling, and why search structure matters from the start.
A historical ecosystem note on the early installer direction for MODX Evolution and the effort to make first-time setup less intimidating.
Why many teams moved template editing out of the manager and into an IDE workflow, using file includes, versioning, and diff tools for safer development.
A historical ecosystem note on CacheExtender 0.5 and why cache-control helpers mattered for high-traffic or highly dynamic Evo projects.
A short ecosystem note on ddTypograph 2.0 beta and why output-cleaning utilities remained important for editorial Evolution CMS projects.
How the modExtra training workflow helped developers understand package structure, processors, assets, and transport builds in the MODX ecosystem.
How a custom checkbox-style TV input can be added to Evolution CMS when the standard checkbox field is too limited for the project’s needs.
How to think about Shopkeeper versus miniShop2 when a catalog grows large and the project needs more structured commerce workflows.
A historical ecosystem note on combining MODX Revo, miniShop2, and external inventory systems such as mSklad for more serious commerce 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.
A short ecosystem note on TreeTabs 1.1 and why manager-side navigation helpers remained valuable on larger Evolution CMS sites.