Buttons and tags
Square labels in exhibit black. They turn tomato under the pointer.
Stable Class names and props are not expected to change before 1.0.
In this chapter 15 pages
Buttons
<div class="ply-cluster">
<button class="ply-button" type="button">Read the paper</button>
<button class="ply-button ply-button--secondary" type="button">BibTeX</button>
<button class="ply-button ply-button--ghost" type="button">Cancel</button>
<button class="ply-button ply-button--sm" type="button">Small</button>
<button class="ply-button" type="button" disabled>Disabled</button>
<button class="ply-button" type="button" aria-busy="true"><span class="ply-loading" aria-hidden="true"><i></i></span>Running</button>
</div>- Use one primary button per view, for the action most readers came for. Everything else is secondary or ghost.
- Label buttons with the action: "Read the paper", "Copy BibTeX", "Run again". Not "Click here" or "Submit".
- A link that looks like a button is fine: put the classes on an
<a>. - While an action runs, set
aria-busy="true"and add the small machine as a spinner.
<Button href="/paper.pdf">Read the paper</Button>
<Button variant="secondary">BibTeX</Button>
<Button busy>Running</Button>| Prop | Effect | Default |
|---|---|---|
variant | primary, secondary, or ghost | primary |
size | md or sm | md |
href | Renders an <a> instead of a <button> | |
icon | Square icon-only button. Give it an aria-label. | false |
busy | Shows the loading machine and sets aria-busy | false |
Tags
<div class="ply-cluster">
<span class="ply-tag">NeurIPS 2026</span>
<span class="ply-tag ply-tag--solid">Oral</span>
<span class="ply-tag ply-tag--note">New</span>
</div>Tags name a venue, a type, or a topic. A tag that filters something is a real button or link.
Link tags
A topic tag that leads to a list of its papers is a link. .ply-tag--link keeps the tag's shape and takes the link's look: teal, underlined, at least 28px tall (44px under a finger), filled with ink on hover. The current tag is the solid one, without the underline, and carries aria-current="page". .ply-tag-list sets a ul of tags as a wrapping row, also inside .ply-prose, where list items would otherwise take the prose spacing.
<ul class="ply-tag-list" role="list" aria-label="Topics">
<li><a class="ply-tag ply-tag--link" href="#" rel="tag">Topology</a></li>
<li><a class="ply-tag ply-tag--link ply-tag--solid" href="#" rel="tag" aria-current="page">Sheaves</a></li>
<li><a class="ply-tag ply-tag--link" href="#" rel="tag">Graph learning</a></li>
</ul>The Tag component writes the same markup. href makes it a link, and current marks the tag for the page showing, as the solid tag with aria-current="page". Other attributes, such as rel or data attributes for analytics, go on the element. Put the tags in a ul class="ply-tag-list".
<ul class="ply-tag-list" aria-label="Topics">
<li><Tag href="/topics/sheaves/" rel="tag" current>Sheaves</Tag></li>
<li><Tag href="/topics/topology/" rel="tag">Topology</Tag></li>
</ul>Status
<div class="ply-cluster" style="--ply-cluster-gap: 1.5rem">
<span class="ply-status ply-status--idle">Idle</span>
<span class="ply-status ply-status--running">Training</span>
<span class="ply-status ply-status--done">Converged</span>
<span class="ply-status ply-status--warning">Loss plateau</span>
<span class="ply-status ply-status--error">Diverged</span>
</div>Status always pairs a mark with a word, so it reads without color: an empty ring for idle, a pulsing ball for running, a check, a triangle, and a cross. Use it in demo status lines and experiment tables.
<Status state="running">Training</Status>When a script changes the status, add live so screen readers announce it: <Status state="running" live>. Inside an app shell, leave it off; the status bar is already a live region.