Powder24 p24-ui reference
Signed in as Sample Person

p24-ui v1

The shared Powder24 stylesheet for P24 apps. Link it, put class="p24-body" on the body, and use the p24- classes below. Nothing is styled until an element opts in.

<link rel="stylesheet" href="https://apps.powder24.co.uk/p24-ui/v1/p24.css">
<link rel="icon" href="https://apps.powder24.co.uk/p24-ui/v1/favicon.svg" type="image/svg+xml">

Colour

Black, white and the brand gradient. Status colours carry meaning only, never decoration.

--p24-bg

--p24-surface

--p24-surface-sunk

--p24-table-group-bg

--p24-table-hover-bg

--p24-ink

--p24-ink-muted

--p24-chrome

--p24-toast-bg

--p24-success

--p24-warning

--p24-danger

--p24-info

--p24-neutral

Type

Heading one

Heading two

Heading three

Heading four

Body text is Geist at 16px. Paragraphs in .p24-prose stop at about seventy characters so a wide page never stretches a sentence across the screen.

Muted small text for secondary detail. A text link is ink, underlined.

Geist Mono for identifiers: APPS-320 · 2026-09-28

Tabular figures: 1,204.50 · 98.10

100events
7brands

Spacing

The page rhythm: 48px between sections, 16px from a heading to its content, and 16px between stacked blocks and notices. The headings, .p24-section, .p24-stack and .p24-prose use these tokens. An app's own spacing reads them with a literal fallback, as in var(--p24-space-block, 1rem). Gaps inside a component — card padding, button clusters, form fields, table cells — are not rhythm.

--p24-space-section · between sections · 48px

--p24-space-heading · heading to content · 16px

--p24-space-block · between stacked blocks and notices · 16px

A heading, 16px above its content

A paragraph, then two notices in a .p24-stack, each 16px below the last. Each section on this page sits 48px below the one before it.

Stacked. A notice 16px below the paragraph.
Stacked again. And another 16px below that.

One white bar for every app. The wordmark links back to the Apps Hub in the same tab; the app's name beside it is plain text. On the right, the app's own links — Documentation, then Dashboard, then any others, each in a new tab — and the signed-in person's name. Every slot but the wordmark and name is optional, and an absent slot is an absent element, never an empty one.

Bare: wordmark and app name only.

Powder24 Example app

Links only.

Powder24 Example app

Identity only.

Powder24 Example app
Signed in as Sample Person

Full: in-page sections, links and a long name cut with an ellipsis.

Powder24 Example app
Signed in as Sample Person With A Much Longer Display Name
<header class="p24-header"><div class="p24-wrap p24-header__inner">
  <span class="p24-header__brand">
    <a class="p24-header__home" href="https://apps.powder24.co.uk/" aria-label="Powder24 Apps"><img class="p24-wordmark" src="https://apps.powder24.co.uk/p24-ui/v1/p24-wordmark.svg" alt="Powder24" width="138" height="22"></a>
    <span class="p24-header__app">App name</span>
  </span>
  <div class="p24-header__tools">
    <nav class="p24-header__links" aria-label="App links">
      <a class="p24-header__link" href="…" target="_blank" rel="noopener">Documentation</a>
      <a class="p24-header__link" href="…" target="_blank" rel="noopener">Dashboard</a>
    </nav>
    <span class="p24-header__identity" title="Name"><span class="p24-visually-hidden">Signed in as </span>Name</span>
  </div>
</div></header>

Live and demo copies

An app with a live copy and a demo or test copy that look alike marks which is which. The live copy shows LIVE after the app name; any copy that is not live shows the banner straight after the header, on every page, signed in or not. The word LIVE and the banner's wording are in the markup, so both still read without the stylesheet.

The live copy.

Powder24 Example app LIVE

A demo copy.

Powder24 Example app — DEMO
DEMO. This copy works against demo skifarm-api and the FTP test folders, never live bookings or live files.
<span class="p24-header__brand">
  …
  <span class="p24-header__app">App name</span>
  <span class="p24-live-marker" title="…">LIVE</span>
</span>

</header>
<div class="p24-mode-banner" role="status"><div class="p24-wrap"><strong>DEMO.</strong> …</div></div>
<main …>

Buttons

