Skip to content
Gallery
Design Ops
Design Ops
Share
Explore
Consistency Performance Scorecard (QPS)

icon picker
How to start contributing

Learn how to contribute effectively to the Quartz Design System and collaborate with the community. Follow these steps to make impactful additions and improvements.
PC
Pierre Copin
All contributions are tracked and monitored
here
⁠
. Please refer to it to see the status and progress of current and past contributions.

1. Governance model

The Core tier is the foundation for everything else. Its modules provide the styles, guidelines, components, and patterns that all products must use.
The Prisms build on top of the Core. Their modules provide components and patterns shared by all products of the same nature. Applications and Websites are two of them.
The Facets build on top of the prisms to provide guidelines, patterns, and components tailored for a specialized area.
⁠
image.png
⁠
⁠

Who does what?

⁠
image.png
⁠
⁠
1. Product Alignment
Product Team: Provides feedback and contributes use cases. They participate in testing and iterating on the design system.
Experts / Contributors: Conduct research and facilitate discussions, helping to formalize ideas.
Quartz Team: Updates the design system based on feedback.
2. Standards and Requirements
Product Team: No specific role defined here in the diagram.
Experts / Contributors: Contribute requirements and standards, helping to formalize design principles.
Quartz Team: Estimates the impact and effort required for implementation.
3. Industrialize and Share
Product Team: Consumes the final design system and maintains it within their products.
Experts / Contributors: If they are in capacity to do so, help build the design system components.
Quartz Team: Develops specifications, builds components, provides support and ensure they’re shared and informed across teams.

2. Key Meetings for Effective Contribution and Collaboration

Proposed list of meetings, adaptable based on the Core Team's capacity and the contributing team's needs.

1. Kickoff & Alignment Meeting (At the start of the process or as needed)

Participants: Representatives from all teams (Product Team, Experts, Quartz Team)
Purpose: To align on upcoming goals, features, and priorities for the design system.
Agenda:
The Quartz Team determines if the contribution is part of the Core, a Prism, or a Facet, categorizing it appropriately within the design system's structure.
Review new product requirements and use cases.
Discuss any major shifts in design or technical standards.
Set shared objectives for the next sprint or quarter.

2. Weekly Sync / Standup (Weekly or bi-weekly, 15–30 minutes)

Participants: Leads or designated members from each team
Purpose: To provide quick updates on progress, blockers, and immediate needs.
Agenda:
Quick status updates from each team (Experts, Quartz).
Identify any dependencies or blockers and decide on action items to resolve them.
Align on any minor changes in priorities or timelines.

3. Design Review (Bi-weekly or Monthly, 1 hour)

Participants: Product designers, Experts/Contributors, Quartz Team
Purpose: To review new components, design changes, and user experience standards.
Agenda:
Present new designs or updates to existing components.
Get feedback from cross-functional stakeholders.
Document any agreed changes or new requirements.
Align on design standards and ensure consistency.

4. Requirements & Standards Workshop (Monthly or as needed, 1–2 hours)

Participants: Product Team, Experts/Contributors, Quartz Team
Purpose: To formalize and update requirements and standards for new components or system changes.
Agenda:
Review proposed requirements from the Product Team.
Define or refine standards to ensure scalability and reusability.
Prioritize requirements and establish consensus on specifications.

5. Build & Handoff Meeting (End of each sprint or cycle, 1 hour)

Participants: Quartz Team, Product Team representatives
Purpose: To discuss the implementation of finalized components or features and prepare for handoff.
Agenda:
Showcase completed components or updates.
Review any technical documentation or specifications.
Discuss any support needed from the Quartz Team during integration.
Address any final questions before handing off for consumption by the Product Team.

6. Feedback & Retrospective (Monthly or End of Sprint, 1 hour)

Participants: All teams (Product, Experts, Quartz)
Purpose: To gather feedback on the process and identify improvements.
Agenda:
Reflect on what worked well and what didn’t.
Identify bottlenecks, inefficiencies, or areas for improvement.
Agree on actionable improvements for the next cycle.

Summary of Sessions

Kickoff & Alignment – Sets overall goals and priorities.
Weekly Sync – Keeps everyone aligned and removes blockers.
Design Review – Ensures consistency and gathers design feedback.
Requirements Workshop – Defines and finalizes standards.
Build & Handoff – Prepares components for use by the Product Team.
Feedback & Retrospective – Continuously improves the collaboration model.
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.