ADRs tagged "drupal"
A collection of drupal-related software design choices that address architecturally significant requirements
- ADRs 36
- Collaborators 42
- Disciplines 27
- Use PHPStan for PHP code static analysis at level 6
- Only allow developers and site administrators access to the default Drupal files listing
- Use `access_unpublished` for password-protected pages
- Use the term "microcontent" to describe embeddable content from the same website
- Use 'drush deploy' when building Drupal sites
- Use Renovate for third-party dependency updates
- Use human-readable names as exposed filter identifiers in Views
- Enforce Twig coding standards with automatic linting
- Use ImageMagick with Drupal
- Use only one h1 on each page
- Do not use placeholder text in form fields
- Order content type form fields based on content priority
- Standardize the order of steps when building a Drupal site
- Use Typed Entity to encapsulate business logic in dedicated classes
- Leverage view modes when rendering entities
- Use identical cache backends on development environments
- Do not add the Metatag field to the node form
- Use Claro for the Drupal administration theme
- Use Simple Add More to improve editorial experience
- Use Type Tray to improve editorial UX
- 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
- Always hide non-translatable fields on translation forms
- Lock entity language on edit forms
- Consistently name entity fields
- Use PHPUnit for unit testing PHP code
- Composer patches configuration and best practices
- Always use typehints in new PHP code
- Block the Drupal user 1 account in production environments
- Confirm Drupal site configuration is always in a default state
- Use DDEV for local environments
- Use strict types in PHP code
- Use settings.php for environment overrides and local settings
- Stage File Proxy for static files