typo3-update
TYPO3 v14 development
Strategy: This collection targets TYPO3 v14.x only. Patterns here assume a v14 codebase. For migrating from older majors, use
typo3-rector,typo3-extension-upgrade, Fractor, and the official upgrade guide first.
TYPO3 API First: Always use TYPO3's built-in APIs, core features, and established conventions before creating custom implementations. Do not reinvent what TYPO3 already provides. Always verify that the APIs and methods you use exist and are not deprecated in TYPO3 v14 by checking the official TYPO3 documentation.
1. Version Strategy
Target: TYPO3 v14.x only
| Version | Role for this collection |
|---|---|
| v14.x | Supported target — examples and constraints assume TYPO3 v14 |
| Older majors | Not targeted — complete a core upgrade, then use these patterns |
Best Practice: Declare TYPO3 v14-only constraints in composer.json and ext_emconf.php for new work.
Version Constraints
More from dirnbauer/webconsulting-skills
document-processing
>-
187ai-search-optimization
>-
185typo3-content-blocks
>-
89typo3-ddev
Use when providing DDEV URLs, accessing TYPO3 backend in browser, performing any ddev command (e.g. start, stop, restart, describe, exec), setting up DDEV for TYPO3 extension development, or testing across multiple TYPO3 versions. Triggers on: ddev URLs, backend URLs, local development, docker environment, PHP version management, multi-version testing.
85webconsulting-branding
>-
78legal-impressum
>-
76