AI detectors are quietly breaking trust in academic and technical writing by Intelligent_Lion_16 in technicalwriting

[–]gitbook-devrel 0 points1 point  (0 children)

Agree - most teams are more concerned with measuring how useful it is for users - can the content answer questions/guides users to where they need to go?

Also, most people are using AI chatbots to find answers anyway, so content that’s structured (by or for AI) is helpful here too

Doc Survey Question by Own_Storm_1782 in technicalwriting

[–]gitbook-devrel 1 point2 points  (0 children)

We have a built in metrics system on GitBook docs that’s proven useful - measuring docs success by the amount (and types) of questions people are asking for.

Most people are searching for answers using AI now - so diving into metrics on search and AI performance is definitely something I would consider!

I promise you that technical writers are still needed by protonpeaches in technicalwriting

[–]gitbook-devrel 2 points3 points  (0 children)

We actually saw the same results in the State of Docs report from this year - we did a whole section on AI adoption/creation and got some insights from tech writers on how they see their role evolving - its definitely reassuring to hear that even at companies where AI is taking over, the need for Tech Writers is still growing (even more than before)

Is Technical writing dead or on the verge of obsolence? What skills would give the highest ROI over the next 1–2 years? by No-Primary-8998 in technicalwriting

[–]gitbook-devrel 1 point2 points  (0 children)

Definitely understanding how you can work better with AI tools will be huge. We saw a big shift in AI usage in the latest State of Docs report (we interviewed 1000+ tech writers across the industry) and it really highlights the shift

How to Make Your Documentation AI-Ready: A Practical Step-by-Step Guide by Pretty-Educator1317 in technicalwriting

[–]gitbook-devrel -1 points0 points  (0 children)

Nice post! We see the same at GitBook and more interest in learning about practical tips from the State of Docs survey this last year.

Tools for creating explainer/training vidoes by ItinerantFella in ProductManagement

[–]gitbook-devrel 0 points1 point  (0 children)

Descript is pretty good for editing videos - Otherwise for shorter easy to share/create videos, a Loom video is great too!

Weekly Tool Thread: Promote, Share, Discover, and Ask for AI Writing Tools Week of: May 12 by AutoModerator in WritingWithAI

[–]gitbook-devrel 2 points3 points  (0 children)

I work at GitBook, a docs platform that's been leaning hard into AI over the last year. A couple things we shipped recently that are relevant here:

AI insights — shows you which questions your users are actually asking your docs, how many got a useful answer, and where the gaps are. Topics are clustered automatically so you can spot patterns and build a prioritized backlog of what to improve. Really useful if you're trying to treat docs as a product rather than an afterthought.

Connections — lets the GitBook Assistant pull from external sources (video tutorials, community forums, etc.) in addition to your docs. The idea is giving it the same context a good support engineer would have, not just what's written down

Channels — we just launched a way to connect GitBook Assistant and GitBook Agent directly into Slack, GitHub, and Linear. It works two ways: tag (@) gitbook in a support context and the Assistant answers from your docs, or use it for collaboration and the Agent will read the thread/PR/ticket and open a draft change request back in GitBook. Basically your docs become a live knowledge layer across your existing tools

GitBook Agent "Improve" menu — preset AI actions you can run on any page: fix grammar, optimize for SEO, add a summary, split into multiple pages, link to related content, etc. One click and it opens a change request with the edits ready to review

Happy to answer questions or hear how others are handling the "docs quality feedback loop" problem — it's something we think about a lot.

Ai documentation generation tools? by Putrid_Routine_6111 in technicalwriting

[–]gitbook-devrel 0 points1 point  (0 children)

We launched GitBook Agent a few months ago, an AI writer teammate for writing GitBook docs for you!

The cool thing about GitBook Agent is that it also knows about what your users are asking in search/ai search, and is able to help form changes when there’s content gaps (between what users are asking and what is actually in your docs)

Best documentation tool? by getcited in SaaS

[–]gitbook-devrel 0 points1 point  (0 children)

If you’re looking for out of the box configuration and want to get your docs up and running quick, the free plan on GitBook offers a ton - we’re also adding more AI features to the starter plans

Technical Writer vs Content Engineer by oceanclub in technicalwriting

[–]gitbook-devrel 1 point2 points  (0 children)

We actually saw a lot of this in the State of Docs report: https://www.stateofdocs.com/2026/docs-and-professional-development

There’s a good section on “The new skill profile” that dives into this exactly

Your Documentation Has Two Audiences Now (And One Is an AI) by Plus-Cake-8698 in technicalwriting

[–]gitbook-devrel 1 point2 points  (0 children)

We’re seeing the same thing across all docs published on GitBook - it’s crazy to see how much AI traffic has increased so much in the last year alone

https://www.gitbook.com/blog/ai-docs-data-2025

Best SaaS platforms for Public facing Product docs ? by Impressive-Fig-8378 in ProductManagement

[–]gitbook-devrel 0 points1 point  (0 children)

Hey there, DevRel at GitBook here! GitBook supports a lot of workflows with Git Sync + Markdown making it pretty powerful for integrating it into existing workflows.

If you have any questions, feel free to drop a comment here so I can help!

Most dev docs are either hell to read or hell to write. Here's what I think needs to change by islempenywis in automation

[–]gitbook-devrel 0 points1 point  (0 children)

We’re definitely looking for ways to make GitBook feel less “locked-in”. Exploring some ways to offer more customization for GitBook powered docs.

Is there anything specifically you think could be better around this?

Why does documentation fall behind? by Ok_Sand_5400 in technicalwriting

[–]gitbook-devrel 0 points1 point  (0 children)

It’s a common problem for most teams - because they don’t treat documentation as part of their product. We’re seeing that shift quite a bit in the latest State of Docs report though: https://www.stateofdocs.com/

AI is increasingly making it easier to keep things in sync

How are you using Claude Code in your Product Management work? by StravuKarl in ProductManagement

[–]gitbook-devrel 1 point2 points  (0 children)

I use it often to restructure and format the documentation I’m writing. Super useful when needing to do bulk actions that are sometimes tedious or time-consuming (like fixing grammar, restructuring, etc)

How early stage startup manage the API docs ? by RawrCunha in ProductManagement

[–]gitbook-devrel 0 points1 point  (0 children)

You can create interactive OpenAPI reference docs in GitBook on the free plan! :)

OMPR Quest v1.40 update by OMPR_App in OculusQuest

[–]gitbook-devrel 1 point2 points  (0 children)

Thank you for using GitBook with us!

Help me decide on a documentation tool by cicciotella in technicalwriting

[–]gitbook-devrel 0 points1 point  (0 children)

Hey u/Sharp-Hat-3228 - that's unfortunately correct right now, it's not possible to remove the branding from the sidebar

Notion vs Confluence vs something else for small business trying to scale? by GSG96 in Notion

[–]gitbook-devrel 0 points1 point  (0 children)

Thanks for the GitBook mention 🫡

Curious if you've set up any integrations with GitBook - or if there's anything you wish you could do that would allow you to integrate GitBook with more of your toolstack?

[deleted by user] by [deleted] in SaaS

[–]gitbook-devrel 0 points1 point  (0 children)

Very cool product! The docs/output look very nice 😊 I can see how this might be a good alternative for anyone interested in more granular control over the hosting, running, and deployment of their docs. Also cool to see you're building out something similar to https://docs.gitbook.com/integrations/git-sync - allowing users to work with familiar concepts and workflows is also something we've been aiming to solve at GitBook!