KISS Principle: Simplicity as an Architecture Decision

Contrib before custom: before developing a custom module, check whether a maintained contrib module exists. The community has already solved most standard problems.

Fewer content types: not every content variation needs its own content type. Often a flexible content type with Paragraphs is sufficient.

Clear information architecture: flat hierarchies, unambiguous navigation, predictable URL patterns. Users and search engines will thank you.

Every custom module must be checked with Drupal updates. Every additional content type increases editorial complexity. Every special customization makes an agency switch harder.

arocom measures the complexity of a Drupal project by the number of custom modules, the depth of configuration and the deviation from the Drupal standard. The closer to the standard, the lower the long-term operating costs.