The Doc Landscape
Navigating documentation in a living knowledge system
A reference platform for technical writers navigating documentation in a living knowledge system — across evolving systems, modern software teams, and AI-driven software environments.
The Living Knowlede System
Most documentation problems aren’t writing problems. They’re system problems: decisions that never got documented, evergreen content becoming outdated without anyone noticing, feedback loops that don’t exist.
The Living Knowledge System maps the full knowledge architecture that documentation lives within: its lifecycle stages, knowledge tiers, audiences, and the places where knowledge quietly breaks down. This series is for technical writers and documentation engineers thinking about documentation at the level of architecture, not just content.
Writing for Retrieval Systems
Writing for Retrieval is a focused series for writing and structuring documentation that can be found, chunked, retrieved, and reused by search and AI systems.
It explores how retrieval changes documentation quality: headings carry more weight, sections need enough context to stand on their own, metadata becomes operational, and stale or duplicated content becomes harder to hide.
The goal is not to turn technical writers into machine learning engineers. It’s to help documentation practitioners understand how retrieval systems use content, why they fail, and what documentation needs to support trustworthy answers.
Writing About AI
Writing About AI is a focused series for documenting AI-enabled products and features. It helps you account for systems that behave variably and respond to context rather than fixed inputs.
Instead of treating AI as one thing, the series breaks features down by behavior so you can set expectations, support onboarding, and write documentation users trust when outcomes aren’t fully predictable.
From the Reflections blog
- How Spec-Driven Development Can Benefit Documentation Work
Spec-driven development can help documentation even if the spec is not maintained after release. Its value is in the development window, when product intent is clearer, more structured, and easier to use. That can give technical writers better source material and a chance to clarify gaps earlier, while documentation engineers can use the structure to improve handoffs, checks, and workflows.
- The State of Docs, August 2026
Technical writers are facing a weak hiring market at the same time that employers are expanding what they expect from documentation roles. AI is making content production cheaper, while skills around APIs, automation, retrieval, evaluation, governance, and documentation infrastructure are becoming more valuable. The work isn’t disappearing, but the traditional “technical writer” role is getting harder to separate from the systems that create, verify, and use documentation.
- How to Choose a CCMS Based on Your Documentation Needs
There is no universally “best” CCMS. Different documentation platforms are designed around different assumptions about structure, governance, collaboration, publishing, maintenance, and scale. A system that works well for support-oriented knowledge sharing may become painful for complex product documentation over time, while a heavily structured platform may create unnecessary overhead for smaller or simpler documentation environments. The real question isn’t which platform has the most features, it’s whether the platform matches the actual documentation environment your organization is building.
Technical Writing Best Practices
If you’re working in complex or rapidly changing software environments, view with Technical Writing Best Practices. This series focuses on the foundations (clarity, structure, terminology, and maintainability) that make documentation reliable over time, especially when systems evolve and knowledge is reused across teams and tools.
Who this platform is for
This platform is for you if you:
- Document traditional or AI-enhanced software systems
- Work on documentation structure, reuse, and lifecycle
- Design content for clarity, onboarding, and trust across teams and tools