A stylesheet that styles HTML elements by what they are and where they sit. Write semantic markup and link the sheet, and the page gets the FivePaths layout, a light and a dark scheme, and text that clears WCAG AAA contrast.
Every text and background pairing clears 7:1. The repository's contract test measures each one against the least favorable ground it can land on.
AAA
How the framework is designed
The approach in brief, for a developer deciding whether to build a website, an application or another HTML interface on it.
Elements instead of class names
Most CSS frameworks give you a set of classes to learn and put on divs. This one styles the HTML elements themselves, by what they are and where they sit. A section is a full-width band. A ul is a bulleted list, and the same ul with data-list="cards" is a grid of cards. Five classes remain, for the few cases no element covers, such as a secondary button.
Why the nesting matters
Because the rules match on position, the nesting has to be exact. A heading wrapped in an extra div loses its styling, and nothing reports an error. That makes v3 a good fit for markup produced by templates, components or an assistant that keeps to the patterns on this page. Markup edited freely by hand is better served by v2, which uses classes and stays supported.
The brand lives in tokens
Colors, fonts and spacing are CSS custom properties. A project on another brand overrides them and keeps every component. Dark bands reuse the same components with the token values swapped, so nothing needs a dark version of its own. Tokens come in groups, and a group is replaced all at once, because the contrast test measures the colors in a group against each other.
On this page
Set up a page
Link a release in the head. Everything after that is HTML.
Pin the release. A release is published once and never changes, so the sheet you reviewed is the sheet visitors receive. The current release is 3.7.1; base.css with no number follows the newest.
The first element in the body is the skip link. It stays off screen until it has focus.
The header is a brand link and then a nav. aria-current marks the page you are on, and class="ink" marks the header's one call to action.
Only a direct child of a section is placed in the content column. A div wrapped round a section's content takes it out of the grid.
The footer's first paragraph is the byline row, and its small is the fine print.
The site's own sheet
A site's own rules go in site.css, linked after the framework. The framework's rules sit in cascade layers and a site sheet does not, so a site rule wins without extra specificity. A name the site invents carries the site's prefix.
site.css
/* What this site has and the framework does not */[data-example-map] {
aspect-ratio: 4 / 3;
border: 1px solid var(--fp-rule);
border-radius: var(--fp-radius);
}
Structure
Sections and bands
A section is a band across the page, and data-band picks its ground.
Markupmain > section > header
<header>
<p>Structure</p>
<h2>Sections and bands</h2>
<p>A section is a band across the page, and <code>data-band</code> picks its ground.</p>
</header>
A p before the heading is an eyebrow, and the p after it is the lead. Give an eyebrow only to the few sections that need one.
Band values
data-band
Ground
none
The page ground.
alt
The alternate ground, for every other section.
dark
The near-black ground. Everything inside re-reads its tokens and adapts.
hero
The opening band, dark, carrying the page's h1.
proof
One line of claim beside a chip, dark.
cta
The closing band, dark and centered.
strip
A thin band between two rules.
data-tight on any band gives it less vertical padding.
Wider than the column
data-width="wide" takes the wider track. "full" runs to the viewport edges and drops the frame.Markup: Wider than the columnmain > section > [data-width="wide"]
<figuredata-width="wide">
<imgsrc="example-screen.svg"alt="A page laid out in the framework: a header, a dark hero, and three cards"width="1600"height="1000">
<figcaption><code>data-width="wide"</code> takes the wider track. <code>"full"</code> runs to the viewport edges and drops the frame.</figcaption>
</figure>
Lists and groups
A list in main is styled by being one. data-list picks a shape that needs a grid.
A list
Each item gets a drawn dot, so nothing falls back to a missing glyph.
Running text is capped at a readable measure.
Markup: A listmain ul:not([data-list])
<ul>
<li>Each item gets a drawn dot, so nothing falls back to a missing glyph.</li>
<li>Running text is capped at a readable measure.</li>
</ul>
A list of checks
Both color schemes
A 44px target on every control
Markup: A list of checksmain ul[data-marker="check"]
<uldata-marker="check">
<li>Both color schemes</li>
<li>A 44px target on every control</li>
</ul>
A numbered list
Link the release.
Write the markup.
Check both schemes.
Markup: A numbered listmain ol:not([data-list])
<ol>
<li>Link the release.</li>
<li>Write the markup.</li>
<li>Check both schemes.</li>
</ol>
Steps
Pin a release
The sheet you reviewed is the sheet you serve.
Write elements
Their position carries the layout.
Run the checks
Contrast, targets and reflow, in both schemes.
Markup: Stepsol[data-list="steps"]
<oldata-list="steps">
<li><h3>Pin a release</h3><p>The sheet you reviewed is the sheet you serve.</p></li>
<li><h3>Write elements</h3><p>Their position carries the layout.</p></li>
<li><h3>Run the checks</h3><p>Contrast, targets and reflow, in both schemes.</p></li>
</ol>
Its content sits in a div and gets the same padding.
Three across
data-cols sets the count once there is room for it.
Markup: Cardsul[data-list="cards"]
<uldata-list="cards"data-cols="3">
<li><ahref="#tokens">
<h3>A card that links</h3>
<p>The link fills the card, so the whole card is the target.</p>
<span>See the tokens</span>
</a></li>
<li><div>
<h3>A card that does not</h3>
<p>Its content sits in a div and gets the same padding.</p>
</div></li>
<li><div>
<h3>Three across</h3>
<p><code>data-cols</code> sets the count once there is room for it.</p>
</div></li>
</ul>
<divdata-actions>
<ahref="#start">Set up a page</a>
<ahref="base.css">Read base.css</a>
</div>
The first link is the primary action and takes the fill; the rest are secondary. A second primary needs a second group. ghost, ink and teal name a variant where position cannot.
Layouts and blocks
A two-column layout is named in data-layout. A figure is framed by what it holds.
Split panels
One option
Each child is a panel.
The other
data-band="dark" on a panel re-points its tokens, so it reads correctly with no rules of its own.
Markup: Split panels[data-layout="split"]
<divdata-layout="split">
<div>
<h3>One option</h3>
<p>Each child is a panel.</p>
</div>
<divdata-band="dark">
<h3>The other</h3>
<p><code>data-band="dark"</code> on a panel re-points its tokens, so it reads correctly with no rules of its own.</p>
</div>
</div>
A grid
A figure takes a column.
Columns
As many as fit, each at least 15.5rem.
data-cols
2, 3 or 4, once there is room.
Markup: A grid[data-layout="grid"]
<divdata-layout="grid">
<figure>
<imgsrc="example-screen.svg"alt="A page laid out in the framework: a header, a dark hero, and three cards"width="1600"height="1000">
<figcaption>A figure takes a column.</figcaption>
</figure>
<aside>
<p>Note</p>
<p>So does a callout, or a panel a site draws itself.</p>
</aside>
<dl>
<dt>Columns</dt><dd>As many as fit, each at least 15.5rem.</dd>
<dt>data-cols</dt><dd>2, 3 or 4, once there is room.</dd>
</dl>
</div>
Columns for children of any kind. Cards are a list and keep their own shape; a grid is the same tracks without the card.
Feature rows
Copy on one side
Two columns that stack below 56rem. flip swaps them, uneven weights them, and top aligns them to the top.
Markup: Feature rows[data-layout~="feature"]
<divdata-layout="feature">
<div>
<h3>Copy on one side</h3>
<p>Two columns that stack below 56rem. <code>flip</code> swaps them, <code>uneven</code> weights them, and <code>top</code> aligns them to the top.</p>
</div>
<figure>
<imgsrc="example-screen.svg"alt="A page laid out in the framework: a header, a dark hero, and three cards"width="1600"height="1000">
</figure>
</div>
<figuretabindex="0"aria-label="Release files">
<table>
<caption>Release files</caption>
<thead><tr><thscope="col">File</th><thscope="col">Changes</th><thscope="col">Path</th></tr></thead>
<tbody>
<tr><thscope="row">The release</th><td>Never</td><td><ahref="base-3.7.1.css"target="_blank">base-3.7.1.css<spanclass="visually-hidden"> (opens in a new tab)</span></a></td></tr>
<tr><thscope="row">The alias</th><td>With each release</td><td><ahref="base.css"target="_blank">base.css<spanclass="visually-hidden"> (opens in a new tab)</span></a></td></tr>
<tr><thscope="row">The token contract</th><td>With each release</td><td><ahref="tokens.json"target="_blank">tokens.json<spanclass="visually-hidden"> (opens in a new tab)</span></a></td></tr>
</tbody>
</table>
</figure>
A table scrolls sideways inside its figure, so the figure takes tabindex="0" and a label to be reachable from the keyboard. Its figures are tabular: each digit takes the same width, so a column of numbers lines up by place. The links here open a new tab and say so in a visually-hidden span, which the figure clips with the table, so a link in a column past the edge of a phone's screen does not widen the page.
A quotation
This sheet is for generated markup, where the component set is closed and a checker fails a build whose structure does not match.
base.css, header commentMarkup: A quotationfigure:has(> blockquote)
<figure>
<blockquote><p>This sheet is for generated markup, where the component set is closed and a checker fails a build whose structure does not match.</p></blockquote>
<figcaption>base.css, header comment</figcaption>
</figure>
The figcaption is the title bar. The classes c, k, m and p on its spans come from a highlighter, for comments, keys, attributes and values.
A definition list
Band
The ground a section sits on.
Measure
The cap on a line of running text, in ch.
Markup: A definition listdl
<dl>
<dt>Band</dt>
<dd>The ground a section sits on.</dd>
<dt>Measure</dt>
<dd>The cap on a line of running text, in <code>ch</code>.</dd>
</dl>
Callouts
Markup: Calloutsaside[data-severity]
<aside>
<p>Note</p>
<p>The first paragraph is the label, so the severity is written as well as colored.</p>
</aside>
<asidedata-severity="warning">
<p>Warning</p>
<p>A published release is never revised. Cut a new one and move the pin.</p>
</aside>
<asidedata-severity="critical">
<p>Important</p>
<p>Every color is a token. A color written as a literal misses the dark scheme and the dark bands.</p>
</aside>
A disclosure
What the triangle shows
It points right while the panel is closed and down once it is open.
Markup: A disclosuredetails > summary
<details>
<summary>What the triangle shows</summary>
<p>It points right while the panel is closed and down once it is open.</p>
</details>
Links
A link in a sentence, like this one to the tokens, keeps the height of its line; data-target marks a link that stands alone.
<p>A link in a sentence, like this one to <ahref="#tokens">the tokens</a>, keeps the height of its line; <code>data-target</code> marks a link that stands alone.</p>
<p><adata-targethref="tokens.json">tokens.json</a> <spanaria-hidden="true">·</span> <adata-targethref="base.css">base.css</a></p>
A link marked with data-target gets a 44px target. The sheet also gives one to a link that is the only element in its paragraph, list item or definition, which is why the first paragraph here holds a code as well.
Chips, blips and fine print
v3BlueGreenRedOrangePurple
Fine print is a small element, in the muted ink.
Markup: Chips, blips and fine print[data-chip], [data-route], small
<p>
<spandata-chip>v3</span>
<spandata-route="blue">Blue</span>
<spandata-route="green">Green</span>
<spandata-route="red">Red</span>
<spandata-route="orange">Orange</span>
<spandata-route="purple">Purple</span>
</p>
<small>Fine print is a small element, in the muted ink.</small>
A route blip is the one place color carries meaning, for data such as a transit line. It is never chrome.
Forms
A form that names its layout gets styled labels, fields and choices. A form without data-layout is left as the browser draws it.
A column of fields
Markup: A column of fieldsform[data-layout="stack"]
<formdata-layout="stack"action="#forms">
<div><labelfor="s-name">Name</label><inputid="s-name"name="name"autocomplete="name"></div>
<div><labelfor="s-email">Email</label><smallid="s-email-hint">Only used to reply.</small><inputid="s-email"type="email"name="email"autocomplete="email"aria-describedby="s-email-hint"></div>
<div><labelfor="s-topic">About</label>
<selectid="s-topic"name="topic"><option>A correction</option><option>The data</option><option>Something else</option></select></div>
<div><labelfor="s-message">Message</label><textareaid="s-message"name="message"></textarea></div>
<fieldset>
<legend>Reply by</legend>
<label><inputtype="radio"name="reply"value="email"checked> Email</label>
<label><inputtype="radio"name="reply"value="phone"> Phone</label>
</fieldset>
<label><inputtype="checkbox"name="copy"> Send me a copy</label>
<divdata-actions><buttontype="submit">Send</button><buttontype="reset">Clear</button></div>
</form>
A field is a div holding its label, a hint in small if it has one, and then its control. A fieldset groups radios or checkboxes, and each choice sits inside its label, which is the 44px target. A reset button is the secondary one.
Switches and sliders
Markup: Switches and slidersform[data-layout] [role="switch"], [type="range"]
<formdata-layout="stack"action="#forms">
<label><inputtype="checkbox"role="switch"name="alerts"checked> Email me when a record changes</label>
<div><labelfor="r-near">Distance from a stop</label>
<inputid="r-near"type="range"name="near"min="100"max="1000"step="100"value="400">
<outputfor="r-near">400 m</output></div>
</form>
A switch is a checkbox with role="switch", for a setting that applies as it changes. A range keeps the browser's slider, in the accent, and its value goes in an output beside it, which this page updates as the slider moves. Both are styled only inside a form that names its layout.
Filters
Markup: Filtersform[data-layout="filters"]
<formdata-layout="filters"action="#forms"role="search"aria-label="Filter records">
<div><labelfor="f-kind">Kind of item</label>
<selectid="f-kind"name="kind"><optionvalue="">Any</option><option>Ordinance</option><option>Resolution</option><option>Agreement</option></select></div>
<div><labelfor="f-from">From</label><inputid="f-from"type="date"name="from"></div>
<div><labelfor="f-q">Words in the title or the report</label><smallid="f-q-hint">Every word must appear.</small><inputid="f-q"type="search"name="q"aria-describedby="f-q-hint"></div>
<divdata-actions><buttontype="submit">Show records</button><buttontype="reset">Reset</button></div>
</form>
The fields wrap across the card as room runs out. A control is the last thing in its field, so the controls in a row stay on one line whatever is written above them. A row of buttons takes a line of its own.
<formdata-layout="stack"action="#forms"novalidate>
<asidedata-severity="critical"tabindex="-1">
<p>There is a problem</p>
<ul>
<li><ahref="#e-email">Enter an email address, like name@example.com</a></li>
<li><ahref="#e-reply-email">Choose how to be replied to</a></li>
</ul>
</aside>
<div><labelfor="e-email">Email</label>
<smallid="e-email-error"data-severity="critical"><spanclass="visually-hidden">Error: </span>Enter an email address, like name@example.com</small>
<inputid="e-email"type="email"name="email"value="name.example.com"autocomplete="email"requiredaria-invalid="true"aria-describedby="e-email-error"></div>
<fieldsetaria-describedby="e-reply-error">
<legend>Reply by</legend>
<smallid="e-reply-error"data-severity="critical"><spanclass="visually-hidden">Error: </span>Choose how to be replied to</small>
<label><inputid="e-reply-email"type="radio"name="e-reply"value="email"required> Email</label>
<label><inputtype="radio"name="e-reply"value="phone"required> Phone</label>
</fieldset>
<divdata-actions><buttontype="submit">Send</button></div>
</form>
An error is written between its label and its control, and the control names it in aria-describedby. The control, a group's fieldset and the message repeat it in --fp-critical, and :user-invalid draws the same border once someone has typed. The summary at the top links to each field. When the page comes back with errors, move focus to the summary, which is what its tabindex="-1" is for. Here a short script does that when you press Send, clears an error once its field is fixed, and moves focus to a field from its summary link.
A pager
Markup: A pagernav ul[data-list="chips"] [aria-current]
A pager is a chip list in a nav. The page in view is marked in weight and ink rather than color, and a chip in a nav is at least 44px wide, so a single digit is a full target. Here the chips move aria-current when you choose one, and the markup follows.
Menus, dialogs and states
What opens over the page, and what shows work in progress. Each is an element or attribute HTML already has, and none needs a script from the framework.
A menu is a disclosure whose panel floats over what follows. data-align="end" hangs the panel from the right edge, for a menu at the end of a row. Tab moves through the links and the summary closes it. A press outside does not, which would take script.
A dialog
Markup: A dialogdialog
<divdata-actions>
<buttontype="button"commandfor="ref-dialog"command="show-modal">Remove the filter</button>
</div>
<dialogid="ref-dialog"aria-labelledby="ref-dialog-title">
<h2id="ref-dialog-title">Remove this filter?</h2>
<p>The list goes back to every record. The words you searched for stay in the box.</p>
<formmethod="dialog">
<divdata-actions><buttonvalue="remove">Remove</button><buttonvalue="keep">Keep it</button></div>
</form>
</dialog>
Opened modal, a dialog sits in the top layer and the page behind it is inert. The form with method="dialog" closes it with no script, and the value of the button pressed becomes the dialog's returnValue. As in any row of actions, the first button is the primary. command and commandfor open it with no script where the browser supports them, and this page calls showModal() where it does not.
A note on a word
A release is once it is published.Served with a year-long cache and never revised, so every visitor gets the same bytes.
Markup: A note on a word[popover]
<p>A release is <buttontype="button"popovertarget="ref-note">immutable</button> once it is published.<spanid="ref-note"popover>Served with a year-long cache and never revised, so every visitor gets the same bytes.</span></p>
A popover opens on a press and closes on Escape or a press anywhere else, with no script. It sits under its button where the browser can anchor it, and in the middle of the screen where it cannot. A button that opens one from inside a sentence is drawn as a word with a dotted underline.
Busy
Ordinances
48 this year
Resolutions
112 this year
Loading the counts
Markup: Busy[aria-busy="true"]
<divdata-layout="split"aria-busy="true">
<div><h3>Ordinances</h3><p>48 this year</p></div>
<div><h3>Resolutions</h3><p>112 this year</p></div>
</div>
<prole="status">Loading the counts</p>
<divdata-actions><buttontype="button"aria-busy="true">Saving</button></div>
On a button, a spinner before the label, and the button takes no second press. On anything else, a spinner floats at its top until the update lands. A screen reader is told nothing by aria-busy alone, so the page says so in a role="status" line as well.
Progress and meters
40% of 2.1 MB
No count yet
96 of 100: good
72 of 100: needs work
31 of 100: poor
Markup: Progress and metersprogress, meter
<divdata-layout="grid">
<div>
<labelfor="ref-upload">Uploading report.pdf</label>
<progressid="ref-upload"max="100"value="40"></progress>
<small>40% of 2.1 MB</small>
</div>
<div>
<labelfor="ref-links">Checking links</label>
<progressid="ref-links"></progress>
<small>No count yet</small>
</div>
<div>
<labelfor="ref-good">Pages with alt text</label>
<meterid="ref-good"min="0"max="100"low="50"high="90"optimum="100"value="96"></meter>
<small>96 of 100: good</small>
</div>
<div>
<labelfor="ref-fair">Pages with headings in order</label>
<meterid="ref-fair"min="0"max="100"low="50"high="90"optimum="100"value="72"></meter>
<small>72 of 100: needs work</small>
</div>
<div>
<labelfor="ref-poor">Pages with captions</label>
<meterid="ref-poor"min="0"max="100"low="50"high="90"optimum="100"value="31"></meter>
<small>31 of 100: poor</small>
</div>
</div>
A progress bar is a task; with no value it is indeterminate and a band slides along the track. A meter is a measurement, and its low, high and optimum color the bar in the accent, bronze or critical. Neither writes its value, so the page does, in words that say whether a reading is good.
Tokens and schemes
Every color, size and face is a custom property. A site on another brand sets the tokens and keeps every component.
The tokens a site sets
Token
Group
Light
Dark
--fp-bg
light
#ffffff
#10141c
--fp-ink
light
#141821
#edf0f6
--fp-accent
light
#006060
#4dd2d2
--fp-board
board
#10141c
#10141c
--fp-amber
fill
#ffb300
#ffb300
--fp-sans
type
"Overpass", …
"Overpass", …
Set a group wholly or leave it alone. The rest of each group is tuned against these, and the contract test measures every pairing between them; set half a group and the pairings stop holding. tokens.json lists each group's members and the pairings that have to hold.
Light and dark
The page follows the reader's system setting. data-theme on the html element pins one scheme.
html
<htmllang="en"data-theme="dark">
theme-1.0.0.js runs the header button that switches schemes. Its two labels name the scheme each one switches to, and the sheet shows one at a time.
A page prints in the light scheme whatever it is pinned to, and its dark bands print on the page's ground, because a browser prints without background graphics unless asked. A link in running text prints its address, every disclosure prints open, and the scheme toggle is left off.
Adopting the framework with an AI assistant
Paste this at the start of a project and fill in its last part with the project's details.
The prompt suits any project whose output is HTML: a website, a web application, a CMS theme or an internal tool. It points the assistant at the public reference files, states the rules the framework depends on, and asks for a structural check before the assistant hands back its work. Its links to the sheet and the tokens name release 3.7.1, the current one.
Prompt
This project uses the FivePaths microsite framework, release 3.7.1, for the HTML it produces. That HTML may be written by hand, rendered by templates or a CMS, or built by a component framework; the framework styles it the same way in each case. Before you write any markup, templates or components, read these four files, in this order:
1. https://cdn.fivepaths.com/microsite/v3/
The component reference. Every pattern the framework styles is shown there with its exact markup. Treat it as the complete list of what you may use.
2. https://cdn.fivepaths.com/microsite/v3/base-3.7.1.css
Read the comment at the top of the file. It summarizes which element goes where and names the classes that exist.
3. https://cdn.fivepaths.com/microsite/v3/tokens-3.7.1.json
The design tokens, the surface groups they are overridden in, and the color pairings that must keep 7:1 contrast.
4. https://cdn.fivepaths.com/microsite/v3/DESIGN.md
A summary of the three files above in the DESIGN.md format: the tokens as YAML, then the rules for color, type, layout and each component. It follows the newest 3.x release, so where it differs from the files above, they win.
How the framework works
- It styles HTML elements by what they are and where they sit. A section is a band, a ul is a list, a ul with data-list="cards" is a card grid, and data attributes choose between variants.
- The nesting carries the styling. Selectors such as main > section > header > h2 + p match only when the elements are direct children in that order. An extra wrapper element, a reordered heading or a missing header turns the styling off with no error.
- Only five classes exist: ghost, ink and teal on an action link, tld inside the wordmark, and visually-hidden. Do not add classes to the framework's components.
- Colors, type and spacing are --fp-* custom properties. Never hardcode a color.
Rules for this project
1. Load the pinned release exactly as the "Set up a page" section of the reference shows: the framework's stylesheet, then the project's own stylesheet, then theme-1.0.0.js. The reference calls the project's stylesheet site.css; use whatever name and location suit the project.
2. Build every page, screen or view on the body skeleton in that section: the skip link, a header with the brand link and nav, main with its sections, and a footer. Leave out the parts the project has no use for, and keep the order and nesting of the parts that remain.
3. Use only patterns shown on the reference page, and copy their structure exactly, including which elements are direct children of which. If something the project needs fits no pattern, stop and ask me rather than inventing markup.
4. Where templates, components or a CMS produce the markup, these rules apply to the HTML that reaches the browser. Make sure no wrapper the tooling adds lands between elements the reference nests directly, and check the rendered output rather than the source.
5. Put a section's content directly inside the section. Give an element that needs more room data-width="wide" or data-width="full"; never wrap it.
6. Rebrand by overriding tokens in the project's stylesheet, one whole surface group at a time as tokens.json defines them. Never set part of a group. After a color change, go through every pairing tokens.json lists and confirm it still clears 7:1 in the light scheme, the dark scheme and the dark bands.
7. Anything the framework does not cover goes in the project's stylesheet, under names prefixed for this project, written in --fp-* tokens, with tints made by color-mix() against a token. Do not restyle the framework's own components there.
8. Style forms only through form data-layout="stack" or data-layout="filters", and show errors with the pattern in the reference's Forms section, including the summary at the top of the form.
9. Keep the AAA floor: headings in order, alt text on every image, a label on every field, a 44px target on every control, nothing carried by color alone, and no sideways scrolling at 320px wide.
10. Never edit or copy base.css. To move to a newer release, change the version where it is loaded and recheck the output.
Before you hand back work
- Compare each section or component with the reference example it is built from and confirm the rendered nesting matches.
- List any markup that is not on the reference page, and say why it was needed.
- List the rules you added to the project's stylesheet and what each one is for.
- Say what you could not check yourself, such as contrast after a token change or how a view looks in the dark scheme.
About this project
[What the project is (a website, a web application, a CMS theme, an internal tool) and who uses it. The pages, screens or views it needs. How its HTML is produced: by hand, a static site generator, a CMS such as Drupal or WordPress, or a component framework. The brand colors and typeface, if it is not FivePaths-branded. Where the code lives and how it is built and deployed.]
The full contract
MARKUP.md in the fivepaths-cdn repository covers every element, tokens.json holds the token contract in a form a build tool can read, and DESIGN.md summarizes both for an agent generating pages.