Vocabulary Reference

The complete data-attribute index. Every attribute in ASW, with a link to its dedicated docs page.

The vocabulary is finite by design. If it isn't listed here, don't use it. Each attribute links to the page where it's documented in full — with examples, live demos, and tokens.

Vault Extensions

Attributes that originate in knowledge management — Obsidian, wikis, task trackers.

AttributeValuesPurposeDocs
data-wikilink (boolean) Mark as vault note reference Wikilinks
data-unresolved (boolean) Mark wikilink target as missing Wikilinks
data-tag (boolean) Vault tag styling Wikilinks
data-task todo done blocked cancelled Task state indicator Tasks
data-status awake sleeping blocked unknown System or service status Status
data-session (boolean) Session metadata wrapper Session
data-mode autonomous interactive Session type indicator Session
data-session-meta (boolean) Session timestamp / metadata line Session
data-hash (boolean) Git commit hash for provenance Session

Text & Utilities

AttributeValuesPurposeDocs
data-text mono dim accent small Inline text treatment — composable, e.g. "mono dim" Utilities
data-visible desktop mobile Responsive show/hide Utilities
data-role status-card diff command-box log-entry prev-next Semantic display role Utilities

Layout

AttributeValuesPurposeDocs
data-layout prose Reading column, 65ch centered Prose
grid-2 Two-column grid, stacks on mobile Grid
grid-3 Three-column grid, stacks on mobile Grid
card-grid Responsive card wrap Grid
stats Horizontal metrics bar Grid
inline Inline definition list Prose
timeline Chronological event list with left-border spine Timeline
timeline alternate Timeline alternating left/right on wide screens Timeline
docs Three-column docs layout: sidebar + content + aside Docs Layout
report Print-first A4 page Prose
fluid Full-width, removes reading constraint Prose

Components

AttributeValuesPurposeDocs
data-callout note tip warning error Callout / admonition type Callouts
data-callout-title (boolean) Title element inside a callout Callouts
data-tooltip Any string Hover/focus tooltip text — no JavaScript Tooltips
data-tooltip-position bottom Place tooltip below instead of above Tooltips
aria-busy true Loading indicator — spinner on buttons, overlay on blocks Buttons

AI Disclosure

Element-level provenance attributes. For page-level disclosure, see AI Disclosure.

AttributeValuesPurposeDocs
ai-disclosure ai-generated ai-assisted autonomous mixed AI provenance of this element — adds visual treatment AI Disclosure
ai-model Any string Model identifier for this element AI Disclosure
data-show-disclosure (boolean) Display an inline disclosure badge AI Disclosure

Charts

Data-driven charts from semantic <table> elements. See Charts for full documentation and live demos.

AttributeValuesPurposeDocs
data-chart bar column area line pie Chart type — on <table> Charts
data-chart-labels (boolean) Show axis labels from <thead> Charts
data-chart-spacing 15 Gap between bars/columns Charts
data-chart-stacked (boolean) Stack multiple datasets Charts
style="--size: N" 0–1 fraction Data value on <td> — the one legal inline style Charts
data-value Any string Label shown after bar — on <td> Charts

Conventions

  1. All data values in monospace. Status indicators, session numbers, timestamps, file paths, hashes — if it's data, use data-text="mono" or wrap in <code>.
  2. Combine attributes freely. data-text="mono dim", data-wikilink data-unresolved, etc.
  3. Semantic HTML first. If HTML has a tag for it, use that tag. Data-attributes are for concepts HTML doesn't cover.
  4. No inline styles. style="" is forbidden except for CSS custom properties representing data values (e.g., style="--size: 0.8" for charts).
  5. No invented classes. The vocabulary is finite and documented here. Don't extend without documenting.

Extending the Vocabulary

Need a new data-attribute? Document four things:

  1. What concept you're expressing
  2. Why existing patterns don't work
  3. Proposed attribute name and values
  4. CSS styling needed (if known)
Resist bloat

The vocabulary's power comes from being finite. Every addition has a cost. Prefer composing existing attributes over inventing new ones.