ADRs tagged "editorial-experience"

When content types have dedicated pages, matching the display order makes edit forms easier to understand.

The metatag field makes the node form slow and overly complex for editorial users.

Claro offers a modern, responsive, and accessible interface that showcases Drupal's capabilities from the outset.

Drupal's editorial experience in the "Add Content" page is confusing out of the box, especially when the content model's complexity increases.

Drupal core by default outputs the maximum number of values (cardinality) as empty elements on entity forms, which usually represents a poor user-experience.

All Drupal websites our team works on have one or more environments. At a minimum, there will be a production and a local development environment. Most projects will have production, staging, development preview, and local environments. Developers and QA often access different environments at the same time. Since making content or configuration changes on the wrong environment can have unintended consequences, it is important to be able to distinguish environments easily.