Documentation engineering
I help teams make documentation easier to use, contribute to, and maintain.
Docs-as-Code consulting, platform engineering, and automation. Work directly with me on architecture, implementation, or an existing system.
What I can help with
Platforms and Docs-as-Code
Shape the content structure, contribution workflow, and platform around your products. Build documentation sites and developer portals with navigation, search, versioning, and review in your repositories.
Automation and references
Generate API and CLI references from maintained sources. Connect preview builds, content checks, and publishing to your release process so your team can review changes before they reach users.
Migrations and improvements
Review the current system, map content and URLs, and plan the move. Implement conversion, validation, redirects, and launch checks. Improve an existing platform when a full migration is unnecessary.
Selected work
ScyllaDB
Documentation tooling across 20+ repositories, including Sphinx extensions and generated API and CLI references.
SNGULAR
Documentation architecture, migration strategy, templates, and writer onboarding across 45+ products.
Inditex
Hands-on codelabs and reusable example repositories to help internal developers adopt the technology stack.
Who I am
I’m David Garcia, a documentation engineer and founder of TechDocs Studio.
I combine software engineering with documentation architecture. My work includes Docs-as-Code migrations, generated references, publishing tools, and learning paths for internal developers. I work directly with your documentation and engineering teams throughout the project.
Working together
We start by reviewing your current platform, content, contributors, and release process. Together, we choose the changes that will make the system easier to use and maintain.
We agree the scope, responsibilities, acceptance checks, and project price before work starts. Your team reviews changes in its own repositories and gets the source, configuration, and instructions to maintain the system.
Technologies
- Docusaurus, Zensical, and GitBook for documentation projects.
- OpenAPI for generated API references.
- Python and TypeScript for tooling and integrations.
- Git and GitHub Actions for review and publishing workflows.