Blog Sections Open
Using modExtra as a Starting Point for MODX Package Development
modExtra became a practical learning path because it showed how a real package is assembled, not just how one snippet works.
A practical starting point for many teams is training material and the modExtra package skeleton as a way to understand real package development. That advice still holds up well.
Why modExtra mattered
- it showed a complete package structure instead of isolated examples
- developers could see how
/assets/components/and/core/components/fit together - it gave a realistic entry point into processors, manager widgets, and transport packaging
For developers moving from template-level customization into package development, this was an important step: stop thinking only in terms of chunks and snippets, and start thinking in terms of component structure, build scripts, and maintainable project layout.
Why this still matters
Even if the exact training material evolves, the lesson remains the same: serious MODX or Evolution ecosystem work benefits from a repeatable package skeleton and a workflow that can be versioned, tested, and rebuilt.
Source: Evolution CMS on GitHub.
ddTypograph 2.0 Beta and the Shift Toward Cleaner Editorial Output
A short ecosystem note on ddTypograph 2.0 beta and why output-cleaning utilities remained important for editorial Evolution CMS projects.
Building a Custom Checkbox TV Input in Evolution CMS
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.