Provider migration

Migrate from Redocly to Bloom

Redocly is strong for API docs and governance. Bloom is narrower around generated SDKs, docs previews, and launch reports.

Checks

What to check

Redocly lint rules and bundling settings need to be preserved or replaced.

Markdown docs and API references need route mapping.

Governance checks should become release checks, not just docs warnings.

SDK generation needs a migration report.

Checks

Export source docs, OpenAPI files, theme settings, redirects, and custom domains.

Decide which content remains hand-authored and which references are generated.

Generate a preview before touching production DNS.

Run SDK and docs checks before publishing packages or indexing new pages.

Details

Bloom is OpenAPI-first.

The migration report shows the SDK, docs, and launch work before anything goes live.

SDKs, docs preview, sitemap, and llms.txt live in the same workflow.

The dashboard shows what is generated, ready, and waiting on review.