The Cogita framework repository maintains Core, plugins, themes, and the handbook example. Personal blogs, team knowledge bases, and product documentation should be independent consumer sites that install and use those packages.
Keeping real blog posts in the framework repository couples two different lifecycles:
After the split, the framework repository publishes packages and its handbook, while the content repository owns articles, site configuration, and deployment.
A docs site uses contentDir; a blog uses posts and its theme plugins. The two content models can be selected independently and do not need to share a repository.
Declare published packages directly in the consumer site:
For a documentation-only site, use the docs theme:
The consumer installs its own themes and plugins. Core does not implicitly bind a theme from the framework monorepo.
workspace:* dependencies with published Cogita packages.contentDir or posts according to the site type.site.base, site.url, and comment mappings for the new repository.The framework repository uses Changesets for package releases. A consumer site only needs a compatible set of versions in its own package.json:
When upgrading, read each package changelog first, then update the CLI, Core, theme, and site plugins as one tested set. Avoid upgrading only one side of a shared contract.
The framework repository also provides an independent blog consumer check. It copies the blog configuration, posts, and public assets into a temporary directory, replaces published dependencies with the current tarballs, and checks the home page, post pages, images, feeds, and sitemap:
This does not modify the blog repository or require it to join the Cogita monorepo.
The handbook provides a similar independent docs consumer check. It installs the current packages into a temporary docs site and checks the docs theme, content directory, and representative routes:
This check does not modify docs-site; it ensures the handbook does not depend on a blog posts directory or hide routing problems behind workspace links.