Renderer props and auth behavior need mapping.
Provider migration
Migrate from RapiDoc to Bloom
RapiDoc is useful for rendering OpenAPI quickly. Bloom targets the broader production problem: generated SDKs, hosted docs, launch reports, and publishing readiness.
Checks
What to check
Reference-only docs need guides, examples, and search structure.
Generated SDKs need runtime and public-surface comparison.
SEO pages need canonical URLs, sitemap, and llms.txt.
Checks
Migration checklist
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
Why Bloom fits
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.
Related pages