ADR Location and Format

[ianmcburnie]

THIS IS A TEST, PLEASE IGNORE

ADR Location & Format

Single place to record the discussion, proposals & next steps.

Owner / Shepherd: owner
Maintainers / Deciders: maintainer1, maintainer2
Created: 2026-01-21
Doc status: Active — single-page tracker (short & current)

Purpose of this Document

Single place to record the problem, short proposals, final decision, and concrete next steps.

Problem

In which location and format can we capture ADRs in a consistent manner for Marko, React@eBay, EvoWeb?

Location Proposals

1. GitHub /docs/adrs
   Use this folder per project (evoweb/marko/react/sample-app)
2. Github Issues
   Rejected
3. Github discussions
   We can create an ADR section
   Uses Markdown, easy to edit
   Keeps all discussion history
   Can set different statuses on it, or labels
   Not really an adopted standard
4. GitHub /docs + PR template
   Same as 1 but with a specific PR template for new or superseded ADRs

Format Proposals

todo

Questions/Comments

• How are we setting it up so that people will read the ADRs?
• Most people don’t read ADRs. Does it make sense to tailor them to be read by AI?
• We can probably author these ADRs a little less informally, and less verbose, if AI is the chief consumer
• Author from the PR using AI

Propose some starter ADRs here

Until we have our system figured out, please propose any ADRs below. Let’s consider 2026 as our starting point.

• Use ebay-design-tokens NPM package as source of truth
• Use Percy for Visual Regression Testing