Build a Reference Library Your AI Writer Actually Reads Before It Answers
How to upload your own documents and links into the content app's Infobase so AI drafts pull from material you chose, not just general knowledge.
"AI writes generic content" is a fair complaint when the AI has nothing specific to draw from. The content app's Infobase page exists to fix that: it's a workspace-scoped library of documents you upload — files, URLs, pasted text — that gets indexed and made retrievable when you're generating a draft, so the model has something concrete to work from instead of only its general training.
What goes into it
The Infobase accepts uploaded files and links you add directly. Each document gets a status as it's processed — pending, processing, ready, or error — so you can see at a glance whether something is actually searchable yet or still being chunked and indexed. A failed document shows why it failed rather than silently not being available.
How it's different from Brand Voice
The content app has a second, separate source of grounding: Brand Voice, which automatically syncs your own published articles into a namespace used to match your tone and style. Infobase is the opposite kind of library — it's user-curated, not automatic. You decide what goes in: product docs, style guides, research, competitor teardowns, internal wikis, whatever the AI should be able to reference that isn't already something you've published. The two systems are deliberately kept apart — one captures how you already write, the other captures what you want the AI to know.
Why this is worth setting up before you lean on AI drafting
A model without a reference library will answer confidently regardless of whether it actually knows the specifics of your product, your pricing, or your positioning. A model with a curated library to query against can point to something instead of guessing. If you're using AI drafting for anything more specific than generic top-of-funnel content — a technical explainer, a comparison page, anything where getting a detail wrong is embarrassing — building out the Infobase first is the difference between a draft you can trust and one you have to fact-check line by line anyway.
Start with whatever you'd hand a new hire on their first week: your positioning doc, your FAQ, your pricing page, a few of your best competitor comparisons. That's usually enough to notice the difference in the next draft you generate.