Frequently Asked Questions about MODX CMS

Is MODX extendable? We want to add bespoke features as well as customize both the front and back end of our clients’ websites.

  • MODX was architected from the ground up to be modular and extensible. In fact, those principles are its namesake (MODular/eXtensible)
  • The upgrade path of the MODX core software is maintained no matter how customized a particular implementation becomes, because the framework encourages — almost enforces, by way of architecture — any add-on components to be developed in modular, namespaced, object-oriented fashion. Anything can be achieved in MODX, with its easy-to-use API, without “hacking the core” whatsoever.

Does MODX support multi-lingual, multi-site deployments? We need to share assets between sites, as well as create bespoke content for each individual site, and syndicate a given piece of content over multiple sites and client apps.

  • This is achievable with “Contexts” — an object in MODX that handles multiple sets of overriding global settings, initializing what can be presented on the front end as completely independent web properties that are nevertheless managed in one CMS deployment.

Can MODX handle high traffic loads and comply with our security policies (this may require core modifications)

  • Core mods aren’t necessary in MODX. It can be extended to do as you please. MODX has passed Federal and third party security audits and is constantly updated to patch any known security issues.
  • Scalability is only dependent on the custom codebase, integration work, and deployment. The MODX Professional Services team have architected, supported, and deployed highly scalable solutions capable of handling thousands of concurrent users and beyond, for some of the most demanding websites on the Internet.

Can we control permissions at a granular level with MODX?

  • The MODX core software features a highly configurable, attributes-based access control system. With user groups, roles and access control lists (ACLs), site owners and developers can control permissions for any user interacting with the system, over countless touch points, on both the front-end website and back end admin area.

Does MODX support publishing workflows?

  • Publishing and un-publishing privileges can be managed per User/Role using ACLs.
  • An example workflow may be that an author with save and edit permissions, but not publishing permissions, will upload new content, and an editor with publishing permissions must review before marking the content as published, making it visible to the world.

What are the available commercial support options for commercial projects, custom development, and consultation?

  • Custom development hours are available on a retainer basis from the MODX Professional Services team
  • Emergency support and ongoing maintenance plans are also available as part of MODX’s tiered Service Level Agreements (SLAs)