A theme package owns page layouts, theme styles, and theme-level plugin declarations. It should not reimplement business logic such as post scanning, comments, or search inside layout components.
A theme package only declares capabilities. Plugin factories validate their own configuration, while themes declare the plugins they need through plugins. Core validates the theme home layout and plugin layout contracts.
A theme package should have its own package.json, build configuration, and version. Consumer projects install the package directly and reference its package name. Core does not bind to a specific theme, so the ecosystem can grow without continuously changing the framework core.
To start from a runnable skeleton, copy the theme starter. It includes pageLayouts.home, a React layout, global styles, and an independent package build configuration.
See the API reference and plugin API specification for the complete contracts.