Blog Sections Open
Rethinking System Settings for More Editable Projects
A cleaner approach to site-specific system variables that avoids writing one-off plugins for every small editable setting.
Many projects need editable variables such as working hours, account settings, support numbers, or business rules. Hard-coding them in templates works at first, but becomes painful as soon as editors need to change them without developer help.
Why This Topic Matters
- site-specific settings should stay editable
- copy-pasting custom plugins for every project does not scale
- centralized settings make deployment and maintenance safer
The right answer is usually a consistent settings mechanism rather than another project-specific hack. Even in older Evolution CMS sites, treating configuration as managed data pays off quickly.
Source: original community announcement.
What Power Users Would Still Simplify in the Evolution CMS Manager
A reflection on which manager functions felt unnecessary or overly heavy, and why backend simplification was an important part of long-term Evolution CMS usability.
EVO Store: The First Repository for MODX Evolution
Why the first dedicated Evolution repository mattered and how it changed the way extras, updates, and package discovery could work.