A decoupled content management system (CMS) separates or decouples the back-end from the front-end of the CMS, enabling the editors, and the publishers, to work in two different applications. The two environments are usually separated through a firewall or have dedicated servers. The system uses an API (Application Programming Interface) to publish content that bridges the two parts.
Due to the separation of the content management and content presentation layers, the decoupled CMS offers higher security, as the back-end will not be compromised if the presentation layer was penetrated through a cyberattack. Another significant benefit of this architecture is that the two applications can scale independently, making the system more easily adaptable to new business requirements.
- Large organizations with multi-language, multi-regional websites
- Content teams that want more independence from developer teams
- Organizations that need the flexibility to separately scale the back-end or front-end as their business grows