# Page Not Found

The URL `hc/en-us/articles/9012860970139-2022-17-0-September-22-2022` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [October 20, 2022 - Augmented Reality](https://community.threekit.com/learn/trio-talks/october-20-2022-augmented-reality.md)
- [March 17, 2022 - Treble](https://community.threekit.com/learn/trio-talks/march-17-2022-treble.md)
- [September 15, 2022 - Order of Operations](https://community.threekit.com/learn/trio-talks/september-15-2022-order-of-operations.md)
- [June 16, 2022 - Virtual Photography](https://community.threekit.com/learn/trio-talks/june-16-2022-virtual-photography.md)
- [January 20, 2022 - Modular Configuration](https://community.threekit.com/learn/trio-talks/january-20-2022-modular-configuration.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://community.threekit.com/learn/trio-talks/october-20-2022-augmented-reality.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 `automate deployments from our CI pipeline` 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://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., `/learn/trio-talks/october-20-2022-augmented-reality.md`).

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