New Component Requests

✅ New Component Review Process

Enhancing Collaboration and Integration for Tailored Design Solutions

To maintain high standards of usability, accessibility, and cohesion within our Universal Design System (UDS), all new components must go through a structured review and approval process. This ensures consistency across teams, reinforces best practices, and empowers contributors to build scalable, user-friendly solutions.

---

📋 1. Proposal Template Submission

Submit your component proposal using the Component Proposal Form. Please include the following:

• Component Type: (e.g., button, card, modal, form field)

• Purpose: What this component is meant to do within UDS

• Design Specifications: Size, color, spacing, style collections, states, etc.

• Functionality: How the component behaves (e.g. hover, focus, responsive)

• Use Cases: When and where it should be used

• Target Audience: Who this is designed for (e.g., end users, admins)

---

📐 2. Design Guidelines Adherence

All proposed components must align with the following:

• Universal Design System primitives, tokens, and appearance layers

• Accessibility best practices (contrast, keyboard nav, semantic structure)

• Proper use of Figma variables and existing text/layout styles

• Reusability and system-wide consistency

---

🔁 3. Feedback & Iteration Loop

• Feedback will be provided in the UX/UI Discord channel.

• Reviewers will suggest improvements or flag inconsistencies.

• Submitters must revise and resubmit their designs for reevaluation.

• This collaborative iteration loop continues until the component meets UDS standards.

---

👥 4. Review Team

• Composed of Universal Design team members and designers with 3+ months experience using UDS

• May include devs, PMs, and stakeholders for cross-functional feedback

• Participates in async Discord discussions and scheduled design reviews

---

✅ 5. Final Review & Approval

Once the component has:

• Passed accessibility and visual consistency checks

• Incorporated all required changes from reviewers

• Aligned with token and appearance layer architecture

Then:

• ✅ Final approval is granted

• 📝 Component documentation is written and published in the UDS library

• 📦 Component is published and made available in the UDS Figma library

See current designs in progress here: Figma: UDS Library (in progress)

---

🛑 Important Reminders

• Do not detach or override core UDS components to create new ones.

• Always submit through this review process to ensure maintainability and system cohesion.

• Documentation is required before components are published to the library.

---

By following this process, we ensure every new component:

• Meets our shared design and accessibility standards

• Is reusable across teams and products

• Reduces duplication, maintenance cost, and inconsistency

• Scales with the evolving needs of Dev Launchers and its contributors