ADRs from "Andrew Berry"
A collection of software design choices that address architecturally significant requirements with contributions made by Andrew Berry
- ADRs 38
- Disciplines 30
- Use 11ty to manage the ADRs
- Document project setup in README.md
- Do not use placeholder text in form fields
- Place form fields in the same order that they are rendered in the resulting page
- 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 [ticket-id]--[short-description] in feature branch names
- Use identical cache backends on development environments
- Use JavaScript strict mode
- Use SMACSS to organize CSS within projects
- Use TypeScript for pure JavaScript development
- Use CSS Logical Properties
- Do not add the Metatag field to the node form
- Use gatsby-theme-adr to manage the ADRs
- Use Claro for the Drupal administration theme
- Use inclusive language in code and technical writing
- 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
- Use dedicated accounts for service integrations
- 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 strict types in PHP code
- Use settings.php for environment overrides and local settings
- Stage File Proxy for static files
- Define the order of steps when building a Drupal site
- Environment Indicator
- Use Log4brains to manage the ADRs