> For the complete documentation index, see [llms.txt](https://tbw.rangle.io/headless-cms-playbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tbw.rangle.io/headless-cms-playbook/introduction/benefits-of-a-headless-cms.md). # Benefits of a headless CMS A headless CMS offers more flexibility to integrate with a variety of front-end solutions and devices, making it an excellent option for highly scalable and performance-focused websites. Non-technical team members can edit content, optimize for SEO and performance, and use the same content across different channels and touchpoints. ## Why use a CMS? Content management systems (CMS) empower non-technical users to create, manage, and publish content and allow developers to focus on more complex tasks rather than content updates. Role permissioning in a CMS facilitates collaboration among teams by allowing multiple users to work on different parts of the website or content simultaneously while still maintaining control over who can make changes and access sensitive information. When set up correctly, a CMS can also improve SEO and website performance. However, some CMS platforms are expensive, and organizations may not have the skills to build and maintain a CMS. There's a high upfront cost of setting up and migrating content and experiences to the CMS. A CMS also comes with customization and design limitations, and if set up incorrectly, it can contribute to SEO and website performance issues. ## Why go headless? There are some key advantages to going headless: * Non-technical team members can still author and edit content within the CMS * It is JavaScript framework agnostic – developers can build the presentation layer in the tool they are most familiar with * Data can be delivered across multiple different devices and platforms from the same CMS * Highly scalable, especially when using with Jamstack architecture * Separating the data from the visuals allows for easier separation of concerns, and improved security by reducing the potential area of an attack * Headless CMS tools optimize for SEO and performance * Faster editing experience as the platform doesn’t have to deal with rendering the content like in a Headful platform * The same content can be used across all of your different channels and digital touchpoints * Allows you to use performant, cloud-based hosting and build services like Vercel and Netlify --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://tbw.rangle.io/headless-cms-playbook/introduction/benefits-of-a-headless-cms.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.