> 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/conclusion/key-takeaways.md). # Key takeaways Headless CMS has become increasingly popular in recent years, and there are now numerous resources available to teach developers how to use them effectively. However, a CMS is only one part of a headless platform. Successfully building and implementing a headless platform requires a solid architectural plan that ties together your CMS, tech stack, content workflows, and business objectives and helps you move at the speed of business. The world of web development is constantly changing, and staying abreast of current trends requires an understanding of where the industry is headed. We answer some of the most pressing questions in this guide, and we'll keep it up-to-date with current information most valuable to you. Do you have any questions we didn't get to? [Leave us a comment.](https://rangle.io/insights/headless-cms-playbook) --- # 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/conclusion/key-takeaways.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.