Care that continues after launch.
Understand what is checked, where content comes from, and how to report something that needs attention.
Checks with a clear scope
| Check | What it verifies | When it runs |
|---|---|---|
| Legacy replacement coverage | Every crawled legacy source has a destination; native cross-references resolve; local assets match their source checksums. | Every build, against the recorded migration inventory. |
| Source comparison | Web SDK MDX inputs and the imported snapshot match a recorded baseline. | Every build. Full input comparison requires the repository; standalone deployments check snapshot integrity. |
| Routes, anchors & images | Internal pages and section links resolve; image requests succeed. | Read-only audit against the running preview. External asset failures are listed separately. |
| Browser health | Rendered images, layout overflow, and application console errors. | Browser verification before sharing a deployment. HTTP checks alone cannot verify this. |
| Feature behavior | Context URLs, search matching, starter generation, and server boundaries. | Focused automated tests and interaction checks. |
Source freshness is more than a date
The change-detection baseline was recorded on 2026-10-21 and covers 232 local Web SDK documentation inputs. A changed input requires an import and review before the baseline is refreshed. It does not establish that every legacy guide matches the latest released SDK.
Java API reference schemas are fetched live. Native and hosted-product content still require review by their source owners. See the update policy for each source →
Content ownership
Web SDK content follows the repository documentation sources. Native SDK references follow their SDK source and release version. Hosted-product setup content needs an assigned editorial owner before migration. Named maintainers are not yet recorded in this preview.
Report a page issue
Use the issue action below any guide to copy its path and your selected versions. Share it with your IDmission team or support@idmission.com. Credentials, session IDs, and personal data should not be included.
Maintainer commands
pnpm check:sources
pnpm test
pnpm check:docs -- https://your-docs-preview.exampleThe audit exits unsuccessfully on broken internal pages, anchors, or required local images. Its report lists external image failures for investigation. Live camera and verification sessions need a test account and a separate integration test.
Report a docs issue
Copy this context into your team’s issue tracker or an email to support@idmission.com.