ADRs from "David Burns"
A collection of software design choices that address architecturally significant requirements with contributions made by David Burns
- ADRs 19
- Disciplines 16
- Use the feature branch git workflow
- Use composer audit in automated checks for known security vulnerabilities
- Use PHPStan for PHP code static analysis at level 6
- Use Renovate for third-party dependency updates
- Use ImageMagick with Drupal
- Document project setup in README.md
- Leverage view modes when rendering entities
- Use [ticket-id]--[short-description] in feature branch names
- Use identical cache backends on development environments
- Configure Composer Patches to Use `-p2` as `patchLevel` for Drupal core
- Store Composer Patches configuration in composer.json
- Use local copies of patch files
- Break composer install if patches don't apply
- Use dedicated accounts for service integrations
- Composer patches configuration and best practices
- Block the Drupal user 1 account in production environments
- Confirm Drupal site configuration is always in a default state
- Environment Indicator
- Use Log4brains to manage the ADRs