How to handle CMS content in a monorepo
AdvancedQuick Answer
TL;DR
Handle CMS content in a monorepo by creating a shared package for CMS client configuration, queries, and TypeScript types that multiple applications consume. Place the CMS Studio in its own workspace, share content schemas across apps, and use a single source of truth for CMS configuration. Monorepo tools like Turborepo, Nx, or pnpm workspaces manage dependencies and build orchestration across the CMS and frontend packages.
Key Takeaways
- Create a shared CMS package with client config, queries, and types that all apps in the monorepo consume
- Place the CMS Studio in its own workspace alongside frontend apps
- Use monorepo tooling (Turborepo, Nx) to manage builds and dependencies across CMS and frontend packages