Bringing Evolution Development Back to Life

MODX Evolution is the reason MODX exists and is very important to this project, but the core team is focused on Revolution, not the legacy codebase. We do want to improve things for the MODX community dependent on Evo, by finding a mutually beneficial way to enable those interested to continue Evo development.

For it to work, we’ve provided a set of guidelines and standards for the community contributions below. These are the same standards applied for any contributions, whether from the core team or from the Community.

Ownership of the MODX Evolution Repository

Currently, only a few people have the rights to push to the official MODX Evolution repository on GitHub. This serves as a gateway to the community of contributors to submit their contributions from their forks for review and acceptance before being pushed for permanent inclusion in the official, upstream repository.

With the current workload of the MODX Team, it also serves as a barrier. That must change!

To revitalize Evolution-ary progress, we would like to invite those interested to identify and agree upon a single liaison—an Integration Manager to serve as the gatekeeper to the official Evolution repository. This person would be responsible for reviewing, managing and merging Pull Requests and marshalling related tracker issues, according to MODX contribution rules and standards, and would have push access to the official repository.

This is an incredibly important responsibility, and the person the community decides upon for this role needs to adhere to and enforce the contribution rules and standards.

While the quantity of contributions to Evo are enormous, many unfortunately don’t meet the proposed quality or project standards, as outlined below. Many have some great improvements that could be accepted into the project if they were not combined with a number of other unrelated changes that are not acceptable for one reason or another.

Contribution Rules and Standards

For the last 7+ years, we’ve figured out what works and what doesn’t in managing a large Open Source project. The following outlines the key take aways.

The first, and most important contribution rule at MODX is: one Pull Request per feature or bug. This is the one thing that will do the most to alleviate the Pull Request bottleneck that currently exists in MODX Evolution. Here are the reasons why:

  • it is much easier for the Integration Manager to review the code and decide if it should be accepted or rejected
  • it is easier to decide or alter where it can best be integrated for the current release cycle(s)
  • it is easier to un-apply the change post-haste, and without affecting other features or bug fixes, if a problem is found after the integration has been pushed

In addition, each Pull Request must have a corresponding ticket in the MODX Project Tracker for Evolution. See for the current open list of issues.

Other MODX contribution standards which reinforce the MODX philosophy include:

  • The contribution should be as extensible as possible when implementing feature requests
  • The contribution should provide a reasonably seamless upgrade path for existing users of a feature being changed in any way
  • The contribution must not break backwards compatibility:
    • of core API methods
    • of included Extras or their associated API methods
  • The contribution should follow MODX Coding Standards as defined here.
  • All code contributors (this means the author of the commit, not just the integrator) must sign a CLA as described here.

Finally, new feature contributions in Evo should not significantly increase the challenges in providing a migration path from Evolution to Revolution. Though we do not yet provide a direct service or official tool for doing this, it is something the MODX Team is committed to accomplishing. We also think this will help keep the community better-aligned on key goals, preventing duplicated or other wasted effort where possible for both Evolution and Revolution contributors. Additional resources and standards for MODX community contributions can be found here.

Let’s Get Started, Today

Please take a few minutes to review these standards and processes. We consider these essential for anything with the “MODX” label attached—based on our extensive experience leading the project, integrating contributions, and releasing the product. We’re ready and excited to see Evo reinvigorated, and we look forward to handing over the keys to the Community ASAP.

Hi. We’re MODX.

We’re here to help you fix, build and grow fantastic sites. How can we help?

How can we help?

Tell us the general reason for reaching out so we can connect you with the right team.

MODX Diagnostics

MODX’s Open Source software is 100% free for anyone to download and use. As the team behind it for more than a decade, we know it inside, out, and then some.

Like any software, sometimes things break; we can usually fix them very fast. But, we do have to charge for our time to support our families and fund its ongoing development. There are almost an unlimited variety of things that can cause problems, including server upgrades, corrupt files, accidental changes, outdated software, database hiccups and more. We will save you a lot of time and frustration, and get you back in action.

With our MODX Diagnostic service, we determine the source of issues, and often fix them on the spot. For more extensive problems needing more time, like hacked sites or overdue upgrades, we provide additional estimates and guidance. MODX Diagnostics cost $99 for standard business hours support (US Central Time), or $500 for priority, rush or after-hours emergencies.

If you don’t have budget for professional support from the source, you look for answers in the MODX Forums or Documentation, or seek help from MODXers in the Community Slack, or from MODX Professionals near you.

Get Support Now

After submitting this we will contact you to collect any access credentials in a secure support ticket. We look forward to helping restore your site back to full health.

Hi! We’d love to work together.

If you have a simple problem that needs our assistance, please request quick fix help here.

What should we keep in mind?

The project involves:
(select all that apply)
What are you planning?
(select all that apply)

Some other considerations

Specific project information

Commercial Support Customers

Customers with a current Commercial Support agreeement can get help using this form. Learn more about MODX Preferred Support.

Let’s get started

What seems to be the issue?

Contact MODX

We welcome conversations, ideas, inquiries and even the occassional cold sales call, but support and requests about how to use MODX software sent via this form cannot be guaranteed a response. That said, we try to respond to everyone that reaches out to us within two business days.

To report a security issue or file a bug for MODX software, please email security [at] to reach our security team. If you are looking for help with MODX, many times you can find an answer in the MODX Forums or MODX Documentation, from MODXers in realtime at the MODX Community Slack Channel, or from a MODX Professional near you.

How can we help?