When a capability should be reused across multiple sites, copy an independent package from one of the repository starters:
CogitaPluginFactory, build context, unified logging, and capability declarations.CogitaTheme, the required home layout, and global styles.After copying a starter, replace the @your-scope placeholder package name, install dependencies, and build:
Register plugins through the site's plugins array and consume themes by package name. Release checks copy both starters into a temporary directory and run real package builds to ensure the templates do not depend on internal workspace paths.
When a plugin needs configuration, prefer a factory closure that receives options and returns null when the configuration is not satisfied. When it needs a page, declare requiredLayouts in plugin metadata and provide the matching pageLayouts in the theme. Add a versioned virtual module only when browser data is required, and cover independent consumers with a build or browser acceptance check.