Skip to content

project docs 2. Use sphinx as our knowledge base system
  • Welcome to MkDocs
    • Architecture Decision Records
      • 1. Record architecture decisions
      • 2. Use sphinx as our knowledge base system
        • Status
        • Context
        • Decision
        • Consequences
      • 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

2. Use sphinx as our knowledge base system¶

Date: 2020-11-03

Status¶

Superceded by 4. Use mkdocs as a knowledge base system

Context¶

The issue motivating this decision, and any context that influences or constrains the decision.

Decision¶

The change that we're proposing or have agreed to implement.

Consequences¶

What becomes easier or more difficult to do and any risks introduced by the change that will need to be mitigated.

Previous 1. Record architecture decisions
Next 3. Use PlantUML for diagramming
powered by MkDocs and Material for MkDocs