From 77300a6b5431398ab416f62e034a2a729df05b2c Mon Sep 17 00:00:00 2001 From: Wes Risenmay Date: Thu, 12 Feb 2026 07:32:45 -0700 Subject: [PATCH 1/3] docs: added a base Architecture Decision Record --- .../0002DocumentArchitectureDecisions.md | 33 +++++++++++++++++++ 1 file changed, 33 insertions(+) create mode 100644 architectureDecisionRecords/0002DocumentArchitectureDecisions.md diff --git a/architectureDecisionRecords/0002DocumentArchitectureDecisions.md b/architectureDecisionRecords/0002DocumentArchitectureDecisions.md new file mode 100644 index 0000000000..7a5b019327 --- /dev/null +++ b/architectureDecisionRecords/0002DocumentArchitectureDecisions.md @@ -0,0 +1,33 @@ +# Title + +Document architecture decisions + +## Context + +It is unclear to engineers what the expectations are for contributing to this repository. We need a system for making, documenting, and enforcing architecture decisions. + +## Decision + +We will document our decisions in our repositories as architecture decision records. + +We will follow the template provided in 0000Example.md. + +Decisions will be made by consensus. If an ADR is agreed upon by at least 2/3 of the engineers on the team, then it can be added to the repository. + +Pull Requests with new code that doesn't adhere to the ADRs will not be approved. High-priority urgent production bugs are an exception to this rule. This exception should be immediately followed up with a PR to fix the code, so that it conforms with the ADRs. + +When making changes to code that doesn't conform to the ADRs the following steps should be taken: + +1. If feasible update the code to conform to the ADRs +1. If updating the code to conform to the ADRs is too large of a scope, then at minimum create a ticket to fix the issue later, and write tests the cover the new code + +## Consequences + +Engineers will be able to go to a single place to learn the following + +1. What architecture decisions were made and why +1. What libraries should be used +1. What coding patterns and style should be used +1. What expectations will need to be met before a PR can be merged + +Pull requests will need conform to the ADRs to be approved. From 3557840c0605811271de71ec5a144948cd4f2a15 Mon Sep 17 00:00:00 2001 From: Wes Risenmay Date: Thu, 12 Feb 2026 07:37:44 -0700 Subject: [PATCH 2/3] add proposed date --- architectureDecisionRecords/0000Example.md | 4 ++++ .../0002DocumentArchitectureDecisions.md | 4 ++++ 2 files changed, 8 insertions(+) diff --git a/architectureDecisionRecords/0000Example.md b/architectureDecisionRecords/0000Example.md index cdbc1b03ef..bad32c2f75 100644 --- a/architectureDecisionRecords/0000Example.md +++ b/architectureDecisionRecords/0000Example.md @@ -2,6 +2,10 @@ Title of the ADR +## Date proposed + +01-01-0001 + ## Context What is the issue that we're seeing that is motivating this decision or change? diff --git a/architectureDecisionRecords/0002DocumentArchitectureDecisions.md b/architectureDecisionRecords/0002DocumentArchitectureDecisions.md index 7a5b019327..72a0f6f3d8 100644 --- a/architectureDecisionRecords/0002DocumentArchitectureDecisions.md +++ b/architectureDecisionRecords/0002DocumentArchitectureDecisions.md @@ -2,6 +2,10 @@ Document architecture decisions +## Date proposed + +02-12-2026 + ## Context It is unclear to engineers what the expectations are for contributing to this repository. We need a system for making, documenting, and enforcing architecture decisions. From 13880505b526dd94ed356ebce312171c739fc537 Mon Sep 17 00:00:00 2001 From: Wes Risenmay Date: Thu, 12 Feb 2026 08:14:24 -0700 Subject: [PATCH 3/3] add proposed date for the styling adr --- architectureDecisionRecords/0001Styling.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/architectureDecisionRecords/0001Styling.md b/architectureDecisionRecords/0001Styling.md index 4c5cef2169..f39c4ec198 100644 --- a/architectureDecisionRecords/0001Styling.md +++ b/architectureDecisionRecords/0001Styling.md @@ -2,6 +2,10 @@ Styling our html +## Date proposed + +08-19-2025 + ## Context According to the [state of css 2025](https://2025.stateofcss.com/en-US) the tools that people are the most happy with in 2025 are [css modules](https://github.com/css-modules/css-modules) and [tailwindcss](https://tailwindcss.com/).