Your documentation is already a retrieval corpus

GitBook, Webflow, and Framer hold the answers to support questions. The work is making them addressable before someone builds a new knowledge base.

Nov 20, 2026The avbbc desk
Your documentation is already a retrieval corpus
GitBook, Webflow, and Framer hold the answers to support questions. The work is making them addressable before someone builds a new knowledge base.

The instinct when support questions repeat is to build a knowledge base. Usually the answers already exist in the product documentation, the marketing site, and the changelog — they are just not addressable by an agent or findable by a search box.

Three servers make existing content addressable: GitBook, Webflow, and Framer.

The short answer

Before writing new docs, check whether the answer exists in a corpus you already maintain. Connect the read path, measure what the agent cannot answer, and write only the gaps.

The three corpora

Source What it holds Support value
GitBook Product docs High — procedures
Webflow Marketing site Medium — claims and positioning
Framer Landing pages Low — mostly not answers

The table is a prioritisation. Product documentation answers questions; the marketing site usually explains what the product is for, which is a different question.

GitBook: the high-value corpus

GitBook exposes spaces and pages. That is exactly the material a support agent needs: procedures, limitations, and the terminology the product uses. The integration is small and the payoff is direct.

The common problem is not access but structure: docs written for browsing are hard to retrieve. A page per task, with the task in the title, retrieves better than a long reference page — which is a writing decision, not a tool one.

Webflow and Framer: claims, not answers

Webflow and Framer hold the marketing site. Reading them is useful for a different job: an agent drafting a support reply should know what the company claims, so it does not contradict the site.

Using them as an answer corpus produces confident marketing language in response to a customer whose problem is not marketing. That is the failure to avoid.

The gap-finding loop

Connect the docs, log the questions the agent could not answer with a cited page, and review that list weekly. It is the cheapest content roadmap available: real questions, measured gaps, and an audience that already asked.

The review matters. A question the agent could not answer is either a missing page or a retrieval miss, and they need different fixes.

Writing for retrieval

Three changes make existing docs more retrievable without a rewrite: a task-shaped title, the answer in the first paragraph, and the product's own terminology repeated in the section. None of these are new ideas; they are the difference between a page written to be browsed and one written to be found.

Frequently asked questions

Do I need a separate knowledge base? Only after the existing corpus is connected and measured. Most teams find the gap is smaller than they thought.

What about outdated pages? Retrieval surfaces them as answers, which is a strong reason to add a verified date to every page.

Can the agent write the pages? Draft them, yes. See publishing with an agent.

Related reading

All posts