A calmer Composer-first workflow
A dependable theme should be easy to add, inspect, update and hand off to the next developer.
Keep dependencies visible
Composer makes package versions and requirements part of the project. For an agency team, that visibility helps with review, deployment and maintenance. It also makes upgrades deliberate rather than mysterious.
A package should publish its tested TYPO3 and PHP ranges clearly. The installation guide should say what else needs configuring after the dependency is added.
Organize for the next person
File structure is a form of documentation. Separate configuration, templates and assets in a way that matches how people search for problems. Small, named components are easier to adapt than one highly abstract layer.
Release notes matter just as much as the first install. Teams need to know what changed and whether a migration step is required.
Document the real path
A useful guide covers the ordinary path and the common failure points: missing site configuration, cache behavior, asset builds and deployment. The goal is to help someone finish a project, not simply run one command.
Loading comments…