---
title: "Introduction to documentation | Writers' Toolkit documentation"
description: "Learn about how Grafana Labs manages technical documentation."
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

# Introduction to documentation

Grafana Labs keeps technical documentation alongside the project code it documents.

Some open source projects and their repositories are:

- Grafana: [https://github.com/grafana/grafana](https://github.com/grafana/grafana)
- Grafana Alloy: [https://github.com/grafana/alloy](https://github.com/grafana/alloy)
- Grafana k6: [https://github.com/grafana/k6-docs](https://github.com/grafana/k6-docs)
- Grafana Loki: [https://github.com/grafana/loki](https://github.com/grafana/loki)
- Grafana Mimir: [https://github.com/grafana/mimir](https://github.com/grafana/mimir)
- Grafana Pyroscope: [https://github.com/grafana/pyroscope](https://github.com/grafana/pyroscope)
- Grafana Tempo: [https://github.com/grafana/tempo](https://github.com/grafana/tempo)

Each repository contains a `docs/sources` directory containing documentation source files.

## Topic-based authoring

The Grafana Labs documentation team uses topic-based authoring. Topic-based authoring is a modular approach to content creation where content is structured around topics that can be mixed and reused in different contexts.

For more information on topic types, refer to [Topic types](/docs/writers-toolkit/structure/topic-types/).

Why is topic-based authoring important?

- **Writing that isn’t topic-based is difficult to reuse.**
  
  If everyone copies information to multiple locations and makes small modifications, the result is rework and increases in errors, which multiplies the costs associated with maintenance and translation.
- **Writing that isn’t topic-based is difficult for readers to understand.**
  
  Content, structure, terminology, and writing style differs and can confuse and frustrate readers.
- **Writing that is topic-based is more consistent and user-friendly.**
  
  Users can find the information they’re looking for quickly and easily. It has a more consistent format and voice, clearly defining the Grafana Labs brand.

## Markdown

Grafana Labs writes technical documentation using Markdown. For more information, refer to the Markdown style guide in [Markdown guide](/docs/writers-toolkit/write/markdown-guide/).

## Ways to contribute

You can contribute content in the following ways:

- [Send an email to the Grafana Documentation team](/docs/writers-toolkit/contribute/#email-docsgrafanacom)
- [Suggest an edit in GitHub](/docs/writers-toolkit/contribute/#suggest-an-edit-in-github)
- [Develop a new topic](/docs/writers-toolkit/contribute/#develop-a-new-topic)

## Join the community

For general discussions about documentation, you’re welcome to join the [#docs](https://raintank-corp.slack.com/archives/C5PG2JK8W) channel on the public Grafana Labs Slack workspace.