> For the complete documentation index, see [llms.txt](https://salsa-digital.gitbook.io/govcms-content-administration/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://salsa-digital.gitbook.io/govcms-content-administration/unit-3-managing-content-in-govcms/archive-content.md).

# Archiving content

{% embed url="<https://vimeo.com/488354549>" %}

In GovCMS sites (as with most websites), content administrators will, from time to time need to **remove** content from their site. There are many cases in which conent may need to be removed, including *Events* that have passed, *Blog articles* or *News & Media* that no longer need to be highlighted on a site, expired job listings and so on.

Archiving content in GovCMS simply **unpublishes** the content. It does not delete the content. As such you can restore the content if needed.

The outcome of archiving any content is that it is **no longer visible to site visitors**. Should a site visitor navigate directly to the page that was previously available, they would receive an 'Access denied' message, as demonstrated in the next exercise.


---

# 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://salsa-digital.gitbook.io/govcms-content-administration/unit-3-managing-content-in-govcms/archive-content.md?ask=<question>&goal=<endgoal>
```

`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.