Mark Hamstra

I'd just like to debunk this FUD, cause that's what it is. EVO is now a community supported CMS and a new release is actually in the works by maintainers of several now-dead forks. If it was killed, the download wouldn't be available on the MODX website today. But with limited resources there's no way MODX LLC can actively develop and support 2 major CMSs and while I don't want to claim that the Evo to Revo transition was handled properly, saying that a "kill switch" was pulled on Evo is simply wrong. Slowed down and focused on Revo, yes, killed, no. I don't agree there's difference between an Evo and Revo user profile either. As for MODX 3.0... it will be a continuation of Revolution, but taking a step back and looking at what it is that still attracts people to Evo and what people are asking for, and incorporating that into Revo. Speedier & slimmer core. Content elements instead of resources and TVs. Easier manager customisation. Easier ACLs. There will be no "kill switch" pulled on Revo when 3.0 as we've never done that. It'll be deprecated (as any old version is), but that doesn't mean you're out of luck if you need help with it, and I'm sure there'll still be a couple of maintenance and security releases as needed. The beauty of MODX 3 is that it will be the first time that, following semver rules, actual breaking changes can be introduced since the release of Revo in 2010. And 3.0 will become the priority this year and you'll hear lots more about it after we release 2.2.7. Aaaaaaaaanyway, kinda off-topic here, sorry for that. Yes, you should make friends with ProcessWire because frankly it's a kick-ass CMS with a great community. I'm sure it's very scalable because of the way it is architected (I bet there's a thing or two we could learn from PW for MODX too!) and from what I've seen it's quite extensible too in case you need to move beyond it's core features.