One brand button for the main action on a page; black pills for everyday actions.

Link as button

Forms

Channel prefix and seven hex characters.
Enter between 1 and 28 nights.

Cards, chips and badges

Quote Tester

up · 84 ms

Interactive card: hover to raise it.

12PassDriftFailSandboxSkipped

Transfer Provider Tester

down · 503

Sunk card, for panels inside a page.

slowno health endpointsandbox

Inverse card

Black, as the site's own panels.

Functionality Testers (5) Empty category (0)

Tables

Cells are middle-aligned at 12px by 16px; .p24-table--compact is for dense data screens. Put every table in a .p24-table-wrap, so it scrolls inside its frame rather than widening the page.

Quote results, demo
Nights Result
TignesTravelgate1,204.507Pass
Val ThorensInterhome986.007Drift
Les ArcsHotelBeds2,310.7514Fail
ChamonixEurotours640.204Skipped
Courchevel 1850, where the provider only returned a price after the search was retried twice with a wider date window, so the quote carries the drift badge until the next nightly run confirms itTravelgate3,480.007Drift
CompactCodeCount
Airline baggage ruleSKI-12742
Deposit messagingSKI-1407

Grouped tables

One table whose rows fall into groups that open and close. Each group is a tbody.p24-group led by a full-width header row; its toggle button carries aria-expanded, and a closed group carries .p24-group--collapsed. p24-ui ships no script, so each app flips both with a few lines of its own:

document.addEventListener("click", function (e) {
  var toggle = e.target.closest(".p24-group__toggle");
  if (!toggle) return;
  var open = toggle.getAttribute("aria-expanded") !== "true";
  toggle.setAttribute("aria-expanded", String(open));
  var group = toggle.closest(".p24-group");
  if (group) group.classList.toggle("p24-group--collapsed", !open);
});
Issues on demo, by Epic
KeySummaryStatusPRs
Open Epic 3 issues
APPS-646Grouped table and filter bar patternsIn review1
APPS-632Readable Release Hub tablesDone2
APPS-637Epic groups on the Release HubTo do0
Open Epic 2 issues
APPS-605Stack builds on unmerged branchesDone1
APPS-618Design passes before skill textDone1
1 issue
APPS-410Dev note in env statusBlocked1

Filter bar

Checkbox chips, each a label and a count, led by an All chip. Each chip is a .p24-check label around a real checkbox, so the bar works with Tab and Space and reads as a set of checkboxes. The app keeps All in step: checked when every value is, indeterminate when some are.

Tabs

Notices, toasts, spinners and dialogs

Saved. The rule is live on demo.
Check before running. Demo talks to live partners.
Sandbox. dev-1 to dev-4 use provider sandboxes.
A neutral notice.
Export ready: 1,204 rows.
Two providers are slow.
The run stopped: provider timeout.
Running against demo.
A plain toast.
Loading…

Delete this rule?

It stops applying on demo straight away. This cannot be undone.

Wide dialog

For forms or tables that need room.

Documentation pages

For pages that explain how something works in plain English. Every page keeps the same blocks in the same order, tags name the areas it belongs to, and the source card links to the document it was written from.

Payments

Who uses it

Customer service
Checks when a customer's next payment is due.
Finance
Reconciles the overnight payment run each morning.

Watch out for

  • The run uses UTC, so 23:00 is midnight in summer.
  • Demo talks to live partners.

Example

Inline code uses .p24-code; a sample uses a code block.

Find a booking's paymentssql
SELECT Id, Amount, DueDate FROM Payments WHERE BookingId = @bookingId ORDER BY DueDate;
For developers

Notes most readers can skip go in a collapsible section.

Layout

The page is at most 1280px wide (.p24-wrap) with side margins that grow with the screen; above 1280px it simply stops growing. Data-heavy pages use .p24-wrap--full. Breakpoints are 800px and 1280px, as on powder24.co.uk. p24-ui is light only, on a white page.

The layout default: page content sits in .p24-wrap, like the header, so it lines up with the wordmark; a full-width page uses .p24-wrap--full on the header and the page alike. Reading width is capped on the content inside, with max-width: var(--p24-measure), never by narrowing or centring the wrap. The wrap's side padding grows to clear a notched screen's edges.

A full-width wrap inside this page.