Usage Guidance
Anvil2’s governance model guides how updates are reviewed, how contributions are evaluated, and how the system evolves. Use this section to understand how decisions are made, what to expect when submitting changes, and how the Anvil and Product teams collaborate.How governance works
Governance ensures that changes to Anvil2 support product-wide consistency, accessibility, and maintainability. This includes:- Reviewing new component or pattern proposals
- Evaluating updates to foundations
- Assessing requests against system principles
- Aligning changes across design, engineering, and product teams
- Maintaining documentation, tokens, and code in sync
- Overseeing versioning, deprecations, and migration guidance
Design System Scope
- Shared foundations (tokens, color, type, spacing, motion, accessibility)
- Core UI components and supported variants
- Reusable interaction patterns and workflows
- Content guidance (with Product Copy)
- Design & engineering tooling for the system
- Documentation, release notes, and support communications
Roles within governance
Design System Team (Core Owners)
- Maintains foundations, components, tokens, patterns, and documentation
- Reviews and guides contributions
- Ensures accessibility standards are met within Anvil2
- Leads cross-team alignment on decisions
- Manages versioning, releases, and deprecations
Product Designers & Engineers (Contributors)
- Propose and contribute new components, patterns, or enhancements
- Identify system gaps for real product work
- Partner with the system team during testing and ideation
- Follow established guidance and standards
- Guide evolution through active conversation
Cross-Functional Partners (Research, PMs)
- Provide input during reviews
- Help validate proposed changes against user needs
- Ensure solutions support customer-facing and internal workflows
- Guide evolution through surfacing user needs