---
title: "Feature: #89010 - Introduce Site Configuration for Distribution Packages"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:feature-89010"
source: "Changelog/10.1/Feature-89010-IntroduceSiteConfigForDistributionPackages.rst"
typo3-version: "10.1"
typo3-major: 10
type: "feature"
issue: 89010
forge: "https://forge.typo3.org/issues/89010"
tags: ["PHP-API", "ext:core"]
rendered: "2026-10-03T08:19:36+00:00"
---

# Feature: #89010 - Introduce Site Configuration for Distribution Packages {#feature-89010}

See [forge#89010](https://forge.typo3.org/issues/89010)

## Description {#description}

Distributions or site packages are designed to deliver a full blown TYPO3 instance with all necessary data and assets
to have a functional installation after the package has been activated.
The import of a distribution can now ship the config file (or many, if this is required).

Similar to assets, that are moved to `fileadmin` ready for use, site configurations are moved into the config folder.

## Impact {#impact}

Distributions can now ship their own site configuration files.

### Example: {#example}

Into the distribution package `Initialisation/Site` folder, put a folder with the site identifier as name, containing the
`config.yaml`.
Each folder will be moved into the target position upon extension activation.

If a folder with the same name already exists, the file will *not* be overridden. In this case no change is made to the existing configuration.