# Page Not Found

The URL `example-usage/understanding-community-assets` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Saving Community Assets](https://digital-commons.gitbook.io/landexplorer-user-guide/example-usage/saving-community-assets.md)
- [Fighting For Housing Justice](https://digital-commons.gitbook.io/landexplorer-user-guide/example-usage/fighting-for-housing-justice.md)
- [Getting Started](https://digital-commons.gitbook.io/landexplorer-user-guide/functionality/getting-started.md)
- [Creating a Map](https://digital-commons.gitbook.io/landexplorer-user-guide/functionality/creating-a-map.md)
- [User Settings](https://digital-commons.gitbook.io/landexplorer-user-guide/functionality/user-settings.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://digital-commons.gitbook.io/landexplorer-user-guide/example-usage/saving-community-assets.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://digital-commons.gitbook.io/landexplorer-user-guide/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://digital-commons.gitbook.io/landexplorer-user-guide/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., `/landexplorer-user-guide/example-usage/saving-community-assets.md`).

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