---
title: "Feature: Initial theme development package"
manual: "Frontend Theme for Extension Development"
version: "main"
source: "Changelog/2.0/Feature-InitialThemeDevelopmentPackage.rst"
modified: "2026-09-17T04:52:50+00:00"
---

# Feature: Initial theme development package

## Description

Initial release of `sbuerk/theme-extension-development`. The package is a
TYPO3 frontend theme for development purposes: its job is to give a TYPO3
installation a reasonable frontend to look at and to render against, without
building a site package for it first — for extension development, for DDEV
based test instances and for acceptance tests.

> [!IMPORTANT]
> The theme is being built up. This release renders a page - see
> [Feature: Site set and page rendering](Feature-SiteSetAndPageRendering.html#feature-site-set-page-rendering) \- and the content elements that exist
> without `fluid_styled_content` \- see
> [Feature: Content element rendering](Feature-ContentElementRendering.html#feature-content-element-rendering).

> [!WARNING]
> This is a development tool, not a production theme. It is meant to be
> required as a development dependency of an extension repository or
> installed into a disposable test instance, and it makes no promise about
> design, markup stability or upgrade paths for a live site.

What this release provides:

-   TYPO3 v13 and v14 support on PHP 8.2 up to 8.5, with core version aware
    implementations below `Core13/` and `Core14/`.
-   Dependency injection wiring through `Configuration/Services.php`,
    with services configured by Symfony dependency injection attributes on the
    classes themselves.
-   Container based tooling through `Build/Scripts/runTests.sh` covering
    linting, coding guidelines, static analysis, unit and functional tests and
    documentation rendering.
-   GitHub Actions workflows running these gates for TYPO3 v13 and v14 on pull
    requests.
-   A functional test setup ready to build on: strict PHPUnit configuration,
    an example fixture extension loaded by its composer package name, site
    based tests issuing frontend sub-requests in several languages, and
    repository tests running in a built frontend environment.
-   Developer documentation below `docs/`, covering the architecture,
    the quality gates, both test suites and the release workflow.

The extension ships a `SBUERKThemeExtensionDevelopmentDummy` placeholder
class and an `SBUERKThemeExtensionDevelopmentExampleExampleInterface`
example service, both meant to be removed once the first real implementation is
added.