Supporters
Huge thanks to all the supporters and contributors that made this report possible
Huge thanks to all the supporters and contributors that made this report possible
Supporters
Contributors
Mira Balani
Staff Technical Writer
Miro
Mira Balani
Staff Technical Writer
Miro
Mira Balani
Staff Technical Writer
Miro
Utsav Banerjee
Senior Manager, Product Language
New Relic
Utsav Banerjee
Senior Manager, Product Language
New Relic
Utsav Banerjee
Senior Manager, Product Language
New Relic
Taylor Bell
Lead Content Engineer
copywriting.dev
Taylor Bell
Lead Content Engineer
copywriting.dev
Taylor Bell
Lead Content Engineer
copywriting.dev
Tido Carriero
Co-Founder
Koala
Tido Carriero
Co-Founder
Koala
Tido Carriero
Co-Founder
Koala
Michael Drogalis
Founder
ShadowTraffic
Michael Drogalis
Founder
ShadowTraffic
Michael Drogalis
Founder
ShadowTraffic
Fabrizio Ferri-Benedetti
Principal Technical Writer
Elastic
Fabrizio Ferri-Benedetti
Principal Technical Writer
Elastic
Fabrizio Ferri-Benedetti
Principal Technical Writer
Elastic
Christopher Gales
Technical Documentation Leader
Christopher Gales
Technical Documentation Leader
Christopher Gales
Technical Documentation Leader
Anna Gasparyan
JetBrains
Anna Gasparyan
JetBrains
Anna Gasparyan
JetBrains
Rob Gray
Senior Technical Writer
Snowflake
Rob Gray
Senior Technical Writer
Snowflake
Rob Gray
Senior Technical Writer
Snowflake
Bekah Hawrot Weigel
Senior Developer Experience and Content Manager
The Linux Foundation
Bekah Hawrot Weigel
Senior Developer Experience and Content Manager
The Linux Foundation
Bekah Hawrot Weigel
Senior Developer Experience and Content Manager
The Linux Foundation
Kim Jeske
Head of Product Content Experience
Cloudflare
Kim Jeske
Head of Product Content Experience
Cloudflare
Kim Jeske
Head of Product Content Experience
Cloudflare
Sasha Maximova
JetBrains
Sasha Maximova
JetBrains
Sasha Maximova
JetBrains
Dalia Molina
Senior Manager, Publishing Platform
Twilio
Dalia Molina
Senior Manager, Publishing Platform
Twilio
Dalia Molina
Senior Manager, Publishing Platform
Twilio
Danny Neira
Support Engineer
Warp
Danny Neira
Support Engineer
Warp
Danny Neira
Support Engineer
Warp
Vinay Antony Payyapilly
Director - Documentation
New Relic
Vinay Antony Payyapilly
Director - Documentation
New Relic
Vinay Antony Payyapilly
Director - Documentation
New Relic
Samy Pessé
CTO
GitBook
Samy Pessé
CTO
GitBook
Samy Pessé
CTO
GitBook
Lee Robinson
VP of Product
Vercel
Lee Robinson
VP of Product
Vercel
Lee Robinson
VP of Product
Vercel
Alexander Rose
GTM Engineer
Pocus
Alexander Rose
GTM Engineer
Pocus
Alexander Rose
GTM Engineer
Pocus
Matt Shaver
Senior Technical Writer
dbt Labs
Matt Shaver
Senior Technical Writer
dbt Labs
Matt Shaver
Senior Technical Writer
dbt Labs
Marco Spinello
Senior Technical Writer
Booking.com
Marco Spinello
Senior Technical Writer
Booking.com
Marco Spinello
Senior Technical Writer
Booking.com
Gábor Szárnyas
Developer Relations Advocate
DuckDB
Gábor Szárnyas
Developer Relations Advocate
DuckDB
Gábor Szárnyas
Developer Relations Advocate
DuckDB
Larry Ullman
Technical Writer
Formerly at Stripe
Larry Ullman
Technical Writer
Formerly at Stripe
Larry Ullman
Technical Writer
Formerly at Stripe
Mirna Wong
Senior Technical Writer
dbt Labs
Mirna Wong
Senior Technical Writer
dbt Labs
Mirna Wong
Senior Technical Writer
dbt Labs
“In some cases, technical documentation has even surpassed marketing websites as the primary driver of product adoption. Why? Because it offers immediate value. A well-written doc doesn’t just describe a product’s features; it shows users how to apply them in their own environment.”
Kim Jeske
Head of Product Content Experience
Cloudflare
“Users want to see relevant information quickly, without needing to search through endless pages. AI chatbots are one solution, but I think a better answer is presenting users with relevant information from the docs right in the product, at the moment they need it.”
Samy Pessé
CTO
GitBook
“Over the past few years, our documentation has evolved into dynamic, user-centric knowledge systems — driven by a powerful combination of AI, automation, real-time feedback loops, and the irreplaceable insight of human expertise.”
Mira Balani
Staff Technical Writer
Miro
“My very subjective hunch is that users are going to consume the docs mainly through chatbots. While the docs must remain accessible in a traditional way — through a website, search, or navigation — the main way to look up something in the docs will be by asking a chatbot to produce an answer based on those docs.”
Marco Spinello
Senior Technical Writer
Booking.com
“I suspect writers will spend more time in two areas. First, as editors, reviewing generated content, managing the AI, verifying technical accuracy, updating, etc. Second, I suspect writers can do more predictive and visionary docs product work.”
Larry Ullman
Technical Writer
Formerly at Stripe
“AI just accentuates all of the existing best practices. Writing good content doesn’t really go anywhere. Actually, it’s even more important because you need to write something that’s accessible to both humans and AIs.”
Lee Robinson
VP of Product
Vercel
“What many docs, in my opinion, get wrong, is that they provide more of the reference API than concrete examples. [At DuckDB] you can open [the reference API] and you have 10-15 ready-to-go examples. People really like that. It’s also great for LLMs because they learn from this more easily than from a reference manual.”
Gábor Szárnyas
Developer Relations Advocate
DuckDB
“In the absence of the documentation, the product doesn't exist. It's a bunch of code packages together with a UI sitting on top, but there are a lot of products which don't have a UI, right? So the role of documentation becomes monumental there.”
Utsav Banerjee
Senior Manager, Product Language
New Relic
“In some cases, technical documentation has even surpassed marketing websites as the primary driver of product adoption. Why? Because it offers immediate value. A well-written doc doesn’t just describe a product’s features; it shows users how to apply them in their own environment.”
Kim Jeske
Head of Product Content Experience
Cloudflare
“Users want to see relevant information quickly, without needing to search through endless pages. AI chatbots are one solution, but I think a better answer is presenting users with relevant information from the docs right in the product, at the moment they need it.”
Samy Pessé
CTO
GitBook
“Over the past few years, our documentation has evolved into dynamic, user-centric knowledge systems — driven by a powerful combination of AI, automation, real-time feedback loops, and the irreplaceable insight of human expertise.”
Mira Balani
Staff Technical Writer
Miro
“My very subjective hunch is that users are going to consume the docs mainly through chatbots. While the docs must remain accessible in a traditional way — through a website, search, or navigation — the main way to look up something in the docs will be by asking a chatbot to produce an answer based on those docs.”
Marco Spinello
Senior Technical Writer
Booking.com
“I suspect writers will spend more time in two areas. First, as editors, reviewing generated content, managing the AI, verifying technical accuracy, updating, etc. Second, I suspect writers can do more predictive and visionary docs product work.”
Larry Ullman
Technical Writer
Formerly at Stripe
“AI just accentuates all of the existing best practices. Writing good content doesn’t really go anywhere. Actually, it’s even more important because you need to write something that’s accessible to both humans and AIs.”
Lee Robinson
VP of Product
Vercel
“What many docs, in my opinion, get wrong, is that they provide more of the reference API than concrete examples. [At DuckDB] you can open [the reference API] and you have 10-15 ready-to-go examples. People really like that. It’s also great for LLMs because they learn from this more easily than from a reference manual.”
Gábor Szárnyas
Developer Relations Advocate
DuckDB
“In the absence of the documentation, the product doesn't exist. It's a bunch of code packages together with a UI sitting on top, but there are a lot of products which don't have a UI, right? So the role of documentation becomes monumental there.”
Utsav Banerjee
Senior Manager, Product Language
New Relic
“In some cases, technical documentation has even surpassed marketing websites as the primary driver of product adoption. Why? Because it offers immediate value. A well-written doc doesn’t just describe a product’s features; it shows users how to apply them in their own environment.”
Kim Jeske
Head of Product Content Experience
Cloudflare
“Users want to see relevant information quickly, without needing to search through endless pages. AI chatbots are one solution, but I think a better answer is presenting users with relevant information from the docs right in the product, at the moment they need it.”
Samy Pessé
CTO
GitBook
“Over the past few years, our documentation has evolved into dynamic, user-centric knowledge systems — driven by a powerful combination of AI, automation, real-time feedback loops, and the irreplaceable insight of human expertise.”
Mira Balani
Staff Technical Writer
Miro
“My very subjective hunch is that users are going to consume the docs mainly through chatbots. While the docs must remain accessible in a traditional way — through a website, search, or navigation — the main way to look up something in the docs will be by asking a chatbot to produce an answer based on those docs.”
Marco Spinello
Senior Technical Writer
Booking.com
“I suspect writers will spend more time in two areas. First, as editors, reviewing generated content, managing the AI, verifying technical accuracy, updating, etc. Second, I suspect writers can do more predictive and visionary docs product work.”
Larry Ullman
Technical Writer
Formerly at Stripe
“AI just accentuates all of the existing best practices. Writing good content doesn’t really go anywhere. Actually, it’s even more important because you need to write something that’s accessible to both humans and AIs.”
Lee Robinson
VP of Product
Vercel
“What many docs, in my opinion, get wrong, is that they provide more of the reference API than concrete examples. [At DuckDB] you can open [the reference API] and you have 10-15 ready-to-go examples. People really like that. It’s also great for LLMs because they learn from this more easily than from a reference manual.”
Gábor Szárnyas
Developer Relations Advocate
DuckDB
“In the absence of the documentation, the product doesn't exist. It's a bunch of code packages together with a UI sitting on top, but there are a lot of products which don't have a UI, right? So the role of documentation becomes monumental there.”
Utsav Banerjee
Senior Manager, Product Language
New Relic
“In some cases, technical documentation has even surpassed marketing websites as the primary driver of product adoption. Why? Because it offers immediate value. A well-written doc doesn’t just describe a product’s features; it shows users how to apply them in their own environment.”
Kim Jeske
Head of Product Content Experience
Cloudflare
“Users want to see relevant information quickly, without needing to search through endless pages. AI chatbots are one solution, but I think a better answer is presenting users with relevant information from the docs right in the product, at the moment they need it.”
Samy Pessé
CTO
GitBook
“Over the past few years, our documentation has evolved into dynamic, user-centric knowledge systems — driven by a powerful combination of AI, automation, real-time feedback loops, and the irreplaceable insight of human expertise.”
Mira Balani
Staff Technical Writer
Miro
“My very subjective hunch is that users are going to consume the docs mainly through chatbots. While the docs must remain accessible in a traditional way — through a website, search, or navigation — the main way to look up something in the docs will be by asking a chatbot to produce an answer based on those docs.”
Marco Spinello
Senior Technical Writer
Booking.com
“I suspect writers will spend more time in two areas. First, as editors, reviewing generated content, managing the AI, verifying technical accuracy, updating, etc. Second, I suspect writers can do more predictive and visionary docs product work.”
Larry Ullman
Technical Writer
Formerly at Stripe
“AI just accentuates all of the existing best practices. Writing good content doesn’t really go anywhere. Actually, it’s even more important because you need to write something that’s accessible to both humans and AIs.”
Lee Robinson
VP of Product
Vercel
“What many docs, in my opinion, get wrong, is that they provide more of the reference API than concrete examples. [At DuckDB] you can open [the reference API] and you have 10-15 ready-to-go examples. People really like that. It’s also great for LLMs because they learn from this more easily than from a reference manual.”
Gábor Szárnyas
Developer Relations Advocate
DuckDB
“In the absence of the documentation, the product doesn't exist. It's a bunch of code packages together with a UI sitting on top, but there are a lot of products which don't have a UI, right? So the role of documentation becomes monumental there.”
Utsav Banerjee
Senior Manager, Product Language
New Relic
“In some cases, technical documentation has even surpassed marketing websites as the primary driver of product adoption. Why? Because it offers immediate value. A well-written doc doesn’t just describe a product’s features; it shows users how to apply them in their own environment.”
Kim Jeske
Head of Product Content Experience
Cloudflare
“Users want to see relevant information quickly, without needing to search through endless pages. AI chatbots are one solution, but I think a better answer is presenting users with relevant information from the docs right in the product, at the moment they need it.”
Samy Pessé
CTO
GitBook
“Over the past few years, our documentation has evolved into dynamic, user-centric knowledge systems — driven by a powerful combination of AI, automation, real-time feedback loops, and the irreplaceable insight of human expertise.”
Mira Balani
Staff Technical Writer
Miro
“My very subjective hunch is that users are going to consume the docs mainly through chatbots. While the docs must remain accessible in a traditional way — through a website, search, or navigation — the main way to look up something in the docs will be by asking a chatbot to produce an answer based on those docs.”
Marco Spinello
Senior Technical Writer
Booking.com
“I suspect writers will spend more time in two areas. First, as editors, reviewing generated content, managing the AI, verifying technical accuracy, updating, etc. Second, I suspect writers can do more predictive and visionary docs product work.”
Larry Ullman
Technical Writer
Formerly at Stripe
“AI just accentuates all of the existing best practices. Writing good content doesn’t really go anywhere. Actually, it’s even more important because you need to write something that’s accessible to both humans and AIs.”
Lee Robinson
VP of Product
Vercel
“What many docs, in my opinion, get wrong, is that they provide more of the reference API than concrete examples. [At DuckDB] you can open [the reference API] and you have 10-15 ready-to-go examples. People really like that. It’s also great for LLMs because they learn from this more easily than from a reference manual.”
Gábor Szárnyas
Developer Relations Advocate
DuckDB
“In the absence of the documentation, the product doesn't exist. It's a bunch of code packages together with a UI sitting on top, but there are a lot of products which don't have a UI, right? So the role of documentation becomes monumental there.”
Utsav Banerjee
Senior Manager, Product Language
New Relic
“In some cases, technical documentation has even surpassed marketing websites as the primary driver of product adoption. Why? Because it offers immediate value. A well-written doc doesn’t just describe a product’s features; it shows users how to apply them in their own environment.”
Kim Jeske
Head of Product Content Experience
Cloudflare
“Users want to see relevant information quickly, without needing to search through endless pages. AI chatbots are one solution, but I think a better answer is presenting users with relevant information from the docs right in the product, at the moment they need it.”
Samy Pessé
CTO
GitBook
“Over the past few years, our documentation has evolved into dynamic, user-centric knowledge systems — driven by a powerful combination of AI, automation, real-time feedback loops, and the irreplaceable insight of human expertise.”
Mira Balani
Staff Technical Writer
Miro
“My very subjective hunch is that users are going to consume the docs mainly through chatbots. While the docs must remain accessible in a traditional way — through a website, search, or navigation — the main way to look up something in the docs will be by asking a chatbot to produce an answer based on those docs.”
Marco Spinello
Senior Technical Writer
Booking.com
“I suspect writers will spend more time in two areas. First, as editors, reviewing generated content, managing the AI, verifying technical accuracy, updating, etc. Second, I suspect writers can do more predictive and visionary docs product work.”
Larry Ullman
Technical Writer
Formerly at Stripe
“AI just accentuates all of the existing best practices. Writing good content doesn’t really go anywhere. Actually, it’s even more important because you need to write something that’s accessible to both humans and AIs.”
Lee Robinson
VP of Product
Vercel
“What many docs, in my opinion, get wrong, is that they provide more of the reference API than concrete examples. [At DuckDB] you can open [the reference API] and you have 10-15 ready-to-go examples. People really like that. It’s also great for LLMs because they learn from this more easily than from a reference manual.”
Gábor Szárnyas
Developer Relations Advocate
DuckDB
“In the absence of the documentation, the product doesn't exist. It's a bunch of code packages together with a UI sitting on top, but there are a lot of products which don't have a UI, right? So the role of documentation becomes monumental there.”
Utsav Banerjee
Senior Manager, Product Language
New Relic
“In some cases, technical documentation has even surpassed marketing websites as the primary driver of product adoption. Why? Because it offers immediate value. A well-written doc doesn’t just describe a product’s features; it shows users how to apply them in their own environment.”
Kim Jeske
Head of Product Content Experience
Cloudflare
“Users want to see relevant information quickly, without needing to search through endless pages. AI chatbots are one solution, but I think a better answer is presenting users with relevant information from the docs right in the product, at the moment they need it.”
Samy Pessé
CTO
GitBook
“Over the past few years, our documentation has evolved into dynamic, user-centric knowledge systems — driven by a powerful combination of AI, automation, real-time feedback loops, and the irreplaceable insight of human expertise.”
Mira Balani
Staff Technical Writer
Miro
“My very subjective hunch is that users are going to consume the docs mainly through chatbots. While the docs must remain accessible in a traditional way — through a website, search, or navigation — the main way to look up something in the docs will be by asking a chatbot to produce an answer based on those docs.”
Marco Spinello
Senior Technical Writer
Booking.com
“I suspect writers will spend more time in two areas. First, as editors, reviewing generated content, managing the AI, verifying technical accuracy, updating, etc. Second, I suspect writers can do more predictive and visionary docs product work.”
Larry Ullman
Technical Writer
Formerly at Stripe
“AI just accentuates all of the existing best practices. Writing good content doesn’t really go anywhere. Actually, it’s even more important because you need to write something that’s accessible to both humans and AIs.”
Lee Robinson
VP of Product
Vercel
“What many docs, in my opinion, get wrong, is that they provide more of the reference API than concrete examples. [At DuckDB] you can open [the reference API] and you have 10-15 ready-to-go examples. People really like that. It’s also great for LLMs because they learn from this more easily than from a reference manual.”
Gábor Szárnyas
Developer Relations Advocate
DuckDB
“In the absence of the documentation, the product doesn't exist. It's a bunch of code packages together with a UI sitting on top, but there are a lot of products which don't have a UI, right? So the role of documentation becomes monumental there.”
Utsav Banerjee
Senior Manager, Product Language
New Relic
“In some cases, technical documentation has even surpassed marketing websites as the primary driver of product adoption. Why? Because it offers immediate value. A well-written doc doesn’t just describe a product’s features; it shows users how to apply them in their own environment.”
Kim Jeske
Head of Product Content Experience
Cloudflare
“Users want to see relevant information quickly, without needing to search through endless pages. AI chatbots are one solution, but I think a better answer is presenting users with relevant information from the docs right in the product, at the moment they need it.”
Samy Pessé
CTO
GitBook
“Over the past few years, our documentation has evolved into dynamic, user-centric knowledge systems — driven by a powerful combination of AI, automation, real-time feedback loops, and the irreplaceable insight of human expertise.”
Mira Balani
Staff Technical Writer
Miro
“My very subjective hunch is that users are going to consume the docs mainly through chatbots. While the docs must remain accessible in a traditional way — through a website, search, or navigation — the main way to look up something in the docs will be by asking a chatbot to produce an answer based on those docs.”
Marco Spinello
Senior Technical Writer
Booking.com
“I suspect writers will spend more time in two areas. First, as editors, reviewing generated content, managing the AI, verifying technical accuracy, updating, etc. Second, I suspect writers can do more predictive and visionary docs product work.”
Larry Ullman
Technical Writer
Formerly at Stripe
“AI just accentuates all of the existing best practices. Writing good content doesn’t really go anywhere. Actually, it’s even more important because you need to write something that’s accessible to both humans and AIs.”
Lee Robinson
VP of Product
Vercel
“What many docs, in my opinion, get wrong, is that they provide more of the reference API than concrete examples. [At DuckDB] you can open [the reference API] and you have 10-15 ready-to-go examples. People really like that. It’s also great for LLMs because they learn from this more easily than from a reference manual.”
Gábor Szárnyas
Developer Relations Advocate
DuckDB
“In the absence of the documentation, the product doesn't exist. It's a bunch of code packages together with a UI sitting on top, but there are a lot of products which don't have a UI, right? So the role of documentation becomes monumental there.”
Utsav Banerjee
Senior Manager, Product Language
New Relic
“In some cases, technical documentation has even surpassed marketing websites as the primary driver of product adoption. Why? Because it offers immediate value. A well-written doc doesn’t just describe a product’s features; it shows users how to apply them in their own environment.”
Kim Jeske
Head of Product Content Experience
Cloudflare
“Users want to see relevant information quickly, without needing to search through endless pages. AI chatbots are one solution, but I think a better answer is presenting users with relevant information from the docs right in the product, at the moment they need it.”
Samy Pessé
CTO
GitBook
“Over the past few years, our documentation has evolved into dynamic, user-centric knowledge systems — driven by a powerful combination of AI, automation, real-time feedback loops, and the irreplaceable insight of human expertise.”
Mira Balani
Staff Technical Writer
Miro
“My very subjective hunch is that users are going to consume the docs mainly through chatbots. While the docs must remain accessible in a traditional way — through a website, search, or navigation — the main way to look up something in the docs will be by asking a chatbot to produce an answer based on those docs.”
Marco Spinello
Senior Technical Writer
Booking.com
“I suspect writers will spend more time in two areas. First, as editors, reviewing generated content, managing the AI, verifying technical accuracy, updating, etc. Second, I suspect writers can do more predictive and visionary docs product work.”
Larry Ullman
Technical Writer
Formerly at Stripe
“AI just accentuates all of the existing best practices. Writing good content doesn’t really go anywhere. Actually, it’s even more important because you need to write something that’s accessible to both humans and AIs.”
Lee Robinson
VP of Product
Vercel
“What many docs, in my opinion, get wrong, is that they provide more of the reference API than concrete examples. [At DuckDB] you can open [the reference API] and you have 10-15 ready-to-go examples. People really like that. It’s also great for LLMs because they learn from this more easily than from a reference manual.”
Gábor Szárnyas
Developer Relations Advocate
DuckDB
“In the absence of the documentation, the product doesn't exist. It's a bunch of code packages together with a UI sitting on top, but there are a lot of products which don't have a UI, right? So the role of documentation becomes monumental there.”
Utsav Banerjee
Senior Manager, Product Language
New Relic
“In some cases, technical documentation has even surpassed marketing websites as the primary driver of product adoption. Why? Because it offers immediate value. A well-written doc doesn’t just describe a product’s features; it shows users how to apply them in their own environment.”
Kim Jeske
Head of Product Content Experience
Cloudflare
“Users want to see relevant information quickly, without needing to search through endless pages. AI chatbots are one solution, but I think a better answer is presenting users with relevant information from the docs right in the product, at the moment they need it.”
Samy Pessé
CTO
GitBook
“Over the past few years, our documentation has evolved into dynamic, user-centric knowledge systems — driven by a powerful combination of AI, automation, real-time feedback loops, and the irreplaceable insight of human expertise.”
Mira Balani
Staff Technical Writer
Miro
“My very subjective hunch is that users are going to consume the docs mainly through chatbots. While the docs must remain accessible in a traditional way — through a website, search, or navigation — the main way to look up something in the docs will be by asking a chatbot to produce an answer based on those docs.”
Marco Spinello
Senior Technical Writer
Booking.com
“I suspect writers will spend more time in two areas. First, as editors, reviewing generated content, managing the AI, verifying technical accuracy, updating, etc. Second, I suspect writers can do more predictive and visionary docs product work.”
Larry Ullman
Technical Writer
Formerly at Stripe
“AI just accentuates all of the existing best practices. Writing good content doesn’t really go anywhere. Actually, it’s even more important because you need to write something that’s accessible to both humans and AIs.”
Lee Robinson
VP of Product
Vercel
“What many docs, in my opinion, get wrong, is that they provide more of the reference API than concrete examples. [At DuckDB] you can open [the reference API] and you have 10-15 ready-to-go examples. People really like that. It’s also great for LLMs because they learn from this more easily than from a reference manual.”
Gábor Szárnyas
Developer Relations Advocate
DuckDB
“In the absence of the documentation, the product doesn't exist. It's a bunch of code packages together with a UI sitting on top, but there are a lot of products which don't have a UI, right? So the role of documentation becomes monumental there.”
Utsav Banerjee
Senior Manager, Product Language
New Relic
“In some cases, technical documentation has even surpassed marketing websites as the primary driver of product adoption. Why? Because it offers immediate value. A well-written doc doesn’t just describe a product’s features; it shows users how to apply them in their own environment.”
Kim Jeske
Head of Product Content Experience
Cloudflare
“Users want to see relevant information quickly, without needing to search through endless pages. AI chatbots are one solution, but I think a better answer is presenting users with relevant information from the docs right in the product, at the moment they need it.”
Samy Pessé
CTO
GitBook
“Over the past few years, our documentation has evolved into dynamic, user-centric knowledge systems — driven by a powerful combination of AI, automation, real-time feedback loops, and the irreplaceable insight of human expertise.”
Mira Balani
Staff Technical Writer
Miro
“My very subjective hunch is that users are going to consume the docs mainly through chatbots. While the docs must remain accessible in a traditional way — through a website, search, or navigation — the main way to look up something in the docs will be by asking a chatbot to produce an answer based on those docs.”
Marco Spinello
Senior Technical Writer
Booking.com
“I suspect writers will spend more time in two areas. First, as editors, reviewing generated content, managing the AI, verifying technical accuracy, updating, etc. Second, I suspect writers can do more predictive and visionary docs product work.”
Larry Ullman
Technical Writer
Formerly at Stripe
“AI just accentuates all of the existing best practices. Writing good content doesn’t really go anywhere. Actually, it’s even more important because you need to write something that’s accessible to both humans and AIs.”
Lee Robinson
VP of Product
Vercel
“What many docs, in my opinion, get wrong, is that they provide more of the reference API than concrete examples. [At DuckDB] you can open [the reference API] and you have 10-15 ready-to-go examples. People really like that. It’s also great for LLMs because they learn from this more easily than from a reference manual.”
Gábor Szárnyas
Developer Relations Advocate
DuckDB
“In the absence of the documentation, the product doesn't exist. It's a bunch of code packages together with a UI sitting on top, but there are a lot of products which don't have a UI, right? So the role of documentation becomes monumental there.”
Utsav Banerjee
Senior Manager, Product Language
New Relic
“In some cases, technical documentation has even surpassed marketing websites as the primary driver of product adoption. Why? Because it offers immediate value. A well-written doc doesn’t just describe a product’s features; it shows users how to apply them in their own environment.”
Kim Jeske
Head of Product Content Experience
Cloudflare
“Users want to see relevant information quickly, without needing to search through endless pages. AI chatbots are one solution, but I think a better answer is presenting users with relevant information from the docs right in the product, at the moment they need it.”
Samy Pessé
CTO
GitBook
“Over the past few years, our documentation has evolved into dynamic, user-centric knowledge systems — driven by a powerful combination of AI, automation, real-time feedback loops, and the irreplaceable insight of human expertise.”
Mira Balani
Staff Technical Writer
Miro
“My very subjective hunch is that users are going to consume the docs mainly through chatbots. While the docs must remain accessible in a traditional way — through a website, search, or navigation — the main way to look up something in the docs will be by asking a chatbot to produce an answer based on those docs.”
Marco Spinello
Senior Technical Writer
Booking.com
“I suspect writers will spend more time in two areas. First, as editors, reviewing generated content, managing the AI, verifying technical accuracy, updating, etc. Second, I suspect writers can do more predictive and visionary docs product work.”
Larry Ullman
Technical Writer
Formerly at Stripe
“AI just accentuates all of the existing best practices. Writing good content doesn’t really go anywhere. Actually, it’s even more important because you need to write something that’s accessible to both humans and AIs.”
Lee Robinson
VP of Product
Vercel
“What many docs, in my opinion, get wrong, is that they provide more of the reference API than concrete examples. [At DuckDB] you can open [the reference API] and you have 10-15 ready-to-go examples. People really like that. It’s also great for LLMs because they learn from this more easily than from a reference manual.”
Gábor Szárnyas
Developer Relations Advocate
DuckDB
“In the absence of the documentation, the product doesn't exist. It's a bunch of code packages together with a UI sitting on top, but there are a lot of products which don't have a UI, right? So the role of documentation becomes monumental there.”
Utsav Banerjee
Senior Manager, Product Language
New Relic
About this report
The State of Docs Report was initiated and administered by the team at GitBook, with input from expert partners to align on the metrics, processes, tools, and trends facing technical documentation and docs teams. We are grateful to the many technical partners, supporters, interviewees, and survey respondents for helping shape the survey and the report, for sharing perspectives, and for helping paint a bigger picture about the state of documentation today.
Be part of The State of Docs Report 2026
Interested in helping us get a head-start on the 2026 report?
© 2025 Copyright GitBook INC.
440 N Barranca Ave #7171, Covina, CA 91723, USA. EIN: 320502699
Be part of The State of Docs Report 2026
Interested in helping us get a head-start on the 2026 report?
© 2025 Copyright GitBook INC.
440 N Barranca Ave #7171, Covina, CA 91723, USA. EIN: 320502699
Be part of The State of Docs Report 2026
Interested in helping us get a head-start on the 2026 report?
© 2025 Copyright GitBook INC.
440 N Barranca Ave #7171, Covina, CA 91723, USA. EIN: 320502699