A discussion covering the question of persistence in the next releases of MODX and current progress on relevant initiatives.
What success MODX has achieved over the past ten years is, in my opinion, entirely due to two core tenets that the community has always stood behind. Those ideals are modularity and extensibility.
It’s been over 10 years since Ryan, Raymond, and myself founded the MODX CMS project and a lot has changed in the world of both content management and web development in that time.
JetBrains—the makers of IntelliJ IDEA—have unsurprisingly created the only PHP development environment worth paying for a license of.
Developed from the technology behind MODX Cloud's snapshot features, Teleport is an extensible scripting toolkit that features some very powerful packaging tools for creating distributions of all or part of a MODX site.
Winner of 2013 People's Choice and 2012 Critic’s Choice for Best Open Source CMS, MODX is a powerful and flexible content management system that molds itself to your design. MODX is creative freedom. Find out why CMS Critic and countless others around the world choose MODX.
I knew there had to be a simple, efficient, and effective way to build nested menus using getResources instead of Wayfinder, and I finally figured out a way. With this discovery, I'll likely never use Wayfinder again.
There are a number of benefits to using xPDO instead of writing SQL directly against the database.
A new feature in MODX 2.2 allows Elements to define if tags in default property and property set values are pre-processed. This allows values provided to Elements in this way to use tags in values that are processed before being used by the Element, the same way it would be if the tags appeared directly in the Element tag string.
In an effort to remove the dependency on Ant, the Java-based build tool we have been using to build, test, and produce distribution packages of MODx Revolution, I spent the last week learning Phing, refactoring the xPDO and MODx Revolution build processes to use it, and writing a custom Phing Task to handle our YUICompressor requirements.