Core roadmap
Last updated Sep 25th, 2026 | Page history | Improve this page | Report an issue
Support the team building MODX with a monthly donation.
The budget raised through OpenCollective is transparent, including payouts, and any contributor can apply to be paid for their work on MODX.
Backers
Budget
$204 per month—let's make that $500!
Learn moreThis page points to live sources for MODX Revolution plans. It is not a fixed feature contract. Milestones and issue assignments change as work lands.
The older docs roadmap (2.5 / planned 2.6 / "3.0 Next") was removed during the docs migration. Restoring a long static feature list here would go stale again.
Where to look¶
| Source | What you get |
|---|---|
| GitHub milestones | Issues and PRs grouped by target release (for example open milestones such as v3.3.0 and v4.0.0) |
Changelog on the 3.x branch |
Merged fixes and notes for the next and recent releases |
| Releases and the MODX blog | What already shipped |
| Issues / Pull requests | Active discussion and review |
| Contributor's guide | Which git branch to target (3.x, patch branches, major next) |
| Community forum | Product discussion (for example threads about release cycle and priorities) |
Compatible Extras for site upgrades: SiteDash extras list.
Current line (3.x)¶
Development for MODX 3 happens on the 3.x branch. Patch and minor releases are cut from that line (and from short-lived patch branches when they exist). See Branches in the contributor's guide.
For breaking changes already in 3.0 and later notes (class aliases, processors, xPDO, modAction), start at Upgrading from 2.x to 3.0.
Documented heads-up for package authors: deprecated global class aliases are expected to stop loading automatically in 3.3. Details: Changed class names.
How to use this¶
- Open the milestones for the release you care about.
- Skim the top of
changelog.txton3.xfor what is already merged. - Treat unmerged issues and empty milestones as intent, not a ship date.
If you maintain Extras or custom code, watch deprecation notices on a current 3.x site and the upgrade docs above before the next minor that removes aliases or APIs.
Support the team building MODX with a monthly donation.
The budget raised through OpenCollective is transparent, including payouts, and any contributor can apply to be paid for their work on MODX.
Backers
Budget
$204 per month—let's make that $500!
Learn more










