02 — Requirements
Server
| Component | Version | Note |
|---|---|---|
| TYPO3 | 14.0 – 14.99 | Declared in ext_emconf.php; the extension will not install on v13. |
| PHP | 8.4 recommended | TYPO3 v14's own minimum applies. |
| Bootstrap Package | 16.0 – 16.99 | Hard dependency. Resolved by Composer from packagist, or installed from the TER in classic mode. |
| Database | MySQL 8 / MariaDB 10.6+ | Whatever TYPO3 v14 supports. |
| Composer | 2.x | For the recommended installation path. |
PHP extensions: the TYPO3 v14 defaults, plus gd. Image processing itself is done by the ImageMagick or GraphicsMagick command line tools, which TYPO3 calls — the PHP extensions do not replace them. Nothing beyond what a standard TYPO3 install needs.
For the delivered project
The ZIP from the customer portal is a ready-made DDEV project, so a first installation needs nothing else on the machine:
| Component | Note |
|---|---|
| Docker | DDEV runs the containers on it. |
| DDEV | Assumed to be installed and working; see ddev.readthedocs.io. PHP, Composer and MariaDB live inside the container. |
Setting up Docker and DDEV is not part of this documentation.
Its .ddev/config.yaml pins PHP 8.4, nginx-fpm and MariaDB 10.11. See 03 — Installation with DDEV.
How the extensions are delivered
yavi_core and the theme are not on packagist, and there is no private Composer registry to add. Both come as a ZIP from the customer login at licence.yavithemes.com (Konto → Downloads), and updates come from the same page for as long as the licence's update window runs.
What you do not need
- No Node.js, npm or yarn. SCSS is compiled server-side by scssphp, which ships with Bootstrap Package. There is no asset pipeline to run and no
dist/folder to commit. - No build step in deployment. Deploy the files, flush the cache, done.
Third-party packages pulled in
| Package | Why |
|---|---|
bk2k/bootstrap-package | Base content elements, SCSS compilation, image variants. |
Optional, if the site uses them: b13/container (the multi-column container elements ship configuration for it).
Licence
Every theme requires a licence key. Without a valid licence the extension does not work. yavi_core on its own does not need a key, but on its own it is not a design either. See 11 — Licence.
Writable paths
The installing user needs write access to:
| Path | Why |
|---|---|
config/sites/<id>/settings.yaml | The backend module writes every setting here. |
var/cache/ | Compiled SCSS, DI cache, page cache. |
typo3temp/assets/ | The compiled theme-<hash>.css lands here. |
fileadmin/ | Self-hosted Google fonts are downloaded and cached here on demand. |
If config/sites/<id>/settings.yaml is read-only — a common state on deployments that ship the config as an immutable artifact — the module shows the form but cannot save. That is the single most common "the backend module does nothing" report.
Browser support (frontend)
The theme uses modern CSS deliberately: :has(), color-mix(), overflow: clip, custom properties everywhere, container-type. In practice that means the last two versions of Chrome, Edge, Firefox and Safari. Older browsers get a readable but plainer page — the $color-* SCSS scalars exist as a static fallback for exactly that case.