# Page Not Found

The URL `unit-9-using-taxonomy-to-categorize-content-and-media/taxonomy-and-vocabulary` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Lists and tables](https://salsa-digital.gitbook.io/govcms-content-administration/rich-text-editing-with-ckeditor-5/lists-and-tables.md)
- [Content admin form](https://salsa-digital.gitbook.io/govcms-content-administration/understanding-content/content-admin-form.md)
- [Adding field data](https://salsa-digital.gitbook.io/govcms-content-administration/creating-editing-and-archiving-content/adding-field-data.md)
- [Logging out](https://salsa-digital.gitbook.io/govcms-content-administration/logging-in-2fa-and-the-admin-interface/logging-out.md)
- [Content moderation and workflow](https://salsa-digital.gitbook.io/govcms-content-administration/workflows/content-moderation-and-workflow.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://salsa-digital.gitbook.io/govcms-content-administration/rich-text-editing-with-ckeditor-5/lists-and-tables.md?ask=<question>&goal=<user_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 `build a script that syncs our docs to a CMS` 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.

### Option 2 — Browse the documentation index

Full index: https://salsa-digital.gitbook.io/govcms-content-administration/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://salsa-digital.gitbook.io/govcms-content-administration/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/govcms-content-administration/rich-text-editing-with-ckeditor-5/lists-and-tables.md`).

You may also use `Accept: text/markdown` header for content negotiation.