# Page Not Found

The URL `files/kF74bnLOpswkYNmIN7Ss` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Wagon for Takt Planning (BETA) 🚋](https://changelog.visilean.com/changelog/release-2.0-2024/wagon-for-takt-planning-beta.md)
- [Attendance Module: History and Comments!](https://changelog.visilean.com/changelog/release-7.0-2024/attendance-module-history-and-comments.md)
- [Accessibility For Takt Visualiser](https://changelog.visilean.com/changelog/release-4.0-2024/accessibility-for-takt-visualiser.md)
- [Milestone Tasks are now in Takt Visualiser](https://changelog.visilean.com/changelog/release-3.0-2024/milestone-tasks-are-now-in-takt-visualiser.md)
- [GeoTIFF Overlay in Maps](https://changelog.visilean.com/changelog/release-3.0-2026/geotiff-overlay-in-maps.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://changelog.visilean.com/changelog/release-2.0-2024/wagon-for-takt-planning-beta.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://changelog.visilean.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://changelog.visilean.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., `/changelog/release-2.0-2024/wagon-for-takt-planning-beta.md`).

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