Contributing to Tango
Tango grows through contributors who improve the framework, sharpen its public contracts, and make the documentation easier to learn from. Whether you want to fix a bug, improve an example, refine a package README, or help maintain release workflows, the contributor documentation below is the place to begin.
The contributor guides currently focus on the workflows that already exist in the repository: code contributions, documentation contributions, maintainer topics, and maintainer how-to guides.
Getting started
Start with Contributor setup. It explains how to get a local checkout building, how to run the repository validation suite, and what tools are expected for day-to-day maintenance work.
If you are new to Tango's internals, these pages are a good next stop after setup:
Work on Tango
There are two main ways to contribute directly to the framework.
Contributing code
Code contributions include runtime behavior, public APIs, examples, tooling, tests, and release-related maintenance. The code contribution guide walks through the normal path from choosing a change to opening a pull request, including testing expectations and documentation follow-through.
- Contributing code
- Contributor topics
- Architecture decisions
- Contributor how-to guides
- Releasing packages
Contributing documentation
Documentation work includes the Tango documentation site, package READMEs, contributor guides, and other public technical prose. The documentation guide explains how the docs are organized, how to run VitePress locally, and how documentation changes fit into the normal pull request workflow.
Maintainer reference
Some contributor pages are most useful once you already know the area you are changing and need architectural context or a procedure you can follow step by step.