LogoLogo
  • What is UDML?
  • Document structure
    • <components>
    • <imports>
    • <instructions>
    • <meta>
    • <styles>
    • <tokens>
    • <mappings>
    • <screens>
  • Directives
    • ai-hint
    • <data> Directive Specification
    • <interaction> Directive
    • <layer> Directive
    • <repeat> Directive
    • <responsive>
    • selection
    • <tracking> Directive
  • Components
    • Layout
      • <accordion> Component
      • <box> Component
      • <column> Component
      • <divider>
      • <grid> Component
      • <row> Component
    • Navigation
      • <breadcrumbs> Component
      • <pagination> Component
      • <tab> Component
      • <tabs> Component
    • Text & Display
      • <avatar>
      • <heading>
      • <icon>
      • <image>
      • <label>
      • <text>
      • <video>
    • Controls & Input
      • <button>
      • <checkbox>
      • <input> Component
      • <radio>
      • <select>
      • <slider>
      • <stepper>
      • <switch>
      • <textarea>
    • Forms
      • <form> Component
      • <formField> Component
      • <formGroup> Component
    • Data Collections
      • <dataColumn> Component
      • <dataTable> Component
      • <list> Component
      • <timeline> Component
      • <treeView> Component
    • Data Visualization
      • <chart> Component
      • <summary> Component
    • Modals
      • <dialog> Component
      • <modal> Component
      • <popover> Component
      • <toast> Component
      • <tooltip> Component
  • Prompting Guides
    • Prompting AI Developer Tools with UDML
    • Working with UDML in an Existing Codebase
  • Contributing to UDML
Powered by GitBook
On this page
  • 🧠 What We're Looking For
  • 📐 Design Language Improvements
  • 🧩 New Components or Missing Patterns
  • 🔌 Integration Ideas
  • 🛠 How to Contribute
  • 📄 Format Guidelines
  • 🙌 Thank You!
Edit on GitHub

Contributing to UDML

Thanks for your interest in contributing to UDML — the Universal Design Markup Language!

We're building a shared, semantic vocabulary for describing user interfaces in a way that's intuitive for designers, actionable for AI agents, and portable across platforms. Your insights and input can help make UDML more complete, more useful, and more future-proof.

🧠 What We're Looking For

We're especially interested in contributions around:

📐 Design Language Improvements

  • Proposing better ways to express layout, styles, or structure

  • Suggestions for standardizing terminology across components

  • Ideas for making the spec more expressive or easier to understand

🧩 New Components or Missing Patterns

  • Adding components we’ve missed (e.g., advanced inputs, rich tables, animation primitives)

  • Enhancing support for interaction or accessibility features

  • Comparing patterns used in other design systems or tools

🔌 Integration Ideas

  • Suggestions for how UDML could connect with Figma, design tokens, codegen tools, or AI workflows

  • Ideas for plugins, tooling, or export pipelines

🛠 How to Contribute

  2. Open an issue – Report a bug, suggest a feature, or share a use case.

  3. Submit a pull request – Propose changes to the spec or documentation. We’ll help guide the process.

✨ You don’t need to be an expert in design systems or AI to contribute — we welcome ideas, questions, and constructive feedback from all backgrounds.

📄 Format Guidelines

  • Most of the spec is documented as individual .md files (one per component)

  • Follow the structure used in existing specs: attributes table, usage examples, and AI guidelines

  • Keep language clear and focused — our goal is readability for both humans and machines

🙌 Thank You!

UDML is an experiment, a collaboration, and a challenge — and it gets better with every contributor.

We appreciate your time, ideas, and perspective 💙

PreviousWorking with UDML in an Existing Codebase

Last updated 1 month ago

Start a discussion – If you're not sure where to begin, head to the tab.

Discussions