> For the complete documentation index, see [llms.txt](https://salsa-digital.gitbook.io/govcms-site-builder/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-site-builder/unit-4-taxonomy-categorising-content/editorial-considerations.md).

# Editorial considerations

Content editors/authors will spend about 80% of their time on 20% of tasks. Find out what these common tasks are. Think about the CMS’s audience and find out about their goals and needs.

Make sure you give the content team permissions for:

* "Use contextual links"
* “Access GovCMS Media Editor Browser pages”
* “Access GovCMS Media File Browser pages”
* “Access GovCMS Media Image Browser pages”
* “Access Image browser pages”
* “Access the Files overview page”
* “Use the administration pages and help”
* “Use the toolbar”
* “Use the site in maintenance mode”
* "View the administration theme"
* modules to users who maintain the site


---

# 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-site-builder/unit-4-taxonomy-categorising-content/editorial-considerations.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.