CORE CONCEPTSAvailable
UXDL Glossary
Alphabetical reference of canonical terms, validator codes, and linter terminology used in UXDL specifications.
Alphabetical Glossary
- Action — An interactive trigger initiated by an actor on a screen (e.g. submit_credentials, retry_payment).
- Actor — A human user (type: human) or system service (type: system) initiating actions in the experience graph.
- Address — A deterministic dot-separated path targeting a specific UXDL element (e.g. billing.actions.retry_payment.relations.success).
- Canvas — The spatial, visual flowchart editor view for UXDL interaction graphs.
- Contextual Finding — An advisory heuristic linter observation regarding product flow completeness (e.g. dead-end screen, missing recovery path).
- Document — The structured textual editor view projecting UXDL metadata, requirements, and acceptance criteria.
- External Relation — A relation targeting a URL outside the modeled experience (e.g. external: 'https://stripe.com').
- Group — An editor-managed cluster of screens grouping related feature surfaces on Canvas.
- Metadata — Open key-value store holding non-normative product, design, analytics, or security context.
- Module — An individual UXDL YAML file declared inside uxdl.project.yaml in multi-file projects.
- Parent — Host screen ID referenced by sub-screens (e.g. modal parent: billing).
- Relation — A directed edge defining the transition outcome following an action.
- Screen — The primary addressable user-interface surface or modal node in UXDL.
- Slice — A bounded requirement scope mapping user stories or tasks to screen anchors and acceptance criteria.
- State — A distinct variant condition or status of a screen surface (e.g. past_due, loading, empty).
- Structural Validation — Deterministic checks verifying syntax, snake_case identifiers, and target references.