This document discusses decoupling content management systems (CMS) by breaking them into independent microservices. It argues that a monolithic CMS architecture holds companies hostage as technologies change and scaling needs evolve. Following a service-oriented architecture (SOA) approach allows splitting a CMS into decoupled services for accounts, APIs, front-ends, and more. Existing protocols and interfaces can facilitate communication between these independent services. Examples of decoupling strategies include using Edge Side Includes for content assembly, message queues for event handling, and the PHP Content Repository specification for a common data interface.