Built with Nuxt and Vue.js, hosted on Cloudflare. Domain registered in 2026.
opencomponents.dev is built with Nuxt, hosted on Cloudflare. It measures traffic with Amplitude and Cloudflare Web Analytics.
| Technology | Version | First seen |
|---|---|---|
| JavaScript Frameworks & Libraries2 | ||
| – | 6 Nov 2026 | |
| – | 6 Nov 2026 | |
| Web Servers, Languages & Backend Frameworks1 | ||
| CDN & Hosting1 | ||
| – | 6 Nov 2026 | |
| Analytics & Tag Management2 | ||
| – | 6 Nov 2026 | |
| Fonts & Icon Fonts1 | ||
| – | 6 Nov 2026 | |
Registration from the registry's RDAP record, the certificate the site serves, and its rank in public traffic lists.
The crew hasn’t read this site’s colors yet. We read a palette when we capture a site’s screenshot, busiest sites first. Meanwhile, browse palettes from other sites.
Counted from every stack change we've recorded: of the sites we watched running one of this site's tools, how many went on to add another. A pattern across sites, not a forecast for this one.
aspmx.l.google.comalt2.aspmx.l.google.comalt1.aspmx.l.google.comalt4.aspmx.l.google.comalt3.aspmx.l.google.comwesley.ns.cloudflare.comjourney.ns.cloudflare.comgoogle-site-verification=-aa8k0m068qZfXQypqPyCYeOWpxL70BSvY-WIaY6ssMv=spf1 include:_spf.google.com ~all# START nuxt-robots (indexable) User-agent: * Allow: / Sitemap: https://opencomponents.dev/sitemap.xml # END nuxt-robots
# Open Components ## Documentation Sets - [Open Components](https://opencomponents.dev/llms-full.txt) ## MCP Server The Open Components MCP server, over streamable HTTP: the contracts, every rule and the docs, a section at a time, for agents to build and review components with. - [Open Components MCP server](https://mcp.opencomponents.dev/mcp): Connect an MCP client to this URL, with no authentication - [MCP Server](https://opencomponents.dev/raw/docs/getting-started/mcp-server.md): How to connect it to Claude Code, Cursor, VS Code and other clients, and what it offers ## Agent Plugin The Open Components agent plugin, for clients that support Agent Plugins: skills that build and review components rule by rule, and the MCP server they read the standard from. - [Agent Plugin](https://opencomponents.dev/raw/docs/getting-started/agent-plugin.md): How to install it in VS Code, GitHub Copilot, Cursor, Codex, Claude Code and other clients, and what it offers - [Open Components agent plugin](https://github.com/uxfront-com/open-components/tree/main/plugins/open-components): The plugin itself: its manifest, its MCP configuration and its skills ## Contracts Every requirement for a component or convention, rules included, in one YAML file. - [Design Tokens](https://opencomponents.dev/raw/docs/foundations/design-tokens.yaml): The Design Tokens contract, with every rule from its checklist - [Button](https://opencomponents.dev/raw/docs/components/button.yaml): The Button contract, with every rule from its checklist - [Card](https://opencomponents.dev/raw/docs/components/card.yaml): The Card contract, with every rule from its checklist - [Checkbox Group](https://opencomponents.dev/raw/docs/components/checkbox-group.yaml): The Checkbox Group contract, with every rule from its checklist - [Checkbox](https://opencomponents.dev/raw/docs/components/checkbox.yaml): The Checkbox contract, with every rule from its checklist - [Dialog](https://opencomponents.dev/raw/docs/components/dialog.yaml): The Dialog contract, with every rule from its checklist - [Field](https://opencomponents.dev/raw/docs/components/field.yaml): The Field contract, with every rule from its checklist - [Input](https://opencomponents.dev/raw/docs/components/input.yaml): The Input contract, with every rule from its checklist - [Popover](https://opencomponents.dev/raw/docs/components/popover.yaml): The Popover contract, with every rule from its checklist - [Radio Group](https://opencomponents.dev/raw/docs/components/radio-group.yaml): The Radio Group contract, with every rule from its checklist - [Spinner](https://opencomponents.dev/raw/docs/components/spinner.yaml): The Spinner contract, with every rule from its checklist - [Switch](https://opencomponents.dev/raw/docs/components/switch.yaml): The Switch contract, with every rule from its checklist - [Textarea](https://opencomponents.dev/raw/docs/components/textarea.yaml): The Textarea contract, with every rule from its checklist - [Tooltip](https://opencomponents.dev/raw/docs/components/tooltip.yaml): The Tooltip contract, with every rule from its checklist - [Contract schema](https://opencomponents.dev/schemas/contract.json): The JSON Schema every contract follows, for validating them, and contracts of your own ## Docs - [Introduction](https://opencomponents.dev/raw/docs/getting-started/introduction.md): Open Components is the standard for perfect UI components, with a perfect user experience, developer experience and agentic experience. - [Roadmap](https://opencomponents.dev/raw/docs/getting-started/roadmap.md): The components we're bringing to the standard, in the order we plan to ship them, and what goes into every page. - [MCP Server](https://opencomponents.dev/raw/docs/getting-started/mcp-server.md): Connect your agents to the standard, so they can read the contracts, every rule and the docs a section at a time as they build and review components. - [Agent Plugin](https://opencomponents.dev/raw/docs/getting-started/agent-plugin.md): Install the standard in your agent as one plugin, with skills that build and review components rule by rule, and our MCP server. - [Design Tokens](https://opencomponents.dev/raw/docs/foundations/design-tokens.md): How to name the CSS variables behind your components, so that people, tools and agents all read them the same way. - [User Interface (UI)](https://opencomponents.dev/raw/docs/components/button/ui.md): How a button looks, from its parts, variants and colours to its sizes, icons, states and tokens. - [User Experience (UX)](https://opencomponents.dev/raw/docs/components/button/ux.md): How a button behaves for every person, input and setting, so it's accessible, predictable, clear in every state and adaptive. - [Developer Experience (DX)](https://opencomponents.dev/raw/docs/components/button/dx.md): How developers use the Button, with one consistent, typed API that composes with links, routers and other components. - [Agentic Experience (AX)](https://opencomponents.dev/raw/docs/components/button/ax.md): How agents read, build and check a button, from its accessibility tree to its contract, its DOM and its tests. - [Button](https://opencomponents.dev/raw/docs/components/button.md): How to build a button that looks right, works for everyone, feels familiar to every developer and can be checked by your agents. - [User Interface (UI)](https://opencomponents.dev/raw/docs/components/card/ui.md): How a card looks, from its parts and what goes in each of them to how cards sit together, its states and its tokens. - [User Experience (UX)](https://opencomponents.dev/raw/docs/components/card/ux.md): How a card behaves for every person, input and setting, so it's accessible, predictable, clear in every state and adaptive. - [Developer Experience (DX)](https://opencomponents.dev/raw/docs/components/card/dx.md): How developers use the Card, with one consistent, typed API that composes with links, routers and other components, and needs no script. - [Agentic Experience (AX)](https://opencomponents.dev/raw/docs/components/card/ax.md): How agents read, build and check a card, from its accessibility tree to its contract, its DOM and its tests. - [Card](https://opencomponents.dev/raw/docs/components/card.md): How to build a card that groups what people need to know about one thing, that keyboard and screen reader users can move through, and that agents can check. - [User Interface (UI)](https://opencomponents.dev/raw/docs/components/checkbox-group/ui.md): How a checkbox group looks, from its parts, sizes and orientation to its states and tokens. - [User Experience (UX)](https://opencomponents.dev/raw/docs/components/checkbox-group/ux.md): How a checkbox group behaves for every person, input and setting, so it's accessible, predictable, clear in every state and adaptive. - [Developer Experience (DX)](https://opencomponents.dev/raw/docs/components/checkbox-group/dx.md): How developers use the Checkbox Group, with one consistent, typed API that's built from Checkboxes and works with your forms however you build them. - [Agentic Experience (AX)](https://opencomponents.dev/raw/docs/components/checkbox-group/ax.md): How agents read, build and check a checkbox group, from its accessibility tree to its contract, its DOM and its tests. - [Checkbox Group](https://opencomponents.dev/raw/docs/components/checkbox-group.md): How to build a group of checkboxes that people can pick any number of options from, that's named by its question, that says when they need to pick one, and that agents can check. - [User Interface (UI)](https://opencomponents.dev/raw/docs/components/checkbox/ui.md): How a checkbox looks, from its parts and sizes to its states and tokens. - [User Experience (UX)](https://opencomponents.dev/raw/docs/components/checkbox/ux.md): How a checkbox behaves for every person, input and setting, so it's accessible, predictable, clear in every state and adaptive. - [Developer Experience (DX)](https://opencomponents.dev/raw/docs/components/checkbox/dx.md): How developers use the Checkbox, with one consistent, typed API that works with your forms however you build them. - [Agentic Experience (AX)](https://opencomponents.dev/raw/docs/components/checkbox/ax.md): How agents read, build and check a checkbox, from its accessibility tree to its contract, its DOM and its tests. - [Checkbox](https://opencomponents.dev/raw/docs/components/checkbox.md): How to build a checkbox that people can check with a click on its label, that says what it means and when it's mixed, that forms send the way they expect, and that agents can check. - [User Interface (UI)](https://opencomponents.dev/raw/docs/components/dialog/ui.md): How a dialog looks, from its parts and how wide it gets to what goes in it, how it shows that it's open and its tokens. - [User Experience (UX)](https://opencomponents.dev/raw/docs/components/dialog/ux.md): How a dialog behaves for every person, input and setting, so it's accessible, predictable, clear in every state and adaptive. - [Developer Experience (DX)](https://opencomponents.dev/raw/docs/components/dialog/dx.md): How developers use the Dialog, with one consistent, typed API that composes with forms and other components and leaves when to open and close it to you. - [Agentic Experience (AX)](https://opencomponents.dev/raw/docs/components/dialog/ax.md): How agents read, open and check a dialog, from its accessibility tree to its contract, its DOM and its tests. - [Dialog](https://opencomponents.dev/raw/docs/components/dialog.md): How to build a modal dialog that takes focus and gives it back, that everyone can close, that developers control and that agents can check. - [User Interface (UI)](https://opencomponents.dev/raw/docs/components/field/ui.md): How a field looks, from its parts and where they go around each kind of control to its sizes, states and tokens. - [User Experience (UX)](https://opencomponents.dev/raw/docs/components/field/ux.md): How a field behaves for every person and setting, so its control is named, described and marked required or invalid the way assistive technologies expect. - [Developer Experience (DX)](https://opencomponents.dev/raw/docs/components/field/dx.md): How developers use the Field, with one typed API that labels, describes and validates every form control, without changing any of them. - [Agentic Experience (AX)](https://opencomponents.dev/raw/docs/components/field/ax.md): How agents read, fill in and check a field, from its accessibility tree to its contract, its DOM and its tests. - [Field](https://opencomponents.dev/raw/docs/components/field.md): How to build a field that labels, describes and explains the errors of any form control, works for everyone, feels familiar to every developer and can be checked by your agents. - [User Interface (UI)](https://opencomponents.dev/raw/docs/components/input/ui.md): How an input looks, from its parts and sizes to its icons, prefixes, actions, states, width and tokens. - [User Experience (UX)](https://opencomponents.dev/raw/docs/components/input/ux.md): How an input behaves for every person, input and setting, so it's accessible, predictable, clear in every state and adaptive. - [Developer Experience (DX)](https://opencomponents.dev/raw/docs/components/input/dx.md): How developers use the Input, with one consistent, typed API that works with any form and other components, whether its value is bound or not. - [Agentic Experience (AX)](https://opencomponents.dev/raw/docs/components/input/ax.md): How agents read, fill in and check an input, from its accessibility tree to its contract, its DOM and its tests. - [Input](https://opencomponents.dev/raw/docs/components/input.md): How to build a text input that people can label, fill in and fix, that works with every keyboard, autofill and password manager, and that agents can check. - [User Interface (UI)](https://opencomponents.dev/raw/docs/components/popover/ui.md): How a popover looks, from its parts and where it opens to what goes in it, its states and its tokens. - [User Experience (UX)](https://opencomponents.dev/raw/docs/components/popover/ux.md): How a popover behaves for every person, input and setting, so it's accessible, predictable, clear in every state and adaptive. - [Developer Experience (DX)](https://opencomponents.dev/raw/docs/components/popover/dx.md): How developers use the Popover, opened by a Button with popovertarget, with one typed API and an open state that follows every open and close. - [Agentic Experience (AX)](https://opencomponents.dev/raw/docs/components/popover/ax.md): How agents read, open and check a popover, from its accessibility tree to its contract, its DOM and its tests. - [Popover](https://opencomponents.dev/raw/docs/components/popover.md): How to build a popover that shows more next to what opened it, leaves the rest of the page working, opens and closes the way people expect and can be checked by your agents. - [User Interface (UI)](https://opencomponents.dev/raw/docs/components/radio-group/ui.md): How a radio group looks, from its parts and sizes to its states, layout and tokens. - [User Experience (UX)](https://opencomponents.dev/raw/docs/components/radio-group/ux.md): How a radio group behaves for every person, input and setting, so it's accessible, predictable, clear in every state and adaptive. - [Developer Experience (DX)](https://opencomponents.dev/raw/docs/components/radio-group/dx.md): How developers use the Radio Group, with one consistent, typed API that works with your forms however you build them. - [Agentic Experience (AX)](https://opencomponents.dev/raw/docs/components/radio-group/ax.md): How agents read, fill in and check a radio group, from its accessibility tree to its contract, its DOM and its tests. - [Radio Group](https://opencomponents.dev/raw/docs/components/radio-group.md): How to build a radio group that asks one clear question, lets people pick one answer with a pointer or the arrow keys, says what's wrong when they skip it, and that agents can check. - [User Interface (UI)](https://opencomponents.dev/raw/docs/components/spinner/ui.md): How a spinner looks, from its parts, size and colour to how it moves and the one variable you can set. - [User Experience (UX)](https://opencomponents.dev/raw/docs/components/spinner/ux.md): How a spinner behaves for every person and setting, so it's accessible, predictable, clear in every state and adaptive. - [Developer Experience (DX)](https://opencomponents.dev/raw/docs/components/spinner/dx.md): How developers use the Spinner, with no props, events or slots, and one implementation that every component shares. - [Agentic Experience (AX)](https://opencomponents.dev/raw/docs/components/spinner/ax.md): How agents read, build and check a spinner, from the text around it to its contract, its DOM and its tests. - [Spinner](https://opencomponents.dev/raw/docs/components/spinner.md): How to build a spinner that shows something is busy, without getting in the way of screen readers, reduced motion or the layout around it. - [User Interface (UI)](https://opencomponents.dev/raw/docs/components/switch/ui.md): How a switch looks, from its parts and sizes to its states and tokens. - [User Experience (UX)](https://opencomponents.dev/raw/docs/components/switch/ux.md): How a switch behaves for every person, input and setting, so it's accessible, predictable, clear in every state and adaptive. - [Developer Experience (DX)](https://opencomponents.dev/raw/docs/components/switch/dx.md): How developers use the Switch, with one consistent, typed API that works with your forms and leaves its state to you or the browser. - [Agentic Experience (AX)](https://opencomponents.dev/raw/docs/components/switch/ax.md): How agents read, build and check a switch, from its accessibility tree to its contract, its DOM and its tests. - [Switch](https://opencomponents.dev/raw/docs/components/switch.md): How to build a switch that turns a setting on or off right away, that everyone can see, label and flip, and that agents can check. - [User Interface (UI)](https://opencomponents.dev/raw/docs/components/textarea/ui.md): How a textarea looks, from its parts and sizes to how tall it gets, its count, its states and its tokens. - [User Experience (UX)](https://opencomponents.dev/raw/docs/components/textarea/ux.md): How a textarea behaves for every person, input and setting, so it's accessible, predictable, clear in every state and adaptive. - [Developer Experience (DX)](https://opencomponents.dev/raw/docs/components/textarea/dx.md): How developers use the Textarea, with the Input's consistent, typed API that works with your forms however you build them. - [Agentic Experience (AX)](https://opencomponents.dev/raw/docs/components/textarea/ax.md): How agents read, fill in and check a textarea, from its accessibility tree to its contract, its DOM and its tests. - [Textarea](https://opencomponents.dev/raw/docs/components/textarea.md): How to build a textarea that people can label, write in at length and fix, that grows or resizes without cutting anything off, and that agents can check. - [User Interface (UI)](https://opencomponents.dev/raw/docs/components/tooltip/ui.md): How a tooltip looks, from its parts and the two jobs it can do to where it opens, its states and its tokens. - [User Experience (UX)](https://opencomponents.dev/raw/docs/components/tooltip/ux.md): How a tooltip behaves for every person, input and setting, so it's accessible, predictable, clear in every state and adaptive. - [Developer Experience (DX)](https://opencomponents.dev/raw/docs/components/tooltip/dx.md): How developers use the Tooltip, with one consistent, typed API that you wrap around any trigger and that handles when to open, where and for whom. - [Agentic Experience (AX)](https://opencomponents.dev/raw/docs/components/tooltip/ax.md): How agents read, build and check a tooltip, from its accessibility tree to its contract, its DOM and its tests. - [Tooltip](https://opencomponents.dev/raw/docs/components/tooltip.md): How to build a tooltip that shows a short hint on hover and keyboard focus, that people can reach, read and dismiss, and that agents can check. ## Changelog - [The agent plugin](https://opencomponents.dev/raw/changelog/agent-plugin.md): Install the standard in your agent as one plugin, with skills that build and review components rule by rule, and our MCP server. - [The Button](https://opencomponents.dev/raw/changelog/button.md): Our first component page, on building a button that looks right, works for everyone, feels familiar to every developer and can be checked by your agents. - [The Button, a page per layer](https://opencomponents.dev/raw/changelog/button-sub-pages.md): The Button's page is now an Overview with a page for each of its UI, UX, DX and AX layers, each with its own rules, so you can read one layer at a time. - [The Card](https://opencomponents.dev/raw/changelog/card.md): Our fourth component page, on a card that groups what people need to know about one thing, that keyboard and screen reader users can move through, and that agents can check. - [The Checkbox](https://opencomponents.dev/raw/changelog/checkbox.md): Our fourth component page, on a checkbox that people can check with a click on its label, that says what it means and when it's mixed, that forms send the way they expect, and that agents can check. - [The Checkbox Group](https://opencomponents.dev/raw/changelog/checkbox-group.md): A new component page, on a group of checkboxes that its question names, that people can pick any number of options from, with a select-all box that's never out of step, and that agents can check. - [Every component, a page per layer](https://opencomponents.dev/raw/changelog/component-sub-pages.md): The Card, Checkbox, Checkbox Group, Dialog, Input, Radio Group, Spinner, Switch, Textarea and Tooltip pages now each have an Overview and a page for each of their UI, UX, DX and AX layers, like the Button's. - [A schema for contract
| – |
| 6 Nov 2026 |
| – |
| 6 Nov 2026 |