Reference
Reference docs are for looking things up after you already know what part of Routa you are working with.
Public Lookup
These are the reference pages most readers should reach first:
Product Specs
Use this when you need route, endpoint, or API surface inventory rather than narrative docs.
Providers & Models
Look up supported providers, model configuration, and specialist setup.
Resources
Open the curated link hub when you already know the area and want deeper supporting material.
Maintainer References
These are useful when you are operating the repository or shipping Routa itself:
Release Guide
Maintainer release flow, package distribution, and publication steps.
Code Style
Implementation and testing conventions for repository changes.
Contributing
Branch, PR, and contribution expectations for Routa itself.
Repository Map
Fast path-to-purpose inventory for repository areas.
What Belongs Here
Reference material answers questions like:
- what routes and endpoints exist?
- what specialists are built in?
- how does the release process work?
- what stable public or repository-facing documents should be looked up directly?
Use Another Section Instead
If you are still deciding where to start or how to use the product, these sections are usually better entry points:
- Getting Started for onboarding and first-run choices
- Use Routa for product workflows
- Developer Guide for configuration, hosting, and deeper technical setup
- Design Docs for durable implementation intent
If you are still deciding where to start, go back to Getting Started or Quick Start.