Style guide / Components

Component reference

Live components and implementation rules for the cartridge visual system.

Use this reference to copy markup, compare component states and find the implementation source. The design guide explains visual decisions; the editorial guide owns voice and naming. Reuse a shared partial where one exists, and give copied controls page-unique IDs and radio names.

Colors

Paper
#faf9f5
Near-white reading ground
Ink
#151515
Body text and structure
Cobalt
#173ebc
Links, navigation and strong fields
Yellow
#f6d92f
Cover geometry and highlights
Vermilion
#ee3e35
Large decorative accents
Green
#007c55
Closing footer field

Use --kh-cart-paper, --kh-cart-ink, --kh-cart-blue, --kh-cart-yellow, --kh-cart-red and --kh-cart-green. The swatches above consume the live tokens. Yellow and red are large decorative accents. Use white/cobalt, white/green, ink/paper and cobalt/paper for text. Muted text uses --kh-ink-muted (#5b5e5a).

The design guide palette records contrast and colour roles. Existing aliases keep earlier components in step: --kh-ground maps to paper; --kh-color--blue and --kh-color--apparatus map to cobalt; rules use neutral ink. --kh-panel-bg is white, #ffffff, to lift grouped content from the paper ground. Visited reading links retain --kh-color--visited (#563d82).

Typography

Make it make sense.

The homepage cover is trying Science Gothic; Anton 400 remains the display voice elsewhere. IBM Plex Sans 400/600 handles reading and interfaces; League Mono 400 at normal width handles code and metadata. Copy stays sentence case; display uppercase is CSS. The design guide describes the hierarchy and font assets lists loaded faces.

Page-title typography is selected by the page family, not by adding a heavier font weight. Standard titles grow to 4.5rem; utility, note and photo titles are smaller. Long-form reading uses 18px and about 62ch, reducing to 17px on small screens.

Heading classes and document outline

.kh-text-heading--1, --2 and --3 are retained type utilities. They do not change a heading's semantic level. Use one page h1, then choose heading levels for the document outline. These examples use h3 because they sit under this reference's Typography section; they demonstrate utility classes, not additional page titles.


<h3 class="kh-text-heading--1">A large utility heading</h3>
<h3 class="kh-text-heading--2">A section-scale utility heading</h3>
<h3 class="kh-text-heading--3">A smaller utility heading</h3>

A large utility heading

A section-scale utility heading

A smaller utility heading

Content headings


<div class="kh-content">
  <h3>A heading inside reading content</h3>
  <p>Plain heading tags inherit the content rules. Keep paragraphs in the reading face.</p>
  <h4>A subordinate heading</h4>
  <p>The tag describes structure, independently of its visual size.</p>
</div>

A heading inside reading content

Plain heading tags inherit the content rules. Keep paragraphs in the reading face.

A subordinate heading

The tag describes structure, independently of its visual size.

Body and inline text


<p class="kh-text-body--1">Lead text with an intentional place in the hierarchy.</p>
<p>Ordinary reading text, with <strong>real semibold</strong>, <em>real italic</em>, <code>inline code</code> and <a href="/blog/">a descriptive link</a>.</p>
<p class="kh-text-body--3">Supporting text using the retained body utility.</p>
<p class="kh-meta">24 Oct 2026 / supporting metadata in League Mono</p>

Lead text with an intentional place in the hierarchy.

Ordinary reading text, with real semibold, real italic, inline code and a descriptive link.

Supporting text using the retained body utility.

24 Oct 2026 / supporting metadata in League Mono

Display utility


<h3 class="kh-font-headline kh-font-headline--display">A retained display-heading utility</h3>

A retained display-heading utility

The retained display utility and the current Anton page-family titles have separate selectors. Use the page layout for a page title; inspect the actual class combination before promising a fixed size.

Intro pair


<div class="kh-content">
  <h3 class="kh-intro__heading">A page introduction</h3>
  <p class="kh-intro__text">The lead adds scope or context instead of repeating the title.</p>
</div>

A page introduction

The lead adds scope or context instead of repeating the title.

Sources: _kh-content.scss, typography utilities in index.scss, and the page-family overrides in _kh-cartridge-system.scss, all under src/components/vf-componenet-rollup/. Test long titles and 200% text sizing; fixed widths and nowrap must not clip meaningful text.

Shared structure

The datasheet class names remain stable. Their current presentation uses cobalt rules, open lists and restrained panels. Decorative section numbers are retired from indexes; stable project references and ordered instructions still carry meaningful numbers.


<div class="kh-section-head">
  <h3>Recent writing</h3>
  <span class="kh-meta">Newest first</span>
</div>

Recent writing

Newest first

Panels


<div class="kh-panel">
  <div class="kh-panel__row">
    <div class="kh-panel__cell"><span class="kh-panel__label">Place</span>Bonn, Germany</div>
    <div class="kh-panel__cell"><span class="kh-panel__label">Practice</span>Platforms, content and audiences</div>
  </div>
  <div class="kh-panel__row">
    <div class="kh-panel__cell"><span class="kh-panel__label">Purpose</span>Group related facts with a shared boundary.</div>
  </div>
</div>
PlaceBonn, Germany
PracticePlatforms, content and audiences
PurposeGroup related facts with a shared boundary.
  • .kh-section-head aligns a heading and supporting metadata; it can wrap.
  • .kh-panel groups related rows on white with a 2px ink frame and a 4px cobalt offset shadow. Internal rules stay light so the values remain easy to scan. .kh-panel__row and .kh-panel__cell supply the structure; .kh-panel__label names a value in uppercase cobalt mono. Direct navigation links use Sans 600. Keep the cells upright and preserve wrapping at narrow widths.
  • Use tables when comparison requires column headings. A panel is not a substitute for table semantics.
  • Navigation, entry footers and bylines are repeated chrome. Put data-pagefind-ignore on the wrapper so their content does not leak into Pagefind or embeddings.

Sources: _kh-datasheet.scss for the stable primitives; _kh-cartridge-system.scss for current surfaces and rules. Do not add an empty left column merely to indent an introduction.

Labels and micro-copy

Use the interface vocabulary for destination names and deliberate context-specific labels. Keep labels in sentence case; descriptions should add information rather than repeat the heading.

.kh-cartridge-kicker, .kh-meta and .kh-panel__label are supporting labels. They must remain readable without hover. Put an explanation next to a data mark when its meaning would otherwise depend on a tooltip. Preserve proper names and acronyms; do not author all-caps text just because its display style is uppercase.

Buttons and links


<div class="kh-cluster"><a class="kh-button" href="/work/">Explore the work</a>
  <button class="kh-button" type="button">Example action</button>
  <button class="kh-button" type="button" disabled>Unavailable action</button>
</div>
<p><a href="/all/">Ordinary navigation stays a link ↗</a></p>
Explore the work

Ordinary navigation stays a link ↗

Buttons use Plex Sans 600, white on cobalt, square corners and at least 44px height. Hover/focus uses ink; keyboard focus has an ink outline and white inner ring. Resize or use a keyboard to inspect the live controls. The example action has no side effect; the disabled example uses the native disabled state.

Contract Use
.kh-button on an a with href Navigation to a real destination
.kh-button on button type="button" An action implemented by its owner
button type="submit" Submits the surrounding form
disabled A native unavailable action; supply surrounding explanation when needed
aria-label Required when an icon or hidden text would otherwise leave the control unnamed

The retained --primary and --sm class names appear in older content. The cartridge rule defines the common button presentation; do not assume those names provide a new hierarchy or smaller target. The old button-colour custom properties are overridden by the cartridge styling. Add a scoped, documented component modifier when a new variant is actually needed.

Sources: index.scss and _kh-cartridge-system.scss. Search-specific label/icon spans are documented under search forms.

Badges and labels


<p><span class="kh-label">Design systems</span><span class="kh-label">CSS</span></p>
<p class="kh-meta">IS-03 / supporting metadata, not a second headline</p>

Design systemsCSS

IS-03 / supporting metadata, not a second headline

Topics are labels; dates and reference IDs are metadata. Entry-type labels retain real names such as “Digesting” and “Impact story”. A label is a span unless it actually links somewhere; do not style static text as an unexplained control. Sources: index.scss, _kh-datasheet.scss and _kh-cartridge-system.scss.

Entry lists and selected-work cards

Prefer partials/post-summary.njk inside .kh-datasheet-list to reproducing its branching logic. It derives digest, note, photograph and impact-story states from tags, and supplies date/body/media wrappers. The current layouts align those cells on desktop and reflow on mobile. Keep an imageless media cell empty; do not add placeholder text that defeats :empty selectors.

Standard entry structure


<div class="kh-datasheet-list">
  <article class="kh-summary kh-summary--news">
    <div class="kh-summary__meta">
      <div class="kh-summary__date">16 Nov 2026</div>
    </div>
    <div class="kh-summary__body">
      <h3 class="kh-summary__title"><a class="kh-summary__link" href="/blog/">An entry with a clear title</a></h3>
      <p class="kh-summary__text">A concise description that adds information.</p>
    </div>
    <div class="kh-summary__media"></div>
  </article>
</div>

Digesting variant


<div class="kh-datasheet-list">
  <article class="kh-summary kh-summary--news kh-summary--highlight">
    <div class="kh-summary__meta">
      <div class="kh-summary__date">16 Nov 2026</div>
      <a class="kh-summary__tab" href="/digesting/">Digesting</a>
    </div>
    <div class="kh-summary__body">
      <h3 class="kh-summary__title"><a class="kh-summary__link" href="/digesting/">A short curatorial observation</a></h3>
      <p class="kh-summary__text">Digesting and note entries omit the media thumbnail in the shared partial.</p>
    </div>
    <div class="kh-summary__media"></div>
  </article>
</div>

Media and selected-work variants


<div class="kh-datasheet-list">
  <article class="kh-summary kh-summary--news">
    <div class="kh-summary__meta">
      <div class="kh-summary__date">16 Nov 2026</div>
    </div>
    <div class="kh-summary__body">
      <h3 class="kh-summary__title"><a class="kh-summary__link" href="/style-guide/design/">An image-bearing entry example</a></h3>
      <p class="kh-summary__text">A local vector stands in for a project image in this example.</p>
    </div>
    <div class="kh-summary__media"><a class="kh-summary__image" href="/style-guide/design/">
      <img class="kh-summary__image" src="/images/cartridge-pattern.svg" width="300" height="92" alt="Geometric cover marks" eleventy:ignore loading="lazy">
      </a>
    </div>
  </article>
</div>

For an image-bearing entry, the partial adds a linked image inside .kh-summary__media; the image transform may insert picture. Never position only the nested img when the wrapper is the grid child. The homepage reverses its list inside .kh-cartridge-writing: white text, yellow dates and a cobalt field.

The work page uses .kh-work-cards and .kh-work-card. Its explicit selected_work list supplies the URL, leadership angle, summary and optional qualified proof/context. The title and optional image come from the matching published story. Selection represents platform, editorial and standards leadership; the full chronological record remains below.


<div class="kh-work-cards">
  <article class="kh-work-card"><a href="/work/">
    <div class="kh-work-card__proof"><strong>15 sites</strong><span>Example scope, not an unqualified outcome</span></div>
    <div class="kh-work-card__body">
      <p class="kh-cartridge-kicker">Platform leadership</p>
      <h3>An inspectable work example ↗</h3>
      <p>Use a real project image or a scoped proof statement. Keep the baseline and measurement period close to any percentage.</p>
    </div>
    </a>
  </article>
</div>

Sources: partials/post-summary.njk, src/site/work.njk, _kh-datasheet.scss, _kh-cartridge.scss and _kh-cartridge-system.scss.

Note boxes


<aside class="kh-note-box"><span class="kh-note-box__label">Update</span>A short correction that changes how the surrounding text should be read.</aside>

<aside class="kh-note-box"><span class="kh-note-box__label">Context</span>
  <p>A note may contain more than one block when the structure helps.</p>
  <ul>
    <li>A scoped qualification.</li>
    <li>A link to the <a href="/style-guide/editorial/">editorial guidance</a>.</li>
  </ul>
</aside>

Use aside for contextual content, a concise summary or a correction; keep ordinary paragraphs outside boxes. Use a short label such as “Update” or “Context”. The upright yellow label sits on its own line above the body, with a cobalt left rule and a quiet reading surface. Plain text and structured paragraphs both work; longer notes may include lists. Sources: index.scss and _kh-cartridge-system.scss; editorial guidance: note boxes.

Margin notes and pull-quotes

Author using paired shortcodes inside a Markdown block. They render inline Markdown, so links, emphasis, code and -- punctuation work. Keep each aside to one or two sentences, with no blank paragraphs inside the shortcode.

{% marginnote %}Supporting detail with a [source](/colophon/).{% endmarginnote %}
{% pullquote %}Keep the evidence near the claim.{% endpullquote %}

A margin note is additional content: it stays in the accessibility tree and search. A pull-quote repeats a phrase from the body: the shortcode adds aria-hidden="true" and data-pagefind-ignore. Unique information must never exist only in a pull-quote.

At 1300px and above, article notes float into the right margin and the reading measure adjusts. Below that and in print they return to the flow. The reference previews below deliberately show the in-flow form; inspect an article with notes to verify the wide-margin behaviour.


<div class="kh-reference-asides">
  <aside class="kh-marginnote">Supporting context, including a <a href="/colophon/">source link</a>.</aside>
  <p>The main argument remains readable on its own.</p>
</div>

The main argument remains readable on its own.


<div class="kh-reference-asides">
  <p>Keep the evidence near the claim.</p>
  <aside class="kh-pullquote" aria-hidden="true" data-pagefind-ignore>Keep the evidence near the claim.</aside>
</div>

Keep the evidence near the claim.

Sources: shortcode registration in config/eleventy/markdown.js; layout, float arithmetic and print rules in _kh-content.scss. Prefer the shortcodes to hand-written markup so the accessibility/search markers remain intact.

Content boxes


<div class="kh-box">
  <h3 class="kh-box__heading">A related resource</h3>
  <p class="kh-box__text">A compact grouping of content with a reason to sit together.</p>
  <a href="/garage/">Explore the garage</a>
</div>

A related resource

A compact grouping of content with a reason to sit together.

Explore the garage

Content boxes group a related resource with .kh-box__heading, .kh-box__text and a real link. The box reads its documented theme properties; see component overrides. Source: index.scss.

Collapsible details


<details class="kh-details">
  <summary>
    <h3>Implementation detail</h3>
  </summary>
  <p>The native disclosure works without JavaScript. The summary remains the control.</p>
</details>

Implementation detail

The native disclosure works without JavaScript. The summary remains the control.

Open by default


<details class="kh-details" open>
  <summary>Expanded context</summary>
  <p>Use <code>open</code> when the content should initially be visible.</p>
</details>
Expanded context

Use open when the content should initially be visible.

Use details for secondary material, not to hide the opening argument, a required action or the only explanation of a data point. A summary can contain an appropriate heading; match the page outline. Do not insert a second interactive control inside the summary.

.kh-details is the native content disclosure: a cobalt summary, yellow direction marker, ink frame and cobalt offset shadow. Opening it reveals a white reading area; the marker rotates down and the summary keeps a visible keyboard focus ring. Plain, unclassed details inside .kh-content receive the same treatment. Summary headings retain their semantic level while inheriting the compact Anton display style. .kh-cartridge-contents is the separate article-contents treatment, assembled by layouts/post.njk; its native summary owns the contents navigation. The contents use an ink header, yellow section-count and number accents, and an aligned responsive grid. Each link has a fixed number column and a flexible title column; titles wrap without shifting neighbouring columns. Fill columns from top to bottom, then continue into the next column. Source and keyboard order stay sequential; the entry count supplies the two- and three-column row counts through inline custom properties. Container queries reduce the grid to two columns and then one as space narrows. Preserve the native keyboard disclosure. Do not replace either with a clickable div. Source: index.scss, _kh-cartridge.scss and src/site/_includes/layouts/post.njk.

Blockquotes

Standard quotation


<blockquote>
  <p>A quotation supplies evidence or an outside voice.</p>
  <cite>Demonstration text, not an attributed quotation.</cite>
</blockquote>

A quotation supplies evidence or an outside voice.

Demonstration text, not an attributed quotation.

<blockquote class="kh-quote kh-quote--featured">
  <p>I connect strategy, technical delivery and audience needs.</p>
</blockquote>

Keep quotation text accurate and provide attribution when quoting another person. The featured class remains available for a short, intentional statement; it is not a default decoration for every section. Standard quotations use a white ink-framed field, cobalt edge and a pair of yellow slanted marks in the margin. Featured statements invert to white on cobalt with a yellow edge. Text remains upright; long paragraphs and citations wrap normally. The marks are decorative CSS, not extra quotation text. Source: _kh-cartridge-system.scss, over the retained primitives in _kh-content.scss and index.scss.

Code and live demos

Use fenced Markdown with a language identifier. Code blocks sit on the paper ground with a solid ink sawtooth edge and a sparse strip of complete geometric marks above the code. The triangle, squiggle, outline square and dotted bar have their own reserved margin; they are not a pattern hidden beneath a white box. The original SVGs (cartridge-code-edge.svg and cartridge-code-marks.svg) carry the decoration without adding selectable text. Inline code stays plain. Inline code can wrap when needed; long blocks contain their own overflow. Source text must not force the entire page sideways. Paired code/demo examples share one decorated outer edge rather than repeating it on both panes.

.example {
  color: var(--kh-cart-ink);
}

When code should stay plain

Use the decorative edge for authored code excerpts. Code that forms part of a diagram, interactive demo, editor or utility owns its own presentation. A kh- class on a pre excludes it from the decorative treatment automatically; use .kh-code--decorated to opt a classed snippet back in deliberately.

For a quiet prose snippet, use .kh-code--plain. It keeps the ordinary code formatting and scrolling without the sawtooth edge or margin marks:

<pre class="kh-code--plain"><code>const width = 100;</code></pre>

For a paired Source/Result wrapper, use .kh-demo.kh-demo--plain. The source pane stays plain too. Keep the wrapper’s labels, borders and data-pagefind-ignore contract. The Mangrove story’s .kh-sv-demo__code is component-owned: its exact spacing is part of the explanatory graphic.

The paired codeAndDemo shortcode

Place it outside a Markdown block. Its body becomes both escaped source and live HTML:

{% codeAndDemo 'html' %}
<p>A small example with <code>inline code</code>.</p>
{% endcodeAndDemo %}

<p>A small example with <code>inline code</code>.</p>

A small example with inline code.

The shortcode adds .kh-demo with data-pagefind-ignore, a pre/code pane, and .kh-demo__live. Samples therefore stay out of the site's keyword and semantic indexes. Live markup still needs unique IDs, correct headings and harmless actions. Prefer local placeholders to loading third-party embeds. Never submit sample feedback to the live service.

Sources: config/eleventy/markdown.js and .kh-demo in _kh-content.scss. To show Nunjucks tags rather than execute them, wrap the example in a Nunjucks raw block.

Figures and images

Put source files in src/site/images/blog/; entry frontmatter uses /blog/filename.ext. The hero image and the social card are separate mechanisms. Provide descriptive alt text, a useful caption and the correct credit. Ken’s photos use credit: "Own work." with location context in the caption.

Article layouts put the teaser before the hero image so readers reach the introduction sooner on small screens. Keep the teaser at the reading measure and do not repeat it below the image.

Captions use .kh-figure__caption: smaller upright text, a fine rule and a small cobalt/yellow corner mark distinguish them from the article. Use the same caption for ordinary images, comparisons, cover galleries and collages. Bare image captions inside prose receive the same treatment; the older .kh-collage__caption remains a compatibility alias. Keep captions and source links readable rather than setting the whole block in italics.

The image transform can produce a <picture> wrapper. In grids and flex layouts, target that direct child as well as the image. Use the original colours of photographs, diagrams and project screenshots. A wide image may break the reading measure, but it must not break the viewport.

For portrait-cover comparisons, add kh-cover-gallery to a kh-grid kh-grid__col-3 container of figures. Its 7:10 image frames use object-fit: contain to preserve the complete covers and align the captions. It supports generated picture wrappers and stacks through the existing grid breakpoints. The Sonic reference gallery shows it in use.

The homepage before/after reuses kh-compare inside a figure.kh-bleed-out. Match the screenshot dimensions, keep descriptive alt text and links to both originals, and connect the native range to its caption. The control updates --kh-compare-split and its spoken value; without JavaScript the images remain at a static split, and without CSS they stack. On small screens the figure uses the full reading width.

The live feedback counter is a remote image and must retain eleventy:ignore. A raster still pointing to /images/ in production, or a /.11ty/image/ URL in production HTML, is a failed transform; the build checks catch both cases.


<figure>
  <img src="/images/cartridge-pattern.svg" alt="Sparse blue, yellow, green, red and black geometric marks: zigzag, paired strokes, outlined square, wavy line, dotted rule, circle and triangle." width="520" height="160" loading="lazy" eleventy:ignore>
  <figcaption class="kh-figure__caption">Current cover-margin pattern, drawn for this site. The serrated boundaries use the separate <code>cartridge-edge.svg</code> mask.</figcaption>
</figure>
Sparse blue, yellow, green, red and black geometric marks: zigzag, paired strokes, outlined square, wavy line, dotted rule, circle and triangle.
Current cover-margin pattern, drawn for this site. The serrated boundaries use the separate cartridge-edge.svg mask.

Cut-paper collage

Use .kh-collage for an occasional editorial image, with a complete central view and an upright caption. The TG-16 reference supplies unequal cuts, a black anchor and a small colour overlap. Keep data diagrams, comparison figures and ordinary screenshots plain when the decoration would compete with their purpose.

Section, profile and utility page H1s share the cut-paper masthead: Science Gothic on a level baseline, an angular yellow underlay and a cobalt corner shard. Work, About and All writing use the display scale; Search uses the compact scale so controls stay near the top. .kh-shard-heading applies the same treatment to another short heading; --section gives the homepage contact heading its intermediate scale, and --compact supplies the utility scale. Article covers and reading subheadings keep their own hierarchy. The shapes disappear with CSS off and in print.

For Nunjucks posts, import the shared macro before the Markdown block, then call it at the intended visual pause:

{% from "partials/collage.njk" import collageFigure %}
{{ collageFigure('/images/blog/mangrove-figma-library-overview.png',
  'Overview of the Mangrove Figma component library.',
  'The library overview, with details around it.', 'Own work.', 'yellow',
  '/images/blog/mangrove-figma-card-presets-and-brand-tags.png') }}

Arguments are the image URL, meaningful alt text, plain-text caption, credit, optional tone (yellow or red), optional detail-image URL, and optional parallax boolean (default false). Pass true as the seventh argument to load the tiny shared module and enable .kh-collage--parallax. Omit the detail URL to crop decorative copies of the main image. Use /images/blog/… here: these are in-page URLs, not frontmatter paths. Caption and credit are escaped, so add related links beside the figure rather than passing HTML.

The macro emits .kh-collage__stage, three .kh-collage__fragment elements and .kh-collage__main, followed by the caption. Decorative fragments have empty alt text, aria-hidden, data-pagefind-ignore and hidden; scoped CSS reveals them only in styled viewing. They disappear in CSS-off and print views. The complete image is never clipped; its caption stays upright. The image transform’s <picture> wrapper is supported. The optional parallax uses pointer position and CSS transforms, with no image rendering or framework at interaction time. It batches updates with requestAnimationFrame, resets on pointer exit, and stays static for touch/coarse pointers and reduced-motion preferences. The caption and hit areas never move.

For hand-authored HTML, the basic figure also works without extra image fragments:


<figure class="kh-collage">
  <div class="kh-collage__stage">
    <div class="kh-collage__main"><img src="/images/blog/mangrove-figma-library-overview.png" alt="Overview of the Mangrove Figma component library." width="800" loading="lazy"></div>
  </div>
  <figcaption class="kh-figure__caption">Mangrove library overview. <span class="kh-collage__credit">Own work.</span></figcaption>
</figure>
Overview of the Mangrove Figma component library.
Mangrove library overview. Own work.

Examples: design overhaul post, Johnny Castaway and the component gallery. Source: partials/collage.njk, _kh-collage.scss.

Prose figures, page figures and wide media

Use a plain figure inside .kh-content. .kh-figure is the page-level figure grid; content rules deliberately neutralise that grid when it is nested inside prose. The live example above is a prose figure. A page-level layout can use:

<figure class="kh-figure">
  <img class="kh-figure__image" src="/images/cartridge-pattern.svg" width="520" height="160" alt="Describe the meaningful image.">
  <figcaption class="kh-figure__caption">Caption and credit.</figcaption>
</figure>

For a deliberate reading-column escape, use figure class="kh-bleed-out" and inspect it in the actual article layout. Its left bleed begins at 767px and assumes available space beside the reading column; a general documentation panel is not that context. Preserve captions and alternative text at every width.

The transform may replace img with picture. Grid areas and overlap layouts must target the direct picture wrapper as well as an untransformed image. Sources: _kh-content.scss, index.scss, and the image pipeline notes.

Tables

.kh-table--spec supplies column boundaries and current cobalt headers. Use real table, thead, tbody, th and td elements when readers compare records. Give headers scope="col" or scope="row"; use a caption when the surrounding heading does not name the table.


<div class="kh-table-scroll">
  <table class="kh-table--spec">
    <caption>Example project record</caption>
    <thead>
      <tr>
        <th scope="col">Project</th>
        <th scope="col">Year</th>
        <th scope="col">Organization</th>
      </tr>
    </thead>
    <tbody>
      <tr>
        <th scope="row">Shared design system</th>
        <td>2026</td>
        <td>UNDRR</td>
      </tr>
      <tr>
        <th scope="row">Visual Framework</th>
        <td>2019</td>
        <td>EMBL</td>
      </tr>
    </tbody>
  </table>
</div>
Example project record
Project Year Organization
Shared design system 2026 UNDRR
Visual Framework 2019 EMBL

Stacking versus scrolling


<div class="kh-table-scroll">
  <table class="kh-table--spec kh-table--stack">
    <caption>Example compact record</caption>
    <thead>
      <tr>
        <th scope="col">Project</th>
        <th scope="col">Year</th>
        <th scope="col">Organization</th>
      </tr>
    </thead>
    <tbody>
      <tr>
        <td><a href="/work/">Platform recovery</a></td>
        <td data-label="Year">2025</td>
        <td data-label="Organization">UNDRR</td>
      </tr>
    </tbody>
  </table>
</div>
Example compact record
Project Year Organization
Platform recovery 2025 UNDRR
  • .kh-table-scroll contains a genuinely wide table instead of making the page scroll.
  • .kh-table--stack opts a suitable record table into cards below 846px. Add data-label to cells that need a header in this view; titles and reference IDs need not repeat obvious labels.
  • Keep the full table when relationships depend on comparing columns. Do not stack a data matrix merely to avoid horizontal scrolling.

Sources: _kh-datasheet.scss, _kh-cartridge-system.scss; a production example is src/site/work.njk.

Forms


<form action="/search/" method="get">
  <label class="kh-form__label" for="guide-search">Search the site</label>
  <input class="kh-form__input" id="guide-search" name="search_query" type="search" placeholder="Try design systems">
  <button class="kh-button" type="submit">Search</button>
</form>

<label class="kh-form__label" for="guide-context">Supporting context</label>
<textarea class="kh-form__textarea" id="guide-context" rows="3" aria-describedby="guide-context-help"></textarea>
<p id="guide-context-help" class="kh-meta">A local control preview; this text is not submitted.</p>
<label class="kh-form__label" for="guide-disabled">Unavailable field</label>
<input class="kh-form__input" id="guide-disabled" value="Read-only demonstration" disabled>

A local control preview; this text is not submitted.


<label class="kh-form__label" for="guide-select">Example topic</label>
<select class="kh-form__select" id="guide-select">
  <option>Platforms</option>
  <option>Editorial operations</option>
  <option>Shared standards</option>
</select>
<label class="kh-form__label" for="guide-invalid">Email validation example</label>
<input class="kh-form__input" id="guide-invalid" type="email" value="incomplete-address" aria-invalid="true" aria-describedby="guide-invalid-help">
<p id="guide-invalid-help">Example error: enter a complete email address.</p>

Example error: enter a complete email address.

Inputs have an explicit label, a strong boundary and at least 48px height. A placeholder supports a label rather than replacing it. Pair aria-describedby with visible help or an error; set aria-invalid="true" only after validation finds an error. Keep error text adjacent and useful. Use native required, disabled and control types where they fit.

Shared classes: .kh-form__label, .kh-form__input, .kh-form__textarea, .kh-form__select. Behaviour and validation belong to the owning form. Sources: index.scss and _kh-cartridge-system.scss.

Search mode toggle and form


<fieldset class="kh-search-mode">
  <legend>Control preview</legend>
  <label class="kh-search-mode__option">
    <input type="radio" name="guide-mode" value="keyword" checked>
    Keyword
  </label>
  <label class="kh-search-mode__option">
    <input type="radio" name="guide-mode" value="semantic">
    Meaning
  </label>
</fieldset>
Control preview

The checked radio gives its parent a white-on-cobalt selected state through :has(input:checked). :has(input:focus-visible) supplies the keyboard indicator. Give each instance a unique radio name and an accessible legend.

In production, the fieldset starts hidden; the search module reveals it when mode switching is available. /search/ synchronizes the selected radio, panel visibility, input focus and search_type=semantic URL parameter. This reference demonstrates native control states; it does not attach a second search controller.

Search-form markup


<div class="kh-search-widget">
  <div class="kh-search-widget__panel">
    <form class="kh-search-widget__form" action="/search/" method="get">
      <label class="kh-u-sr-only" for="guide-keyword">Search my site</label>
      <input type="search" id="guide-keyword" name="search_query" class="kh-form__input" placeholder="Search my site">
      <button type="submit" class="kh-button" aria-label="Search"><span class="kh-button__label" aria-hidden="true">Search</span><span class="kh-button__icon" aria-hidden="true">→</span></button>
    </form>
  </div>
</div>

At widths up to and including 600px, the label and arrow spans swap, and the submit button sits inside the input as a fixed 44px target. The input reserves space for that target, its gap and the browser’s native search-clear control. Long query text and the caret must remain visible before the button in both search modes. Both are hidden from assistive technology, so the button's aria-label supplies its name. Preserve that name when adapting the markup. Keyword submission uses search_query; semantic input is owned by the existing search implementation. Use unique demo IDs rather than production controller IDs.

Source of truth: src/site/search.njk, _semantic-search.scss and _kh-cartridge-system.scss. Test keyboard mode switching, empty/results/error states and the icon-button state at and below 600px.


<div class="kh-ask" aria-label="Example conversation">
  <div class="kh-ask__conversation">
    <p class="kh-ask__message kh-ask__message--user">What has Ken written about design systems?</p>
    <p class="kh-ask__message kh-ask__message--system">Example response: start with the work record and related writing.</p>
    <p class="kh-ask__message kh-ask__message--status">Example loading state…</p>
  </div>
  <ul class="kh-ask__results">
    <li class="kh-ask__result"><a href="/work/">Work and impact</a>
      <p>A real destination used as a harmless result example.</p>
    </li>
  </ul>
</div>

What has Ken written about design systems?

Example response: start with the work record and related writing.

Example loading state…

Hook Responsibility
.kh-ask Conversation wrapper
.kh-ask__conversation Message list; production uses role="log", aria-live="polite", aria-relevant="additions"
.kh-ask__message--user / --system User and response treatments
.kh-ask__message--status Loading/status feedback
.kh-ask__results / __result Result list and individual entries

This static sample does not create a live region or load the model. Production wiring uses ask-form, ask-input and ask-conversation; do not copy those IDs into a second controller instance. Retain loading, empty, failure and retry explanations; model downloading must not look like an unresponsive button.

Behaviour: src/site/semantic-search.js and src/site/search.njk. Presentation: _semantic-search.scss. Use the working Search page for behavioural checks.

Metrics and snapshots


<div class="kh-metrics-grid">
  <div class="kh-metric"><span class="kh-metric__number">20+</span><span class="kh-metric__label">Years of work</span></div>
  <div class="kh-metric"><span class="kh-metric__number">15</span><span class="kh-metric__label">Sites in the UNDRR ecosystem</span></div>
</div>
20+Years of work
15Sites in the UNDRR ecosystem

Snapshot list


<div class="kh-career-snapshot">
  <ul class="kh-snapshot-list">
    <li><strong>Practice:</strong> Platforms, editorial operations and shared standards.</li>
    <li><strong>Evidence:</strong> Link a claim to its <a href="/work/">work record</a>.</li>
  </ul>
</div>
  • Practice: Platforms, editorial operations and shared standards.
  • Evidence: Link a claim to its work record.

Numbers need a visible explanation, a scope and a source. Distinguish response time, database latency, delivery speed and campaign engagement. Use tabular numerals for values that update. Sources: index.scss, _kh-cartridge-system.scss and the production CV.

Data marks

These build-time marks carry text equivalents and links; they must remain meaningful with CSS disabled. They are not interchangeable with headline metric tiles.

Pattern Implementation Meaning and constraint
Publishing timeline / pulse partials/pulse-strip.njk; pulseMonths filter Dated publishing activity, with links and collapsed empty periods; not a decorative progress bar
Neighbour sequence partials/sequence-mark.njk; neighbourhood filter This entry and chronological neighbours; retained in the entry-foot assembly where selected by layout data
Reading-length gauge partials/length-gauge.njk; lengthFrame filter Position among the comparison corpus; keep the word count, percentile and median explanation
Topic tally topicTally filter in the article layout Number of entries sharing a topic; preserve the visible count

The publishing strip uses a cobalt archive tab with a yellow edge, a cobalt rail and ink dots. Dot area represents monthly entry count; the scale and chronological positions remain unchanged. A yellow ring and a secondary tick identify the current entry’s month, while red slashes mark collapsed empty years. The visible size key, month-link labels and keyboard bypass explain the data without relying on colour. Preserve the explicit track width, recent-end scroll origin and contained horizontal scrolling.

Article metadata separates a yellow date stamp, the word count and a labelled length gauge. The gauge states “Longer than …% of entries” visibly and retains the corpus median in its accessible text and tooltip. Topics wrap as complete links with an attached count and optional detail underneath the parent name. Counts refer to the parent topic, including when a child detail is shown. Preserve real links, 44px targets, wrapping at enlarged text sizes and data-pagefind-ignore; these labels belong to the article chrome, not its search excerpt.

Entry-type key

Where type is encoded as a mark, preserve shape, colour and the text equivalent together. Avoid inventing new abbreviations in a legend. SVGs may carry their own presentation colours; check the actual generated mark rather than assuming every SVG consumes a CSS token. The current article places its publishing timeline at the end, not in the opening masthead.

Sources: _kh-dataviz.scss, config/eleventy/ filters, partials/entry-foot.njk and the individual partials. Add data-pagefind-ignore to navigation that repeats other entries' titles. Authorship offers “Follow new posts” through RSS and Mastodon, separately from contact and CV links. The entry foot renders related posts only when neighbours exist. Its kh-entry-foot--no-related modifier lets authorship span the full row and removes the stacked gap when there is no preceding list; otherwise related posts and authorship share two columns on wide screens. The chronological sequence spans the row in both cases.

Layout primitives

The shell and colour fields span the viewport. Header, homepage and footer content share a centred 72rem measure with at least 2rem desktop gutters and 1rem mobile gutters. Ordinary page layouts remain capped at 76rem; .kh-content defaults to 70ch and article prose to about 62ch. .kh-content--wide removes the generic content measure, not every enclosing page constraint.

Breakpoints

Sass token Value Purpose
$kh-breakpoint--sm / --sm-down 600px / 599px Small-screen boundary
$kh-breakpoint--md / --md-down 846px / 845px Main layout changes
$kh-breakpoint--lg / --lg-down 1024px / 1023px Larger grid spacing
$kh-breakpoint--xl 1300px Wide reading layouts and margin notes

Use the -down partner for max-width rules so adjacent ranges do not both match the same boundary pixel. Source: _settings.scss.

General grid


<div class="kh-grid">
  <div class="kh-note-box">First cell</div>
  <div class="kh-note-box">Second cell</div>
  <div class="kh-note-box">Third cell</div>
</div>
First cell
Second cell
Third cell

Three-column grid and spans


<div class="kh-grid kh-grid__col-3">
  <div class="kh-grid__col--span-1 kh-note-box">One track</div>
  <div class="kh-grid__col--span-2 kh-note-box">Two tracks</div>
</div>
One track
Two tracks

Label and content grid


<div class="kh-grid-stylized">
  <div>
    <p class="kh-meta">A meaningful label</p>
  </div>
  <div>
    <p>Content associated with the label. An empty leading placeholder collapses in the current theme.</p>
  </div>
</div>

A meaningful label

Content associated with the label. An empty leading placeholder collapses in the current theme.

Vertical stack


<div class="kh-stack">
  <p>First block</p>
  <p>Second block using the established sibling spacing.</p>
  <p>Third block</p>
</div>

First block

Second block using the established sibling spacing.

Third block


<div class="kh-stack kh-stack--800">
  <p>A larger vertical stack</p>
  <p>The <code>kh-stack--800</code> modifier uses 2rem sibling spacing.</p>
  <p>Use the established modifier rather than inventing a numeric suffix.</p>
</div>

A larger vertical stack

The kh-stack--800 modifier uses 2rem sibling spacing.

Use the established modifier rather than inventing a numeric suffix.

The default stack uses 1rem; .kh-stack--800 uses 2rem. A purpose-built component can supply --kh-stack-margin--custom. The ordinary --kh-stack-margin is reset on stack children and grandchildren, so setting it on a wrapper is not the same override.

Wrapping cluster


<div class="kh-cluster"><a class="kh-button" href="/blog/">Blog</a><a class="kh-button" href="/work/">Work</a><a class="kh-button" href="/photos/">Photos</a></div>

.kh-cluster is plain wrapping flex with gap and zero direct-child margins. It does not impose display or margins on grandchildren. Do not restore the old negative-margin gutter rules or use !important spacing overrides. For a denser composition, create a purpose-built component rather than changing this shared primitive.

Full-width fields and retained bleed hooks

Current cover/writing/footer fields use full-width blocks with fluid --kh-cart-gutter padding. Keep content centred and extend decorative background layers, instead of widening paragraphs. The full-width regression check covers these fields at mobile and wide viewports. This is page-level markup in the full-width homepage main, not a breakout applied inside an article:

<section class="kh-cartridge-writing" aria-labelledby="writing-title">
  <div class="kh-cartridge-section-head">
    <h2 id="writing-title">Ideas in circulation</h2>
    <a href="/all/">All writing</a>
  </div>
  <div class="kh-datasheet-list">
    <!-- Render the shared post-summary partial for each entry. -->
  </div>
</section>

.kh-u-fullbleed remains a legacy pseudo-element helper using viewport arithmetic. It is not the current shell's implementation and should not be the starting point for a new section. .kh-bleed-out remains available for wide figures; its left-side escape depends on the surrounding layout and must be checked at real widths.

Sources: index.scss, _kh-cartridge.scss, _kh-cartridge-system.scss. See the design guide composition before adding a new page composition.

Pager and navigation states


<nav class="kh-pager" aria-label="Pagination example">
  <ul class="kh-pager__list">
    <li><a href="/all/" class="kh-pager__link">← Newer</a></li>
    <li><a href="/all/" class="kh-pager__link">1</a></li>
    <li><a href="#pager" class="kh-pager__link kh-pager__link--current" aria-current="page">2</a></li>
    <li><a href="/all/3/" class="kh-pager__link">3</a></li>
    <li><a href="/all/3/" class="kh-pager__link">Older →</a></li>
  </ul>
</nav>

Use the shared partials/pager.njk for actual collections. It receives Eleventy's pagination object plus optional pagerLabel, pagerNewer and pagerOlder, and suppresses itself when only one page exists. The current link carries .kh-pager__link--current and aria-current="page"; newer/older destinations remain real links. The example above labels its own local state, not the page's global navigation.

The primary navigation has two strengths: .kh-navigation__link--active marks the exact page; --section identifies a parent section. Only exact-page links receive aria-current. Writing stays a parent on paginated /all/ routes. Label destinations using the interface vocabulary.

Sources: partials/pager.njk, layouts/base.njk, _kh-datasheet.scss, index.scss and _kh-cartridge.scss.

Spacing utilities

Prefer a component's layout/gap before adding per-child offsets. The existing utilities are explicit hooks, not a generated universal scale: do not assume a new numeric suffix exists.

Class Property Value
.kh-u-margin__bottom--200 margin-bottom 0.5rem
.kh-u-margin__bottom--600 margin-bottom 1.5rem
.kh-u-margin__top--1200 margin-top 3rem
.kh-u-padding__bottom--200 padding-bottom 0.75rem
.kh-u-padding__bottom--400 padding-bottom 1rem
.kh-u-padding__top--500 padding-top 1.5rem
.kh-u-padding__top--600 padding-top 2rem
.kh-u-padding__top--800 padding-top 3rem

--kh-stack-margin--custom is the stack's intentional spacing override; the ordinary --kh-stack-margin is set/reset by the stack rules; --kh-page-grid-gap supplies the shared gap (1rem, rising to 2rem at 1024px). A component-specific gap can override that default. Check the cascade before stacking a utility onto an existing margin. Sources: index.scss and _kh-content.scss.

Font assets

Face Weight Role
Science Gothic Cover 750 Homepage trial; width 60, slant −5, contrast 0; fixed Latin instance, about 32 KB
Anton 400 Other display headings, self-hosted Latin WOFF2, about 15 KB
IBM Plex Sans 400, 400 italic, 600 Body and interface
League Mono 100–800; width 50–200% Code and metadata use 400 at 100% width

Plex Sans, Anton and the Science Gothic cover face are static builds. Do not use variable-font axis settings on Plex or Anton. A request for 900 does not create a heavier Anton. Keep archived Recursive and Datatype files: posts document and use them. See font source notes.

Video embeds


<div class="kh-video">
  <iframe title="Local video-layout placeholder" srcdoc="&lt;p&gt;16:9 local placeholder. A production video needs a descriptive title and captions.&lt;/p&gt;" sandbox loading="lazy"></iframe>
</div>

.kh-video is a responsive 16:9 wrapper; its iframe/object/embed fills the wrapper. Use a descriptive iframe title, captions and a useful adjacent explanation. The live sample uses an isolated local placeholder so the reference does not load a video service.

A real embed should earn its loading cost; use a link when readers only need a reference. Production iframe permissions, URLs and playback behaviour belong to that embed's integration. Source: .kh-video in index.scss and its reading-context spacing in _kh-content.scss.

Feedback and confirmation toast

The real feedback action and counter are assembled by partials/feedback.njk. Keep the action's service URL and rel="nofollow"; keep the live remote SVG counter's eleventy:ignore so the build never freezes or rasterises it. Use a grammar-neutral label because its count is unknown at build time. The action uses the shared .kh-button treatment: square cobalt fill, white Plex Sans 600 text, a 44px minimum target, ink hover and visible keyboard focus. .kh-feedback__action removes the button’s outer margin; visiting the service must not change its appearance.

Fragment-driven confirmation

The service redirects back to #thanks. That fragment targets the hidden .kh-feedback-thanks element; CSS displays the fixed banner, starts the timer and dismisses it after about 15 seconds. The production element carries aria-live="polite". This pattern uses no feedback-submission JavaScript.


<p class="kh-meta">Was this useful?</p>
<a class="kh-button kh-feedback__action" href="#guide-feedback-toast"><span aria-hidden="true">&#128077;&nbsp;</span> This was useful</a>

Was this useful?

This was useful

The demo deliberately targets a local example ID and never calls the service. Re-trigger by navigating away from its fragment and back. Check the announcement and focus experience as well as the visual banner. Source: index.scss (.kh-feedback-thanks, kh-banner-in, kh-banner-out, kh-timer) and the feedback implementation article.

Earlier visual treatments

The graph paper, full-site light effect and ruled numbered mastheads are retired from the shared shell. The lighting article and font history preserve the experiments. The proposal board preserves the design directions. Retaining an archive does not make every archived treatment a current default. Social-sharing cards use the current palette and type in their own fixed-size, noindex document.

Decorative backgrounds use near-white paper, angled colour fields and small sawtooth edges. The writing-field edge and role ribbon use cartridge-edge.svg as a repeated mask; cartridge-pattern.svg supplies the original cover marks. Its low-contrast companion, cartridge-paper-pattern.svg, repeats across the homepage hero, article header, contact section and exposed paper above the footer’s green field, including on small screens. Article reading columns stay plain. Patterns belong in margins and section boundaries, with upright content and enough clear space for focus rings.

Accessibility contracts

The base layout's first link points to #main-content. .kh-u-sr-only.kh-skip-link hides it visually until keyboard focus; focus restores the size and clip so it is usable. Keep one real target in the layout rather than inserting competing demo IDs.

Visually hidden text

.kh-u-sr-only keeps content in the accessibility tree. aria-hidden="true" removes content from it. They are not alternatives: use the former for an accessible label, the latter for genuinely redundant decoration. Pull-quotes also carry data-pagefind-ignore because they repeat body text.

Focus and control states

Shared controls use an ink outline and white inner ring. Check links and buttons on paper, cobalt and green, alongside selected, hovered, disabled and invalid states. Keep visible labels, unique IDs and native control semantics. Primary actions are at least 44px; inputs are at least 48px high.

CSS-off mode

Every custom rule belongs inside body:has(#kh-css-toggle:checked). The footer owns the real checked checkbox. Do not add a second checkbox with that ID, or put inline presentation styles into a demo that would survive CSS-off. Source order, text alternatives and real links must continue to work without styling.

Motion and enlarged text

New motion must honour prefers-reduced-motion. Review existing animated components on their own merits; a semantic pattern does not guarantee its animation is already compliant. Test at 200% text sizing: cover text must reflow, and clipping is only for decoration. The overflow checker specifically checks enlarged cover text as well as document width.

Contrast and non-colour meaning

Use the palette's measured combinations. Keep charts' text keys and shape cues. Check forced-colour/high-contrast modes in the actual component; do not infer support solely from the ordinary screenshot. Alt text, captions and print content remain part of the component contract.

Utilities, tokens and implementation

Visibility utilities

These describe the actual rules in index.scss, including legacy naming. Do not infer a breakpoint from a class name.

Class Current behaviour
.kh-u-show-for-mobile-only Screen widths below 600px
.kh-u-show-for-medium-up Visible from 600px upward; despite its name, the hide rule ends at 599px
.kh-u-show-for-medium-only 846–1023px
.kh-u-show-for-large 1024px and above
.kh-u-show-for-print-only, .kh-u-for-print-only Hidden on screen, available in print
.kh-u-do-not-print Hidden in print
.kh-u-sr-only Visually hidden; available to assistive technology

Do not use a visibility utility to hide the only navigation at a viewport width. Preserve the legacy names until an intentional migration; document their behaviour here.

Text, link and navigation hooks

Hook Contract
.kh-u-text--nowrap Prevents wrapping; use only when the content can still fit at enlarged text sizes
.kh-u-text-color--grey Consumes --kh-color--grey, mapped to muted ink by the theme
.kh-link Standalone link styling outside ordinary .kh-content prose
.kh-navigation, __list, __item, __link Navigation structure; active/section state described under Pager
.ken-link--print Print wrapper that exposes link destinations

Print

Keep reading order and captions useful when colour/backgrounds disappear. Screen-only controls use .kh-u-do-not-print; print-only contact content uses the existing print utilities. Margin notes return to the flow. Check the CV's print action, a long article, a table and a figure after changing shared typography or widths.

Current token reference

Property or group Current role/value
--kh-cart-paper / --kh-cart-ink #faf9f5 / #151515
--kh-cart-blue / --kh-cart-yellow #173ebc / #f6d92f
--kh-cart-red / --kh-cart-green #ee3e35 / #007c55
--kh-ground Alias of paper
--kh-color--blue, --kh-color--apparatus Aliases of cobalt
--kh-color--sun Yellow in the cartridge system; the name is retained for compatibility
--kh-color--sun--deep, --kh-color--yellow--dark Cobalt in the cartridge system
--kh-ink-muted, --kh-color--grey #5b5e5a muted ink
--kh-color--visited #563d82 for visited reading links
--kh-panel-bg #ffffff
--kh-rule, --kh-rule--strong Ink at 20% opacity / solid ink
--kh-cart-gutter Fluid outer gutter aligning a 72rem content measure; minimum 2rem, 1rem on mobile
--kh-cart-cut Decorative diagonal depth, clamped from 1.5rem to 3.5rem
--kh-page-grid-gap 1rem; 2rem from 1024px
--kh-grid-stylized-module--prime Legacy 16rem label track, where the layout retains it
--kh-body-width Legacy base-shell setting; the cartridge shell overrides it, so it does not control current full-width fields
--kh-font-sans, --kh-font-mono Self-hosted Plex Sans / League Mono stacks with system fallbacks

Component overrides and ownership

.kh-box reads --kh-box-theme-color--background and --kh-box-theme-color--foreground. Old button-colour properties remain in the base CSS but do not override the cartridge button rule. Prefer a purposeful component modifier to an undocumented inline override. Keep new custom properties declared or provide an intentional fallback; lint:css-vars checks unresolved reads.

Layout frontmatter supplies cartridgeTheme: page, home, article, note, story, photo, profile or utility. Base/layout inheritance supplies the body class and display-font preload. Do not repeat a layout's default flag in every post. Standalone lab documents and historical experiments must identify themselves rather than silently becoming alternative site defaults.

Concern Source of truth
Palette, shell, cover and article composition src/components/vf-componenet-rollup/_kh-cartridge.scss
Shared controls, page families and guide primitives _kh-cartridge-system.scss in the same directory
Content typography, notes, figures and demos _kh-content.scss
Retained primitives and utilities _kh-datasheet.scss, index.scss, _settings.scss
Behaviour The relevant partial/module, not a duplicate controller in this reference
Naming and copy Editorial guide

Use data-pagefind-ignore for repeated chrome and other entries' titles. Use noindex for non-destinations and kens_status: draft for reviewable unpublished posts. Keep those exclusions in their existing shared mechanisms.

Verifying a change

  • Check real source markup and at least one production use before documenting a variant.
  • Exercise keyboard focus, native disclosures, the local toast, search submission and narrow/wide layouts. Keep examples' actions harmless.
  • Check CSS-off, 200% text, print, reduced motion and high-contrast behaviour. A live demo documents a contract; it is not proof of all accessibility states.
  • Run yarn lint:css, production rendering, yarn lint:links, yarn lint:images, yarn lint:css-vars and yarn lint:overflow as appropriate. Run production link/image gates before restarting dev, whose image endpoints differ.
  • Keep old section IDs next to the replacement material so shared links remain useful. Update this reference and the design guide with implementation changes.