sdk-docs-generator

You can generate documentation JSON from SDK source code by parsing the sdk/src exports and types to output CMS-compatible JSON that reflects exact type signatures for the Sanity import pipeline.

The best way to keep SDK docs in sync with code is to run a repeatable update pipeline that validates drift between source and docs, refreshing overview, types, responses, blocks, and utilities after SDK changes or releases.

Yes, you can update Sanity CMS pages when your SDK adds new exports by running the generator against the sdk/src directory to refresh all CMS pages and produce CMS-ready JSON covering overview, types, guides, and changelog.

You validate documentation drift between your SDK source and published docs by inventorying the SDK surface from source and producing updated CMS-ready JSON to compare against existing documentation covering overview, types, guides, and changelog.

Yes, this approach works for generating Sanity CMS import files from TypeScript SDKs by extracting exact type signatures from source and producing JSON that follows the CMS JSON schema and aligns with the Sanity CMS import pipeline.

You should run an SDK documentation generator during your release process after SDK changes, feature additions, or releases to refresh CMS pages and ensure the documentation bundle always reflects the current exports and SDK surface.