> For the complete documentation index, see [llms.txt](https://stateofdocs.com/blog/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stateofdocs.com/blog/state-of-docs-insights.md).

# State of Docs Insights

The State of Docs Report is a comprehensive annual report based on hundreds of survey responses from experts across the documentation industry — bringing together key insights and showcasing all the data.

The 2026 report explores how teams track their docs’ success, the future of the industry, the ongoing impact of AI on creating and consuming documentation, and much more.

Want to become a partner, contribute to the report, or be featured in an interview? Get in touch — we’d love to hear from you!

<p align="center"><a href="https://www.stateofdocs.com/2026" class="button primary">Read the 2026 report</a><a href="mailto:survey@stateofdocs.com" class="button secondary">Get in touch</a></p>

## Latest articles

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><h4>Rethinking documentation for AI agents: A conversation with MongoDB’s Dachary Carey</h4></td><td><a href="/pages/IeSXH1JckebnEgE3wipa">/pages/IeSXH1JckebnEgE3wipa</a></td><td><a href="/files/OED34ObR0g1vDbcXxia8">/files/OED34ObR0g1vDbcXxia8</a></td></tr><tr><td><h4>Building a competitive edge: Why Cloudflare treats docs as a product</h4></td><td><a href="/pages/iFRSaJEo6trOe40rd6ke">/pages/iFRSaJEo6trOe40rd6ke</a></td><td><a href="/files/B5B7KUP5QvaZVQkBS6UQ">/files/B5B7KUP5QvaZVQkBS6UQ</a></td></tr><tr><td><h4>Measuring documentation success: A conversation with Christopher Gales</h4></td><td><a href="/pages/LNaoWMSATVMBk09uyYVX">/pages/LNaoWMSATVMBk09uyYVX</a></td><td><a href="/files/XBlmBmKzOdWXahOCW8eE">/files/XBlmBmKzOdWXahOCW8eE</a></td></tr><tr><td><h4>Reimagining documentation in the AI age: A conversation with Vercel's Lee Robinson</h4></td><td><a href="/pages/Pz43JtUcnUN0PsjwOc5L">/pages/Pz43JtUcnUN0PsjwOc5L</a></td><td><a href="/files/O6LSrdMMeDyntybgBmXY">/files/O6LSrdMMeDyntybgBmXY</a></td></tr><tr><td><h4>Two worlds of documentation: A conversation with Pocus' Alexander Rose</h4></td><td><a href="/pages/2N7N00rEukCXfAkZOxBW">/pages/2N7N00rEukCXfAkZOxBW</a></td><td><a href="/files/XSmy1LXFD3gJONjbwpVu">/files/XSmy1LXFD3gJONjbwpVu</a></td></tr><tr><td><h4>AI-powered documentation support: A conversation with Warp's Danny Neira</h4></td><td><a href="/pages/5sc6Cl3ZLVKJqGADTNTC">/pages/5sc6Cl3ZLVKJqGADTNTC</a></td><td><a href="/files/rEtiU4XV7wFKymvMyDiL">/files/rEtiU4XV7wFKymvMyDiL</a></td></tr><tr><td><h4>Building documentation that converts users to contributors: A conversation with Bekah Hawrot Weigel</h4></td><td><a href="/pages/ZxgT5Qtvkp8TOETLgcdd">/pages/ZxgT5Qtvkp8TOETLgcdd</a></td><td><a href="/files/HdpGdhgNusa0SmgEAumw">/files/HdpGdhgNusa0SmgEAumw</a></td></tr><tr><td><h4>Solo DevRel documentation: A conversation with DuckDB’s Gábor Szárnyas</h4></td><td><a href="/pages/WzVwnqOYR6ajn3n9KvOq">/pages/WzVwnqOYR6ajn3n9KvOq</a></td><td><a href="/files/euPhm0GfQtjtVW6uaqtR">/files/euPhm0GfQtjtVW6uaqtR</a></td></tr><tr><td><h4>Documentation at scale: A conversation with Snowflake’s Rob Gray</h4></td><td><a href="/pages/NFXdHwy8I1WwLuPyS1iR">/pages/NFXdHwy8I1WwLuPyS1iR</a></td><td><a href="/files/1n95pSc5hLSjIne7m7VH">/files/1n95pSc5hLSjIne7m7VH</a></td></tr><tr><td><h4>Open source documentation at scale: A conversation with dbt Labs’ Mirna Wong and Matt Shaver</h4></td><td><a href="/pages/OiPvLJ67gulCBaabnbGa">/pages/OiPvLJ67gulCBaabnbGa</a></td><td><a href="/files/EAv8lkc5Wf33k8vurHlc">/files/EAv8lkc5Wf33k8vurHlc</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://stateofdocs.com/blog/state-of-docs-insights.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.