> For the complete documentation index, see [llms.txt](https://cloudflarepurgedocs.umbhost.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cloudflarepurgedocs.umbhost.net/umbhost.cloudflare.purge-documentation.md). # UmbHost.Cloudflare.Purge Documentation Documentation for the Cloudflare CDN purging package from UmbHost UmbHost.Cloudflare.Purge is a package which allows your editors to purge the Cloudflare CDN right from within the Umbraco CMS backoffice. The cache can be purged from the following locations: Dashboard -> There is a custom dashboard which can purge all or custom URLs\ Content Tree -> You can purge individual content items right from within the node tree\ Media Folder Tree -> You can purge all child media items from the media folder node tree\ Media Folder Item -> You can purge an individual media item from the node tree --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://cloudflarepurgedocs.umbhost.net/umbhost.cloudflare.purge-documentation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.