-
Notifications
You must be signed in to change notification settings - Fork 22
/
.readme.templ
31 lines (21 loc) · 1.35 KB
/
.readme.templ
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
![NATS](large-logo.png)
# NATS Architecture And Design
This repository captures Architecture, Design Specifications and Feature Guidance for the NATS ecosystem.
# Architecture Decision Records
{{- range . }}
## {{ .Tag | title }}
|Index|Tags|Description|
|-----|----|-----------|
{{- range .Adrs }}
|[ADR-{{.Meta.Index}}]({{.Meta.Path}})|{{.Meta.Tags|join}}|{{.Heading}}|
{{- end }}
{{ end }}
## When to write an ADR
We use this repository in a few ways:
1. Design specifications where a single document captures everything about a feature, examples are ADR-8, ADR-32, ADR-37 and ADR-40
1. Guidance on conventions and design such as ADR-6 which documents all the valid naming rules
1. Capturing design that might impact many areas of the system such as ADR-2
We want to move away from using these to document individual minor decisions, moving instead to spec like documents that are living documents and can change over time. Each capturing revisions and history.
## Template
Please see the [template](adr-template.md). The template body is a guideline. Feel free to add sections as you feel appropriate. Look at the other ADRs for examples. However, the initial Table of metadata and header format is required to match.
After editing / adding a ADR please run `go run main.go > README.md` to update the embedded index. This will also validate the header part of your ADR.