# Page Not Found

The URL `spaces/8N1IA5a0lqRClKT5eQQ7/pages/XyzIBDopSGVYh1b2kEhx` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Managing the Discovery Process](https://community.threekit.com/getting-started/managing-your-implementation/managing-the-discovery-process.md)
- [Republish Items](https://community.threekit.com/tools/general-apps/republish-items.md)
- [What is a Quality Workshop?](https://community.threekit.com/getting-started/managing-your-implementation/what-is-a-quality-workshop.md)
- [User Stories](https://community.threekit.com/getting-started/implementation/user-stories.md)
- [Usage of Shadows With AO & SSAO](https://community.threekit.com/learn/workflows/best-practices/usage-of-shadows-with-ao-and-ssao.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://community.threekit.com/getting-started/managing-your-implementation/managing-the-discovery-process.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://community.threekit.com/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://community.threekit.com/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., `/getting-started/managing-your-implementation/managing-the-discovery-process.md`).

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