---
title: What to read next
description: "Where the documentation goes after the tutorial: how-to guides, model requirements, the examples, and the ClikaRT docs underneath."
---

You installed the archive, fetched a model, served it, and ran it from C++. The rest of the documentation, in a useful reading order:

- **[How-to guides](../how-to/index.md)**: problem-oriented recipes past the tutorial, from picking a GGUF quantization to running with no network at all. [Additional examples](../examples.md) sit inside it: the standalone example programs, from the catalog probe to an in-process server.
- **[Your own models and nodes](../how-to/register-your-own-family.md)**: the how-to group for bringing your own architecture, from the full registration contract to [composing your own pipeline node](../how-to/add-a-pipeline-node.md).
- **[Model requirements](../model-requirements.md)**: the memory and device figures per model variant, for sizing a deployment before you fetch anything.
- **[ClikaRT](/clikart)**: the runtime underneath. Its tutorial explains tensors, devices and the async model the pipelines run on; its API reference covers every public name your C++ program touches; its [system requirements](/clikart/system-requirements) are the platform authority.