# Page Not Found

The URL `registry-gen-2/developer-zone/registry-ui-widgets-complete-guide-and-reference` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Register Metadata](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/concepts/registry-and-register-metadata.md)
- [Step-by-Step Guide](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/guide-to-building-a-registry.md)
- [Dynamic Registry: A Foundation for Effective G2P Delivery](https://docs.openg2p.org/resources/blogs/dynamic-registry-a-foundation-for-effective-g2p-delivery.md)
- [Set Language Preference](https://docs.openg2p.org/products/registry/registry/_archive/social-registry/features/languages-support/user-guides/set-language-preference.md)
- [Build & Deploy a Registry](https://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/concepts/build-and-deploy-a-registry.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://docs.openg2p.org/products/registry/registry/developer-zone/building-a-registry/concepts/registry-and-register-metadata.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://docs.openg2p.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://docs.openg2p.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., `/products/registry/registry/developer-zone/building-a-registry/concepts/registry-and-register-metadata.md`).

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