itzbund/gsb-core

Core functionality and base configuration for Government Site Builder (GSB) 11. This is part of the Government Site Builder (GSB) 11. The GSB 11 is a measure of the Dienstekonsolidierung Bund (DKB) of the Federal Ministry of the Interior and for Homeland (BMI) and is carried out on behalf of the Inf

Package info

gitlab.opencode.de/bmi/government-site-builder-11/extensions/gsb_core.git

Type:typo3-cms-extension

pkg:composer/itzbund/gsb-core

Statistics

Installs: 10 385

Dependents: 8

Suggesters: 2

v5.2.0 2026-06-30 09:00 UTC

Requires

Suggests

  • itzbund/gsb-clustered-caching: Clearing caches when asked for, by means of a middleware.
  • itzbund/gsb-consent: Implements the user consent management.
  • itzbund/gsb-csp: Automatically adds integrity attributes to all local CSS/Javascript resources, and provides a restrictive set of CSP headers. It provides a backend module to see applied CSP solutions.
  • itzbund/gsb-feusermanagement: Contains the front-end user administration.
  • itzbund/gsb-glossary: Provides glossary functionality for GSB 11.
  • itzbund/gsb-metadata-cleaner: Helps to reduce the amount of data - especially personal information - in metadata of files. It uses exiftool to delete everything except for "copyright" data and tags which can be configured per storage. This applies to PDFs and images.
  • itzbund/gsb-nginx-proxy: Help with cache clears for nginx based caching proxies; inspired by EXT:varnish and others. This extension will send PURGE or CACHEBYPASS requests to the nginx caching proxy.
  • itzbund/gsb-permissions: Permission management for GSB 11.
  • itzbund/gsb-places: Places for GSB 11
  • itzbund/gsb-private-frontend: Contains federal administration fonts and icons. Only available for the federal administration!
  • itzbund/gsb-public-frontend: Contains the style guide with public fonts.
  • itzbund/gsb-public-notice: Public notice management for GSB 11.
  • itzbund/gsb-rss: RSS feed generation and import functionality.
  • itzbund/gsb-solr: This extension extends the standard solr extension to make it work in the context of GSB 11. It provides a custom PageIndexerRequest object that does not use an external HTTP request to fill the solr index. This is necessary due to limitations in the ITZBund hosting environment.
  • itzbund/gsb-valkey: Provides Redis Sentinel based implementations for caching, locking and session storage.
  • itzbund/gsb-widgets: Contains a set of custom widgets for the editor's dashboard.
  • itzbund/siteconfig-impexp: Site configuration import and export functionality.

Provides

None

Conflicts

None

Replaces

None

GPL-3.0-or-later e7e2fcc5c65cbe85decf0c68afd78333b2deb81a

  • Kai Ole Hartwig <o.hartwig.woop@moselwal.de>
  • Matthias Peltzer <matthias.peltzer.woop@digitas.com>
  • Michael Max Busch <m.busch.woop@moselwal.de>
  • Patrick Schriner <patrick.schriner.woop@diemedialen.de>
  • Christian Rath-Ulrich <christian.rath-ulrich.woop@digitas.com>
  • Thorsten Müller <thorsten.mueller.woop@adesso.de>

This package is auto-updated.

Last update: 2026-06-30 09:04:27 UTC

README

GSB 11 Extension gsb_core

👁 TYPO3 13
👁 PHP 8.3

About

The extension gsb_core is the mainstay of the several GSB 11 extensions. The extension configures TYPO3 and extends it with selected extensions to provide better structured and appealing content while optimizing accessibility.

Learn more about the GSB 11.

Installation

The best way to install this extension is to start with the GSB Sitepackage Kickstarter extension.

Quick installation without GSB Sitepackage Kickstarter

In a composer-based TYPO3 installation you can install the extension EXT:gsb_core via composer:

 composer config -g gitlab-domains gitlab.opencode.de && \
 composer config -g repositories.gsb-core vcs https://gitlab.opencode.de/bmi/government-site-builder-11/extensions/gsb_core.git

 composer require itzbund/gsb-core

In TYPO3 installations above version 11.5 the extension will be automatically installed. You do not have to activate it manually.

