Domäne
Documentation
Skill-Profil
Docs-as-Code: MkDocs, Docusaurus, Antora, Markdown, CI/CD for documentation
Rollen
1
wo dieser Skill vorkommt
Stufen
5
strukturierter Entwicklungspfad
Pflichtanforderungen
5
die anderen 0 optional
Documentation
Docs-as-Code
17.3.2026
Wählen Sie Ihr aktuelles Level und vergleichen Sie die Erwartungen.
Die Tabelle zeigt, wie die Tiefe von Junior bis Principal wächst.
| Rolle | Pflicht | Beschreibung |
|---|---|---|
| Technical Writer | Pflicht | 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. |
| Rolle | Pflicht | Beschreibung |
|---|---|---|
| Technical Writer | Pflicht | 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. |
| Rolle | Pflicht | Beschreibung |
|---|---|---|
| Technical Writer | Pflicht | 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. |
| Rolle | Pflicht | Beschreibung |
|---|---|---|
| Technical Writer | Pflicht | 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. |
| Rolle | Pflicht | Beschreibung |
|---|---|---|
| Technical Writer | Pflicht | Shapes long-term documentation platform strategy: technology selection, roadmap development, integration with developer ecosystem. Determines investments in documentation infrastructure and custom tooling. |