`@stainless-api/docs` dependency version.
Docs replacement
Migrate Stainless docs without guessing.
A Stainless migration is not just SDK codegen. Docs sites may depend on hosted SDKJSON, Astro packages, custom reference components, and deployment workflows.
Details
What to scan
Hosted Stainless API calls or SDKJSON fetches.
Astro/Starlight config and build scripts.
Custom docs routes, redirects, and domain settings.
Details
What Bloom produces
A docs dependency report.
A local docs preview.
A redirect and canonical map.
A generated llms.txt and sitemap for agent-readable docs.
Example output
The docs migration page is grounded in a real docs scan.
Sendblue docs use an older Stainless docs package than the transition guide recommends.
Hosted Stainless dependencies need a local replacement path.
Astro/docs migration needs review before launch.
The scanner produces a reusable report for the dashboard.
| Example | Why it matters | Current result |
|---|---|---|
| Docs dependency scan | Scans package.json and source files for Stainless package, hosted upload, API key references, and SDKJSON readiness. | 60 files scanned, 2 tasks, 2 review items. |
| Transition requirement | Docs must stop fetching generated reference data from hosted Stainless APIs. | Needs local SDKJSON/reference generation before docs launch. |
Related pages