# About the documentation

How the usual neXt publishes and maintains product documentation, technical explanations and workflow guidance, and how to report a correction.

Canonical: https://docs.theusualnext.com/en/about/
Updated: 2026-10-22
Publisher: the usual neXt

This is the documentation centre for **the usual neXt**. Product collections bring together setup, daily use and troubleshooting. Technical guides explain concepts that can also help when planning a project or working with other tools.

## Which documentation is available?

The [TholusOS collection](/en/tholusos/) covers media playback, scheduling, projector calibration, guided school experiences, games, settings and MCP authoring. Each collection has its own overview and navigation so you can stay within the product you are using.

The [software catalogue](https://www.theusualnext.com/en/apps) lists applications and availability. The [company website](https://www.theusualnext.com/en) describes services and projects. Follow those pages for enquiries about products or services whose documentation is not yet available here.

## How are instructions checked?

Product instructions are reviewed against the relevant implementation and available interface. Each guide describes prerequisites, expected results and the conditions that affect a workflow. The [TholusOS version and verification notes](/en/tholusos/about/) explain the coverage of that collection.

Technical explanations link to primary sources near the claims they support. Worked examples illustrate a method; they are not measurements of your equipment. For an installation, confirm behaviour on the software version, connected devices and physical space you intend to use.

## How do updates and languages work?

Each guide carries a review date. Changes to a workflow are reflected in its steps, prerequisites and troubleshooting. When a page moves, an automatic redirect preserves existing links to its replacement.

English is the first publication language. Translations will receive their own reviewed pages and language navigation when available. Product names, protocol identifiers and filenames remain consistent with the tools they describe.

## How can you report an issue?

Use the [contact page](https://www.theusualnext.com/en/contact) and include the guide URL, product and version, relevant equipment, the step you followed and what happened. A short reproducible description helps distinguish an unclear instruction from a configuration or software issue.

Remove passwords, API keys, tokens and personal information from screenshots or logs. For a school session, describe the classroom setup without identifying pupils.

## How does documentation analytics work?

The usual neXt analytics service measures page visits, reading depth and navigation to help improve these guides. Choosing **Accept complete analytics** also enables anonymous session replay. Choosing **Aggregate measures only** keeps replay off. You can change your choice through **Privacy preferences** in the footer.

Replay masks input fields and excludes sensitive areas. Documentation events record actions such as opening search or copying a code example, without sending the search phrase or copied code as event properties. These docs do not link your browsing to a customer account. Preferences are stored for this documentation subdomain for up to 180 days; choices on the main website are separate. See the [website privacy notice](https://www.theusualnext.com/en/privacy) for company contacts and further information.