Sanity integration guide
How to keep Sanity up to date
Your Sanity docs are structured content, and nothing in Sanity tells you when a change to your product made a page wrong.
Keeping help centers accurate at
The short answer
- What Sanity offers
- Sanity CMS has features like Comments and Tasks for review, Scheduled drafts for timing, and AI Assist for drafting, mostly on the Growth plan and above.
- Where it stops
- Each one starts from content already in Sanity or from a person's request, so none of them can see that your product's code changed.
- Where Solo fits
- Solo connects to your docs content, compares it with your code changes, flags the pages a change made wrong, and drafts fixes that a person approves.
On this pageShort answer
Why it matters
Why an accurate docs site matters
A change to your product ships, the page that describes it stays in Sanity Content Lake exactly as written, and your front end keeps rendering the old step. Readers can't self-serve, AI answers repeat the old steps, and search results quote a page that is now wrong.
Readers solve problems without contacting support
A docs page that matches your product lets a reader finish the task on your site. A wrong step sends them to your support team with the same question, because your front end shows whatever the content says.
AI answers repeat what your content says
Sanity Context is a hosted, read-only MCP server that exposes your content to AI agents from your live dataset, and Content Agent works with your current documents. Whatever a page says is what those agents pass along.
Your pages show up correctly in search
Your front end renders pages from this content, so search engines crawl it and AI answer engines may quote it. If a page describes a setting you removed, the wrong answer reaches people before they open your docs.
Built-in tools
What Sanity CMS already offers for docs maintenance
It has features for review, drafting and scheduling, and most of the collaboration tools sit on the Growth plan and above. All of them work from content that is already in the dataset, so none can tell that your product changed.
| Stage | Sanity's features | Missing features |
|---|---|---|
| 01Know upcoming changes | There is no feature for this stage, so news of a change to your product has to reach your docs team from outside the platform. | Nothing in Sanity Studio or Content Lake reads your product's code or feature flags, so a change reaches your docs only if someone passes it on. |
| 02Identify outdated articles | GROQ-powered webhooks fire when documents change, which lets a developer build a needs-review queue. Content Agent can search and audit content for outdated terminology and metadata gaps. | Both work from the content already in Sanity, so they can spot stale wording but can't tell that a change to your product made a page wrong. |
| 03Draft updated copy | AI Assist, on Growth and above, runs your saved instructions on a document or field. Content Agent can rewrite or translate fields across many documents and proposes each change for approval. | Both draft from your instructions and the existing content, not from your code, so someone still has to know what changed and say so. |
| 04Collaborate on updates | Comments on fields or passages and Tasks with assignees, due dates and @mentions are on the Growth plan and above. Workflows, still in early access, adds stages and assigned to-dos to a document. | These tools coordinate people once a page is known to need work, but none tells the team which pages a change to your product affected. |
| 05Publish changes | Edits stay as drafts until someone publishes them, and Scheduled drafts on Growth and above publish a single document at a set time. Document history keeps revisions for 3 days on Free, 90 on Growth and 365 on Enterprise. | Publishing follows a date or a person's click, so nothing prompts a docs change when the feature it describes changes. |
With Solo
Docs management with Solo on top of Sanity
Sanity Studio and Content Lake hold your content, but neither can see your code. Solo reads and indexes your documentation content, compares it with your code changes, flags the pages a change made wrong, and drafts the fix. A person reviews each suggestion, and an accepted change is written to the Sanity document.
What Solo adds to Sanity's built-in tools
| Stage | Sanity without Solo | Sanity with Solo |
|---|---|---|
| 01Know upcoming changes | There is no feature for this stage, so news of a change to your product has to reach your docs team from outside the platform. | Solo summarizes recent changes in your connected code repositories in plain language, and shows a feature flag's rollout status when it's available. |
| 02Identify outdated articles | GROQ-powered webhooks fire when documents change, which lets a developer build a needs-review queue. Content Agent can search and audit content for outdated terminology and metadata gaps. | Solo compares each of your code changes with your indexed documentation content and flags the pages that now describe something your product no longer does. |
| 03Draft updated copy | AI Assist, on Growth and above, runs your saved instructions on a document or field. Content Agent can rewrite or translate fields across many documents and proposes each change for approval. | Solo suggests replacement text for the instructions a change to your product made wrong, with the old and proposed wording side by side. |
| 04Collaborate on updates | Comments on fields or passages and Tasks with assignees, due dates and @mentions are on the Growth plan and above. Workflows, still in early access, adds stages and assigned to-dos to a document. | A person reviews each suggestion with the triggering change attached, then edits, accepts, adds it to a draft, rejects, snoozes or resolves it elsewhere. |
| 05Publish changes | Edits stay as drafts until someone publishes them, and Scheduled drafts on Growth and above publish a single document at a set time. Document history keeps revisions for 3 days on Free, 90 on Growth and 365 on Enterprise. | Accept writes the approved update to the Sanity document, and Add to Draft keeps it in Solo until published, so nothing goes live without a person's approval. |
Questions
Questions about Sanity and Solo
What docs leads on Sanity ask about keeping their content matching their product.
Does Solo replace Sanity?
No. Your content stays in Sanity and your front end keeps rendering it. Solo reads your documentation content, compares it with your code changes and suggests fixes, and your team decides what to accept.
Can Sanity AI Assist keep our docs current?
AI Assist runs your saved instructions on a document or field, so editors can rewrite or fill in content faster. It works from the document and your schema, not from your code, so someone still has to know a feature in your product changed. It is available on the Growth plan and above.
How do we update Sanity docs after a product launch?
Start with the pages about the feature you changed, then the pages readers reach most often. Assign a Task to each page owner and use Comments on the exact fields that are wrong, so the work stays visible. Solo covers the first part by comparing each of your code changes with your documentation content.
Can Solo publish changes to Sanity on its own?
No. Solo suggests each change, and a person reviews it. Accept writes the approved update to the document, or Add to Draft keeps it in Solo until you publish.
Which Sanity plans include the review and scheduling features?
Comments, Tasks, Scheduled drafts and AI Assist are on the Growth plan and above, and grouped publishing for several documents is on certain Enterprise plans. Document history keeps 3 days on Free, 90 days on Growth and 365 days on Enterprise. Check the pricing page for current limits.
Related guides
Also works with
Solo works alongside the tools your team already uses, and each guide covers what is specific to that platform.
Further reading on help center drift
Why Help Center Content Goes Stale After a Product Launch
Why help center content goes stale after a product launch, what breaks behind the scenes, and how support teams can catch the drift before customers do.
6 min read
When to Update Help Center Articles: A Practical Threshold
A calendar-based review cadence misses most drift. Here's a practical threshold for when a help center article actually needs updating, and why it matters.
7 min read
Self-Updating Help Center: How It Actually Works
A self-updating help center catches product changes before customers do. Here's what "automatic" really means, and what still needs a human.
4 min read
See which Sanity pages your product outgrew
A demo shows how Solo compares your code changes with the docs content you manage in Sanity CMS, so you see which pages need a change.