Repository navigation
v0.0.1 — First CMS preview for NAF
Use v0.0.2 or newer. That patch corrects template discovery in the Tailwind build and ships the complete regenerated stylesheet. Existing v0.0.1 installations should update and republish/check CMS assets.
NafCMS v0.0.1 is the first CMS preview for an ordinary NAF application. It provides localized articles and publishing workflows, pages, forms, media, navigation, themes, users and permissions, audit history, and explicit page/API/content/block extension registries. Composer installs it as naf/cms; the host owns configuration, storage and its public webroot.
The preview includes scoped MCP tools and an optional browser-local Ollama assistant. Package defaults remain read-only, while installation-specific runtime files and published assets belong to the host. Authentication, CSRF, permissions and token scopes remain enforced by the existing NAF/CMS integrations.
This release also corrects the standalone chart translation fallback, declares PDO in the CMS, requires Framework 0.2.9 and CLI 0.2.2, and uses published dependency commits. Static analysis avoids application boot, Tailwind builds use explicit package sources, and installation checks preserve the starter's project guide. Obsolete Auth development-repository instructions are replaced with the published Composer setup.
Sitebuilder payloads, extension APIs and storage shapes may change before v0.1. Local AI is Ollama-only, custom theme JavaScript is disabled, and PHP 8.5 remains a compatibility target. Back up the database and host runtime/media/theme files before upgrades; publish/check assets and apply migrations after updating.
Validation at the release commit: 493 tests / 2455 assertions; PHP 8.3 and 8.4 plus PHP 8.5 compatibility; PHP 8.3 minimum NAF dependencies; PHPStan and formatting; Composer/npm audits; 25 builder tests and reproducible assets; MariaDB migrations; archive inspection and a fresh SQLite host covering CLI, scoped MCP, authentication boundaries and vendor immutability. Exact merge CI.
Install with composer require naf/cms in a NAF host. Follow the CMS documentation for plugin order, database configuration, asset publication and first administrator creation.