TechDocs: Spotify's Docs-Like-Code Solution for Backstage
TechDocs exists to bridge the gap between code and documentation, allowing engineers to write their documentation in Markdown files alongside their code. This integration not only streamlines the documentation process but also ensures that the documentation is always up-to-date with the latest code changes. With little configuration, you can generate a visually appealing documentation site directly in Backstage, enhancing accessibility and usability for your team.
The mechanism behind TechDocs is straightforward. Engineers create Markdown files that live with their codebase, and with the help of the TechDocs Addon Framework, you can extend the base docs-like-code experience. The use of MkDocs plugins allows for a rich reading experience, making documentation not just functional but also engaging. Key components include the @backstage/plugin-techdocs, @backstage/plugin-techdocs-react, and @backstage/plugin-techdocs-backend, which together facilitate the seamless integration of documentation into your Backstage environment.
In production, you should be aware that TechDocs is currently in its alpha stage, but it supports most environments, including CI systems and cloud storage solutions. As you adopt this tool, keep an eye on its evolving capabilities and community contributions. The recommended setup is designed to be flexible, but as with any alpha software, expect to encounter some rough edges as it matures into a stable release.
Key takeaways
- →Utilize Markdown files to keep documentation close to your codebase.
- →Leverage the TechDocs Addon Framework to enhance your documentation experience.
- →Explore MkDocs plugins to enrich the reading experience for users.
- →Integrate @backstage/plugin-techdocs for seamless documentation within Backstage.
- →Stay updated on TechDocs' progress as it evolves from alpha to stable.
Why it matters
In production, having documentation that evolves with your code reduces the friction of keeping teams aligned and informed. This integration fosters a culture of documentation as part of the development process, leading to better project outcomes.
Code examples
@backstage/plugin-techdocs@backstage/plugin-techdocs-react@backstage/plugin-techdocs-backendWhen NOT to use this
The official docs don't call out specific anti-patterns here. Use your judgment based on your scale and requirements.
Want the complete reference?
Read official docsDeploy any app in seconds — no infrastructure config, no DevOps overhead. Instant deployments from GitHub, built-in databases, and automatic scaling.
Start deploying free →Mastering Plugin Development in Backstage's Legacy Frontend
Unlock the potential of Backstage by diving into plugin development with its old frontend system. Learn how to integrate diverse tools into a cohesive Software Catalog, enhancing your platform's capabilities. This article reveals the nuances that can make or break your plugin experience.
Mastering the Backstage Software Catalog: Your Centralized Software Hub
Tired of losing track of your software assets? The Backstage Software Catalog centralizes ownership and metadata, making it a breeze to manage everything from services to data pipelines. Discover how to leverage metadata YAML files for seamless integration.
Building Developer Portals with Backstage: Streamline Your Workflow
Backstage is revolutionizing how teams manage their software ecosystem. With features like the Software Catalog for organizing microservices and TechDocs for documentation, it brings clarity to complex environments. Discover how to leverage these tools effectively in your organization.
Get the daily digest
One email. 5 articles. Every morning.
No spam. Unsubscribe anytime.