Logo
  • Home
  • About
  • Developer documentation
  • Getting started
    • Advanced topics
  • Domain Vision Statement
  • Backup workflow
  • Architecture Decision Records
    • Project
      • Accepted
        • 0001 - Adopt Consistent Package Naming Conventions
        • 0002 - Use Conventional Commits
        • 0003 - Use Domain-Driven Design
    • Backend
      • Accepted
        • 0001 - Prefer ArchUnit as an Architectural Decision Record store
        • 0002 - Use consistent naming conventions for Liquibase migrations
        • 0003 - Never Return NULL for Collection Types
        • 0004 - Adopt Test Data Builder and Object Mother Patterns for Test Data Creation
        • 0005 - Use Pitest for mutation testing
        • 0006 - Prefer to treat a single class as a unit for testing
        • 0007 - Decouple event listeners from handlers

Architecture Decision Records

This section documents key architectural decisions made during the project’s development.

ADRs provide a clear and structured history of why certain approaches were chosen, the alternatives considered, and the implications of these decisions.

This site uses Astro JS via GitHub Pages and is stored in the project repository under the website folder.
You can contribute to it by creating a Pull Request, just like you would with any other part of this project.