Architecture Decision Records
Architecture Decision Records (ADRs) document significant design choices in the GTCX UI platform.
Active ADRs
| ADR | Title | Status |
|---|---|---|
| ADR-0001 | Template Format | Accepted |
| ADR-0002 | Ant Design Customization Strategy | Accepted |
| ADR-0003 | Template API Conventions | Accepted |
| ADR-0004 | Offline UX Patterns | Accepted |
| ADR-0005 | i18n and RTL Strategy | Accepted |
| ADR-0006 | Demo Gallery Framework | Accepted |
Key Decisions
ADR-0002: Ant Design Customization
Use Ant Design theme tokens and ConfigProvider as the primary customization mechanism. Avoid deep CSS overrides.
ADR-0003: Template API Conventions
All templates accept standardized props:
data— Primary content/entityactions— Primary/secondary CTAsfilters— List and search controlsaudit— Provenance and trail surfaceslayout— Optional layout overrides
Related Documents
- PRD — Product Requirements Document
- Technical Roadmap — Sprint plan and milestones
- Metronic Audit — Component parity analysis
ADR Template
New ADRs should follow the template in docs/adr/0001-template.md:
# ADR NNNN: Title
## Status
Proposed | Accepted | Deprecated | Superseded
## Context
What is the issue that we're seeing that is motivating this decision?
## Decision
What is the change that we're proposing and/or doing?
## Consequences
What becomes easier or more difficult to do because of this change?