Skip to content

project docs 1. Record architecture decisions
  • Welcome to MkDocs
    • Architecture Decision Records
      • 1. Record architecture decisions
        • Status
        • Context
        • Decision
        • Consequences
      • 2. Use sphinx as our knowledge base system
      • 3. Use PlantUML for diagramming
      • 4. Use mkdocs as a knowledge base system
      • 5. Use PlantUML for diagramming with use of stdlib
      • Colorized
      • Colorized2
      • Colorized3
      • Colorized4
      • Colorized5
      • Colorized6
      • Colorized7
      • Colorized8
      • Colorized9
      • Risksystem
      • Risksystem2
      • Risksystem3
      • Somesystem
      • Somesystem10
      • Somesystem11
      • Somesystem12
      • Somesystem14
      • Somesystem2
      • Somesystem3
      • Somesystem4
      • Somesystem5
      • Somesystem6
      • Somesystem7
      • Somesystem8
      • Somesystem9
      • Systemcontext
      • Webportal
      • Wetclinic
    • Admonition
    • CodeHilite
    • Footnotes
    • Metadata
    • Permalinks
    • PyMdown Extensions
    • Diagrams
    • Routing list
    • Diagrams in those runbooks
  • Status
  • Context
  • Decision
  • Consequences

1. Record architecture decisions¶

Date: 2020-11-03

Status¶

Accepted

Context¶

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

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.

Previous Architecture Decision Records
Next 2. Use sphinx as our knowledge base system
powered by MkDocs and Material for MkDocs