# Page Not Found

The URL `files/MABTqg79x6I6P7fQq35a` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [6.2 Guidelines for onboarding](https://twbvoiceplaybook.clearglobal.org/6.-community-engagement/6.2-guidelines-for-onboarding.md)
- [6.1 Identifying contributor profiles](https://twbvoiceplaybook.clearglobal.org/6.-community-engagement/6.1-identifying-contributor-profiles.md)
- [5.2 Guidelines for validation](https://twbvoiceplaybook.clearglobal.org/5.-recording-and-validation/5.2-guidelines-for-validation.md)
- [1.1 How to use this playbook](https://twbvoiceplaybook.clearglobal.org/1.-introduction/1.1-how-to-use-this-playbook.md)
- [8.1 Sharing data on Hugging Face and platform access](https://twbvoiceplaybook.clearglobal.org/8.-access-to-datasets-and-models/8.1-sharing-data-on-hugging-face-and-platform-access.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 documentation index with the `ask` parameter:

```
GET https://twbvoiceplaybook.clearglobal.org/6.-community-engagement/6.2-guidelines-for-onboarding.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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://twbvoiceplaybook.clearglobal.org/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://twbvoiceplaybook.clearglobal.org/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., `/6.-community-engagement/6.2-guidelines-for-onboarding.md`).

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