# Page Not Found

The URL `display/EKB/2019-01-07+Engage+2.26.0+-+Caliper+1.1+in+Engage` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [2.26.0](https://resources.unizin.org/products/content/unizin-engage/release-notes/2019-01-07-engage-2.26.0-caliper-1.1-in-engage.md)
- [2.26.8](https://resources.unizin.org/products/content/unizin-engage/release-notes/2019-02-22-engage-2.26.8-text-to-speech-tts-in-epub-for-engage.md)
- [2.20.5](https://resources.unizin.org/products/content/unizin-engage/release-notes/2017-08-02-engage-2.20.5-accessibility-update.md)
- [2.18.0](https://resources.unizin.org/products/content/unizin-engage/release-notes/2016-09-22-engage-2.18.0-maintenance-release.md)
- [2.22.0](https://resources.unizin.org/products/content/unizin-engage/release-notes/2018-06-29-engage-2.22.0-accessibility-enhancements.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://resources.unizin.org/products/content/unizin-engage/release-notes/2019-01-07-engage-2.26.0-caliper-1.1-in-engage.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://resources.unizin.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://resources.unizin.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/content/unizin-engage/release-notes/2019-01-07-engage-2.26.0-caliper-1.1-in-engage.md`).

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