Logo
LullabotArchitecture
HomeAll ADRsDrupal ADRsDevOps ADRs
  1. Home
  2. ADRs
  3. Record architecture decisions

DecisionRecord architecture decisions

accepted

We need to record the architectural decisions made on this project.

Table Of Contents

  • Decision
  • Consequences

Decision

We will use Architecture Decision Records, as described by Michael Nygard.

Consequences

See Michael Nygard's article, linked above. For a lightweight ADR toolset, see Nat Pryce's adr-tools.


Decided on Tuesday, June 8th 2021

  • meta

Accepted ADRs

  • Place form fields in the same order that they are rendered in the resulting page

    • drupal
    • editorial-experience

    25 days ago

  • Load JavaScript as external resource with defer attribute

    • javascript
    • front-end
    • performance

    a month ago

  • Define the order of steps when building a Drupal site

    • drush
    • deployments

    2 months ago

  • Load JavaScript as external resource with async and defer attributes

    • javascript
    • front-end
    • performance

    4 months ago

  • Use Typed Entity to encapsulate business logic in dedicated classes

    • drupal
    • code quality

    9 months ago

  • Leverage view modes when rendering entities

    • drupal

    a year ago

  • Use [ticket-id]--[short-description] in feature branch names

    • git

    a year ago

  • Use identical cache backends on development environments

    • drupal
    • devops

    a year ago

  • See all
Home
All ADRs
Drupal ADRs
DevOps ADRs
RSS
GitHub
Twitter
LinkedIn
YouTube
Terms of Service

© 2023 Lullabot, Inc. CC-BY 4.0.