RFC Number: XXXX
Status: Draft
Created: 2026-08-03
Last Updated: 2026-08-03
Initiator: Olivier Dobberkau, President TYPO3 Association
Responsible Body: TYPO3 Association Board
Target Version / Timeframe: Contract version 1.0 by Q1 2027, reference implementation alongside v14 LTS
Olivier Dobberkau dkd-dobberkau
dkd-dobberkau
/ RFC xxxx mcp interface contract for TYPO3 CMS.md
Created
August 3, 2026 10:28
RFC xxxx mcp interface contract for TYPO3 CMS / DRAFT
Strategy Paper — Artificial intelligence along three audiences: Customers, Developers, Infrastructure
Generative AI is changing how content is created, maintained, and found. For TYPO3 as an enterprise CMS, this creates concrete opportunities — but also requirements around data protection, operations, and development. This paper structures the AI roadmap along the three audiences affected by adoption: customers (value and benefits), developers (integration and extension), and infrastructure (operations and scaling).
The goal is a shared understanding of the fields of action as a basis for further prioritization. The structure is deliberately thematic and without a fixed timeline, so it can be slotted into existing roadmaps.
dkd-dobberkau
/ RFC AI Assisted TYPO3 Core Patch Review.md
Created
July 16, 2026 14:54
TYPO3 Core Patch Review: A Sashiko-Inspired Concept
This document sketches what an adaptation of the Sashiko approach could look like for TYPO3 Core development. It is not a proposal to adopt Sashiko itself, which is built specifically around Linux kernel subsystems and the LKML mailing-list workflow. It is a proposal to borrow the pattern behind Sashiko and rebuild it around TYPO3's actual contribution flow, actual failure modes, and actual governance structure. The intent is to give the eventual RFC something concrete to react to rather than a comparison to the kernel in the abstract.
Sashiko is not a single clever prompt. It is a small system of choices that together make an LLM reviewer trustworthy enough to run continuously against a live contribution stream. Four of those choices matter most for us.
dkd-dobberkau
/ typo3-v15-roadmap-rfc.md
Created
May 26, 2026 18:04
RFC: TYPO3 v15 Development Roadmap
dkd-dobberkau
/ PRD_TYPO3_Content_Provenance_Extensions.md
Created
May 14, 2026 14:48
PRD, TYPO3 Content Provenance Extensions
Status. Draft 0.1, May 2026.
Maintainers. To be assigned. Initial drafting by dkd Internet Service GmbH.
Related documents. Content Provenance Specification v0.1 (separate repository).
Audience. TYPO3 contributors, agency developers, integrators, and anyone who wants to build the reference implementation of the Content Provenance Specification on TYPO3.
Fool-proof shell script to spin up a TYPO3 14 project with DDEV in a single command — with secure admin password handling, preflight checks, and credential safety built in.
| Tool | Install |
|---|---|
| Docker (running) | docs.docker.com |
| DDEV ≥ 1.23 | ddev.readthedocs.io |
dkd-dobberkau
/ gist:03950ed0f3311645c89153d9769ebcb5
Created
March 17, 2021 09:38
https://opsone.ch/de/blog/typo3-varnish Translation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| How a TYPO3 extension for Varnish integration was born from a flash of inspiration. | |
| In 2013, my former employer snowflake and Redpill Linpro, the company behind Varnish at the time, agreed to work together. Part of this contract was that I was allowed to attend a Varnish course in Oslo with two colleagues, in order to give courses in Germany, Austria and Switzerland as a certified Varnish trainer afterwards. | |
| Not only the social program remained in my good memory, but also in the course we could learn a lot of new things, although we had already actively used Varnish before. Besides the successful certification of all participants, the idea for the TYPO3 Varnish Extension can be called a great achievement of these 3 days. | |
| TYPO3 and Varnish | |
| Up to this point a TYPO3 extension for Varnish already existed. The process of this extension was that when changing a page in the TYPO3 backend, all URLs belonging to this page were collected and then sent individually to Varnish for deletion. This was not very practical |