简体中文
EnglishHow to Contribute to or Follow Open UI
Updated
Open UI is a W3C Community Group that works to let web developers style and extend built-in web UI components and controls, such as dropdowns, checkboxes, radio buttons, and date/color pickers. If you want to contribute to or follow the project, the official site points to two channels: Discord and GitHub. The site's Contribute section states that Open UI "wouldn't be possible without the support of our awesome community" and directs people to get involved on those two platforms. That is the extent of the contribution guidance provided on the page itself.
What Open UI Is Working On
Understanding the work helps you decide where you can plug in. According to the site, the group's purpose involves:
- Fully specifying the component parts, states, and behaviors of built-in controls
- Defining necessary accessibility requirements
- Providing test suites to ensure compatibility
- Implementing polyfills for extensible web UI controls
The page also notes a long-term goal: establishing a standard process for developing high-quality UI controls suitable for addition to the web platform. A full outline of goals and process is available in the group's charter, which the site links to.
Where to Get Involved
| Channel | What the site says | Best suited for |
|---|---|---|
| Discord | "Get involved on Discord" | Discussion, questions, following day-to-day activity |
| GitHub | "Get involved on ... Github" | Specifications, test suites, polyfills, code-level work |
The page does not describe specific roles, onboarding steps, or a contribution workflow beyond these two entry points. If you are looking for the formal scope and process, the site directs you to the full charter.
Who This Is For
The site frames the project around web developers and design systems. It notes that component frameworks and design systems currently reinvent common web UI controls to give designers full control over appearance and behavior, and that Open UI hopes to make that reinvention unnecessary. It adds that design systems choosing to build their own controls are expected to benefit from Open UI's specifications and test suites. So contributors with backgrounds in specification writing, accessibility, testing, or polyfill implementation are the natural audience — though the site does not restrict participation to those groups.
Practical Next Steps
- Read the full charter linked from the site to understand the goals and process before committing time.
- Join the Discord to follow discussions and ask where help is needed.
- Check GitHub for the specifications, test suites, and polyfills referenced on the page.
- If you maintain a design system, review the specifications and test suites to see whether they apply to controls you currently build yourself.
The site does not state any membership requirements, fees, or login restrictions for these channels, so treat access terms as something to confirm on Discord and GitHub directly.