kumwe / content-model
Portable content, revision, translation and editorial workflow models with persistence ports.
Requires
- php: ^8.5
- ext-mbstring: *
- kumwe/access-context: 0.1.2
- kumwe/access-control: 0.1.2
- kumwe/localization: 0.1.1
- ramsey/uuid: ^4.9
Requires (Dev)
- ext-zip: *
- phpstan/phpstan: ^2.1
- phpstan/phpstan-strict-rules: ^2.0
- phpunit/phpunit: ^12.0
- squizlabs/php_codesniffer: ^4.0
Suggests
None
Provides
None
Conflicts
None
Replaces
None
This package is auto-updated.
Last update: 2026-09-12 15:17:16 UTC
README
Portable content, revision, translation and editorial workflow models with persistence ports, under
Kumwe\Content\. The package provides immutable definitions and snapshots, bounded workflow declarations,
translation groups, scoped queries and reusable repository contracts.
Installation and usage
composer require kumwe/content-model:0.2.0
PHP 8.5 and mbstring are required. Composer resolves the exact Kumwe dependencies from Packagist; consumers need no custom VCS repository definitions. Values are constructed directly and repository ports are supplied by the host. There is no ConfigProvider or captured site, actor, request, connection or container.
See the standalone example, public API, Core contract and integration.
Compatibility and status
The published 0.2.0 contract requires ContentRepository::adopt() for content-definition adoption. Adapters
preserve entry/revision data and reject stale, missing or trashed records as documented in
compatibility. Pre-1.0 consumers pin exact versions.
Core owns authorization, transactions, persistence adapters, dispatch and presentation. Package methods do not establish authority. Publication and package CI remain separate from independent consumer verification and Core acceptance. Dependency status records the current exact dependency graph.
Development
composer install composer check composer examples
The full gate checks syntax, generated API and governed manifests, architecture, static analysis, coding standards, dependency identities, test ownership, examples, security and a clean no-dev archive consumer. See repository guarantees, test ownership, release process, release record and security.