> 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/creating-editing-and-archiving-content/exercise.md).

# Exercise

### Exercise 1

Create a few new pages of content. Make sure that you edit each one a few times, as this creates a revision log that we'll use later.

If you want to add some basic text to help pad out your page, use the handy website [Lipsum](https://www.lipsum.com/feed/html) to provide some placeholder text.

### Exercise 2

Edit a page by accessing the **Content listing page**.

Then edit it again by viewing it and using the **Edit tab** button.

### Exercise 3

Archive a page and try to access it using a different browser or incognito mode. See how it changes.

### Exercise 4

Delete a page and try accessing the URL. You will see a different error message.

### Exercise 5

Use the **Revisions tab** to see the history of your page's changes. View an old revision, compare it against the current revision and then revert it to that old revision.


---

# 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/creating-editing-and-archiving-content/exercise.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.