Ivan Shmidt
882728ae1d
Co-authored-by: Raghunandan Balachandran <meetraghu28@gmail.com> Co-authored-by: Ben Lambert <ben@blam.sh>
1.1 KiB
1.1 KiB
id, title, sidebar_label
| id | title | sidebar_label |
|---|---|---|
| adrs-overview | Architecture Decision Records (ADR) | Overview |
The substantial architecture decisions made in the Backstage project lives here. For more information about ADRs, when to write them, and why, please see this blog post.
Records are never deleted but can be marked as superseded by new decisions or deprecated.
Records should be stored under the architecture-decisions directory.
Contributing
Creating an ADR
- Copy
0000-template.mdtodocs/architecture-decisions/0000-my-decision.md(my-decision should be descriptive. Do not assign an ADR number.) - Fill in the ADR following the guidelines in the template
- Submit a pull request
- Address and integrate feedback from the community
- Eventually, assign a number
- Add the full path of the ADR to the
mkdocs.yml - Merge the pull request
Superseding an ADR
If an ADR supersedes an older ADR then the older ADR's status is changed to superseded by ADR-XXXX and links to the new ADR.