Context: Sitecore's official migration documentation exists at `doc.sitecore.com` but the JSS repository itself — the place developers start when they realize they need to migrate — contains no migration guidance. Community partners (Fishtank: "Farewell to JSS, Welcome to Sitecore Content SDK"; AgencyQ: "The Business Case for Content SDK Migration") have published third-party guides, confirming market demand. First-party migration guidance in the JSS repo closes this gap and establishes Sitecore's voice in the migration narrative.
Steps:
1. Create `MIGRATION.md` at the repo root
2. Include: deprecation timeline (EOL June 2026), package mapping table (JSS -> Content SDK equivalents), key breaking changes summary, environment variable rename table, link to official Sitecore migration guide
3. Add a "Migrating to Content SDK" section to `README.md` linking to `MIGRATION.md`
4. For each JSS package `README.md` that has a Content SDK equivalent, add a migration pointer at the top
5. Submit as a PR with clear commit message referencing the JSS EOL
Acceptance criteria:
`MIGRATION.md` exists at repo root with complete package mapping
`README.md` links to migration guide prominently
Each migratable package README has a migration pointer
Links to official Sitecore documentation are included
Risks: Migration documentation needs to stay synchronized with Content SDK changes. Pin to specific Content SDK versions in the documentation to avoid future drift.