Domain
Documentation
Skill Profile
Docs-as-Code: MkDocs, Docusaurus, Antora, Markdown, CI/CD for documentation
Roles
1
where this skill appears
Levels
5
structured growth path
Mandatory requirements
5
the other 0 optional
Documentation
Docs-as-Code
3/17/2026
Choose your current level and compare expectations. The items below show what to cover to advance to the next level.
The table shows how skill depth grows from Junior to Principal. Click a row to see details.
| Role | Required | Description |
|---|---|---|
| Technical Writer | Required | Knows main docs-as-code tools: MkDocs, Docusaurus, Sphinx, Hugo, Jekyll. Can set up a basic documentation site from a template. Writes documentation in Markdown, knows reStructuredText basics. |
| Role | Required | Description |
|---|---|---|
| Technical Writer | Required | Confidently works with 2-3 docs-as-code frameworks. Configures navigation, search, versioning, custom components. Uses MDX/RST extensions, plugins for diagrams, code highlighting. Integrates docs build into CI/CD. |
| Role | Required | Description |
|---|---|---|
| Technical Writer | Required | Designs docs-as-code infrastructure for large projects: monorepo docs, cross-project navigation, custom plugins. Develops custom components (interactive API explorer, live code playground). Optimizes build performance and SEO. |
| Role | Required | Description |
|---|---|---|
| Technical Writer | Required | Defines docs-as-code strategy and standards for the organization. Selects the toolchain, defines docs platform architecture. Coordinates migration from legacy wiki (Confluence) to docs-as-code approach. Trains teams on tools. |
| Role | Required | Description |
|---|---|---|
| Technical Writer | Required | Shapes long-term documentation platform strategy: technology selection, roadmap development, integration with developer ecosystem. Determines investments in documentation infrastructure and custom tooling. |