Getting started
CMSMotive documentation is planned around the questions a team has when a package joins an existing TYPO3 project: what it needs, how to install it and what can safely be changed.
This is a documentation design preview. Do not run the example package command until a verified release is published.
Requirements
Each released product will publish its tested TYPO3 version range, PHP requirements, dependencies and browser support in one place. No support matrix is claimed by this concept page.
Installation example
A Composer-first path keeps installation visible in the project dependency graph.
$ composer require cmsmotive/theme-nordform
After release, the product docs would cover site set configuration, content setup, asset building and deployment checks step by step.
Theme structure
The intended structure separates TYPO3 configuration, Fluid templates, assets and documentation so custom work remains easy to locate.
Configuration/ ContentBlocks/ TypoScript/ Resources/Private/ Layouts/ Partials/ Templates/ Documentation/
Accessibility
Product documentation should explain keyboard behavior, supported content patterns and known limitations. A release audit report belongs beside those notes, with a date and tested version.
Support and change history
Released packages should include a changelog, migration notes and a clear support route. For the concept, send project questions to hello@cmsmotive.de.