Context: Content SDK is exclusively Next.js-focused. Competitors offer broader framework support: Storyblok has official SDKs for React, Next.js, Vue, Nuxt, Svelte, Astro, and more; Contentful supports 5+ frameworks with mature SDKs. This limits Content SDK's addressable market to the Next.js ecosystem. However, multi-framework support is expensive to build and maintain, and Sitecore's explicit bet on Next.js has enabled deeper integration (proxy.ts, App Router support, Design Studio).
Steps:
1. Survey the Content SDK package architecture to identify what is framework-agnostic vs Next.js-specific
- `core`, `content`, `search`, `analytics-core`, `events`, `personalize` appear framework-agnostic
- `nextjs`, `react` are framework-specific
2. Assess effort to create `@sitecore-content-sdk/vue` and `@sitecore-content-sdk/svelte` packages
3. Evaluate demand signals: Sitecore community requests, competitor adoption data, framework market share
4. Produce an ADR documenting the decision with trade-offs
Acceptance criteria:
ADR produced and reviewed
Clear recommendation: multi-framework investment, Next.js-first with escape hatches, or Next.js-only
If multi-framework: prioritized framework list with effort estimates
Risks: Multi-framework support could dilute engineering focus and slow the Next.js experience improvements that are Content SDK's current strength. The ADR should weigh opportunity cost explicitly.