Feature Flags

This document explains how to use feature flags. We separate between two different kinds of feature flags:

Feature

Feature flags allow you to enable or disable specific features in your installation. \ This is of particular importance to disable features that have not passed the approval process.

Optional

Optional flags allow you to (de-)activate specific features for your installation. \ A practical use for these is the (de-)activation of an extension.

For more information about feature flags in TYPO3, please refer to the official TYPO3 Documentation on Feature Flags.

Feature Flag Configuration

Feature and Optional flags are configured in the .env or the local-dev/.ddev/docker-compose.environment.yaml file on ddev machine. To add a feature flag, use the following syntax:

# FEATURE FLAG
- TYPO3__SYS__features__GSB11_FEATURE_123_NEW_FEATURE=%const(bool:true)%
# OPTIONAL FLAG
- TYPO3__SYS__features__GSB11_OPTION_123_ENABLE_EXTENSION=%const(bool:true)%

In this example, both feature flags, GSB11_FEATURE_123_NEW_FEATURE and GSB11_OPTION_123_ENABLE_EXTENSION, are set to true. To disable the feature, change the value to false or delete the setting.

Feature Flag Truth Table

This table illustrates the behavior of feature flags in various states.

Feature Flag StateEvaluated ValueDescription
featureFlag = truetrueThe feature is explicitly enabled.
featureFlag = falsefalseThe feature is explicitly disabled.
featureFlag = ''falseAn empty value is treated as false.
featureFlag not existfalseA non-existent flag defaults to false.

Usage in PHP Code

To use a feature flag in your PHP code, you can check the flag's value with the isFeatureEnabled() method of the Features class:

if (GeneralUtility::makeInstance(Features::class)->isFeatureEnabled('GSB11_FEATURE_123_NEW_FEATURE')) {
 echo 'Feature is enabled';

 // Feature-specific code
 ...
}

Usage in Fluid Templates

Feature flags can also be checked in your Fluid templates with TYPO3's Feature ViewHelper.

Basic usage

<f:feature name="GSB11_FEATURE_123_NEW_FEATURE">
 This is being shown if the flag is enabled
</f:feature>

Feature > then > else

<f:feature name="GSB11_OPTION_123_ENABLE_EXTENSION">
 <f:then>
 Flag is enabled
 </f:then>
 <f:else>
 Flag is undefined or not enabled
 </f:else>
</f:feature>

Current feature flags of gsb_core

Feature flagDescription
GSB11_OPTION_1972_GSB11_BACKEND_BRANDINGAt default branding to the login screen

Usage

Nothing to do.

Site package

Site packages in EXT:gsb_core are alike to .

A package is available in the site configuration if it matches one of the following criteria:

  • it's extension key includes gsb_core or site AND does not include impexp
  • it has the following configuration in it's composer.json:
 {
 "extra": {
 "itzbund/gsb-core": {
 "isSitePackage": true
 }
 }
 }

If a package has been selected as a site package, it's typoscript configuration (Configuration/TypoScript/{constants|setttings}.typoscript) will be loaded as the root template, which allows for zero configuration deployments.

Further Reading

For more information about feature flags in TYPO3, please refer to the TYPO3 Documentation on Feature Flags.

Middleware based endpoints

/api/version

For infrastructure reasons this extension provides a version endpoint at /api/version which returns a json object with the following structure

{
 "versions": {
 "gsb": "[string|null]",
 "container": "[string|null]",
 "helmChart": "[string|null]",
 "TYPO3": "[string|null]",
 "packageCacheHash": "[string|null]"
 }
}

This endpoint can be used to decide whether a cache flush might be necessary after a deployment (or: whether it's not - because the version hasn't changed).

/api/health

This extension provides a health endpoint at /api/health which returns a response without a body and status code 204.

⚠️ Warning: on production systems you should restrict access to all /api paths from the outside to not expose critical system information.

Contribute

As with TYPO3, we encourage you to join the project by submitting changes. Development of the GSB 11 mainly happens in the GSB 11 TYPO3 extension repositories.

To get started, have a look at our detailed contribution walkthrough.