Docs-as-Code Without the Complexity
Docs-as-code brings structure and version control alongside engineering workflows — but it can also create barriers for cross-functional collaboration. In this session, we’ll explore how to preserve its strengths while making documentation accessible to the entire team, keeping Git-powered workflows intact behind the scenes and collaboration seamless in one centralized system.
About the session#
Treating documentation like software — without making it harder to contribute.
Docs-as-code has become a widely adopted approach for modern documentation teams. By storing documentation in repositories, reviewing changes through pull requests, and publishing via CI/CD pipelines, teams can align documentation more closely with product development.
But as organizations grow beyond engineering, friction often appears.
When documentation workflows depend entirely on Git-based tooling, non-technical contributors can feel excluded. Collaboration shifts into pull requests. Publishing becomes pipeline-dependent. What began as a powerful alignment strategy can unintentionally become a contribution bottleneck.
In this session, we’ll explore how to preserve the strengths of docs-as-code — version control, structured validation, and release alignment — while removing unnecessary complexity for cross-functional teams.
Rather than debating whether docs-as-code is right or wrong, we’ll introduce a hybrid model that keeps technical precision in place while making collaboration accessible to everyone involved in documentation.
What you’ll learn#
- What docs-as-code actually means, in practical terms
- Why engineering teams adopted it in the first place
- Where friction tends to appear as teams scale
- How hybrid documentation workflows balance rigor and accessibility
- How Git-powered workflows can operate in the background without gating contribution
Who should attend#
This session is ideal for:
- Technical writers working with engineering-heavy teams
- Engineering leads evaluating documentation workflows
- Product managers collaborating on documentation
- Teams considering docs-as-code adoption
- Organizations looking to reduce documentation friction
Whether you’re fully committed to docs-as-code or simply exploring modern documentation practices, this session will help you clarify what model best supports your team.
About the speaker#
Armando Salazar is a Documentation Success Manager at Archbee with a background in technical communication and information architecture. He works with cross-functional teams to design documentation workflows that balance structure, collaboration, and scalability. His focus is helping organizations centralize knowledge while reducing unnecessary complexity in the documentation lifecycle.
Join 3,000+ Teams Using Knowledge Portals as the #1 Resource to Answer Team & Customer Questions
Answer questions instantly with AI powered by your documentation.