Website maintenance for Drupal
Drupal needs a different maintenance model from WordPress: Composer, Drush, configuration and larger version jumps must be reported correctly.
What we watch
- Drupal core and Composer-managed packages with update risk separated clearly.
- Drush, PHP and database versions without WordPress-specific signals.
- Report items that do not send the client to solve things only the host or we can change.
How the work runs
- Update level is judged by Drupal's versioning model, not by WordPress logic.
- Composer and Drush are central in the technical report; WP-CLI is irrelevant for Drupal.
- When a PHP patch level is controlled by hosting, the report assigns it to the right owner.
A report you can actually use
The monthly summary shows updates, backups, monitoring and open work.
Actions are split between our work and items that need a client decision.
Admins see the technical state, while clients get a summary in their chosen language.
A good fit when
The site runs on Drupal and needs maintenance that understands Drupal tooling instead of showing WordPress reports under another label.