Style reference
Parastrate's brand and developer guide. Start with the identity, colors, typography, and spacing; then use the HTML/CSS conventions, recipes, and page template to build with them.
The Parastrate identity
Purl is the leaning, open-bowled P in violet. Use the supplied artwork; its outline and lean are part of the mark. The specimens below are the original SVG files, linked for download.
PurlThe standalone violet mark, shown on white. Light lockupPurl and the Ink wordmark on a light background. Dark lockupPurl and the Mist wordmark on Night.
Logo use
Keep clear space on every side of at least 0.21 of the P's height. The standalone mark is at least 20 px tall on screen; a lockup is at least 96 px wide. Preserve proportions, use the supplied color variants, and keep the mark clear of busy imagery. For every variant, print sizes, and misuse examples, see the brand artwork guide. For its position in a page heading, see logo placement.
Imagery and illustration
- Use imagery to explain the subject: a mechanism, a flight, a book, or the actual tool. Preserve the proportions and details people need to understand it.
- Keep screenshots and scenes inside their own frame. They may retain their own colors; surrounding captions, controls, and page surfaces use the theme tokens.
- Give informative images useful alternative text and, when explanation is needed, a visible caption. Use empty alternative text for purely decorative images.
- Use the existing SVG artwork for the logo. Do not redraw it inside an illustration or add a shadow, glow, bevel, or rotation to the mark.
Use the tokens, and both themes come free
Every color on a page comes from the --wb-* tokens in theme.css; none is written out, and the page itself is white, --wb-surface (S2). The same names hold light and dark values, so a page written in tokens works in both (S3). Every token, with its light and dark value and what it is for, is in the token reference. Switch this page between Light, Dark and Device above to see the tokens change.
- Opt in on
<html>:data-theme="auto"follows the device,"dark"and"light"force one. A page with nodata-themestays light and is rejected (S3). - Grounds: the page is white,
--wb-surface, one surface with the shell's own panels. Cards, panels and tables are--wb-surfacetoo, set apart by a 1 px--wb-borderhairline, not by a different ground.--wb-canvas, the faint gray, is only for wells, the tab strip and insets;--wb-surface-insetfor a hover. No beige, no paper, no navy of your own (S2). - Text:
--wb-text, and--wb-text-mutedfor what is secondary. Both meet 4.5:1 on every ground, in both themes. - Accent:
--wb-accentfor links, the current item, the one primary button and focus rings, sparingly. Status uses--wb-success,--wb-warning,--wb-dangerand--wb-info, always with a word, never color alone. A color that carries meaning keeps its meaning in both themes. - Scroll bars are thin, with a Royal Purple thumb (
--wb-scrollbar-thumb, set bytheme.cssfor the whole page, a lighter tint of it on dark grounds). Don't restyle them. Thin is set per element (scrollbar-widthis not inherited):theme.csssets it on*, so a scroller inside your page is covered, and a web component with a shadow root that scrolls says it in its own stylesheet. A scroll bar drawn on a canvas uses the same thickness (10 px) and the same token value. - Pictures and 3D may have their own colors inside their frame (a WebGL scene is dark); the page around them is in tokens.
The brand palette
- Purl violet
#7b3cffThe P itself. The master artwork keeps this violet.
- Royal Purple
#473089The shared interface accent, matching the Home button: links, primary buttons, focus rings, and the scrollbar thumb. Hover:
#3a2672. Set bytheme.css, with a lighter purple in dark mode. - Night
#02060cThe sign-in scene and the logo's dark background.
- Mist
#f0f0f3The wordmark on a dark background.
- Ink
#303036The wordmark on a light background.
These are the logo's and the shell's colors, not tokens for your content: inside a page use the tokens. The logo files and their rules are on the brand page.
Outfit to read, JetBrains Mono to label
Two faces, both served from this site (/src/branding/fonts.css, usable from the apps too). Outfit sets everything people read. JetBrains Mono is for labels like the one above this heading, for data (hosts, counts, times, codes) and for code; at most a third of a page's text (S1). Never a serif, never a page set entirely in mono.
Page title · 1.75rem / 400Mechanical StudiesSection · 1.2rem / 500DrivetrainItem title · 1rem / 500The differentialBody · 15px / 400, 1.55How a car turns without scrubbing its tires.Lead, secondary · 300, mutedInteractive 3D studies of mechanisms and devices.Label · mono 0.64rem, capsDrivetrain · 3 studiesData · mono 0.74remmechanisms.parastrate.com · 7 sections- Buttons and fields don't inherit the page's face on their own; a browser sets them in its system font (Arial, mostly). Add
button, input, select, textarea { font-family: inherit; }. It is the most common way a page fails S1. - Weights: 300 for leads, 400 for text and the page title, 500 for section and item titles. Outfit at 700–800 shouts; it is not used.
- Case: sentence case for headings and buttons; capitals only in a mono label, with 0.13em letter-spacing. Letter-spacing is never added to Outfit.
- Icons are inline SVG in
currentColor, 13–16 px; there is no icon font. An app or page is marked by a small tile of two letters (26 px, 6 px corners, mono 0.64rem, a faint tint of the accent behind the accent-colored letters).
A 4 px grid, hairlines and small radii
4 px8 px12 px16 px24 px32 px48 px
- Spacing in steps of 4 px: 4, 8, 12, 16, 24, 32, 48. 16 px between related things, 32 px between sections.
- Edges: 1 px hairlines in
--wb-border;--wb-border-strongonly to separate major regions. - Corners: 4 px for controls (
--wb-radius-control), 8 px for panels and cards, round pills for chips. No heavy shadows;--wb-shadow-smat most on something raised. - Targets: controls at least 36 px tall on a desktop and 44 px on a phone.
- Decoration is restrained. No gradients, sheens, banners or glow. A group of cards gets one quiet cue: a 3 px line along the top of each card in the group's muted color (violet
#9b86d6for study, brass#b39a5efor desktop tools; written out, not tokens), and chips in a faint tint of the same color. Everything else is white, hairlines and text.
Where the P goes, and why
Every page carries the Purl, once, at its start. It hangs in the left gutter, outside the content, beside the first line of the page's heading, and links to the dashboard. It never takes a line of its own.
P ┌────────────────────────── │ Heading │ The content, all on one │ clean left edge… │
The rules (S5, S9)
- Size: 26 × 24 px (22–32 px wide is accepted). The file is
https://parastrate.com/src/branding/purl.svg. Never recolored, outlined, rotated or put on a tile here; the brand page has the variants for other uses. - Desktop: its right edge 14 px before the content's left edge, in the 72 px gutter; its middle on the middle of the heading's first line.
- Phone: the gutter is gone; the P starts the heading's line, 10 px before the heading, still centered on its first line.
- One: a single Purl per page, at the top. The shell's own logo does not count; your page still carries its own.
- A link to
https://parastrate.com/dashboard, named "Parastrate home". In a tab it brings Home forward.
Why
The P is a signature, not a heading. Hanging it in the margin keeps the content's left edge one clean line, the way hanging punctuation keeps a column of text straight, so the eye finds the start of every page in the same place. It costs no vertical space, so the heading and the first thing a person came for stay as high on the screen as they can. And it is the same on every page, which is what makes the apps read as one family: a reader learns once where the way home is.
One left edge, and one indent for each level
The same policy governs every heading and the content under it, in the left menu, the right panel, Home and any page: the heading's first letter and the first thing in every row under it start on the same left edge. That first thing is a tile, a chevron, a color bar, or the text itself. Nothing under a heading starts to the left or the right of it for no reason.
STUDY the heading's first letter [Hs] HESI A2 Prep a tile on the edge, its label 10 px after it [Bi] BIO 140 Study LIBRARY Books a text-only row: its text on the edge v Building 2 a chevron on the edge, the name one indent in The Visual Handbook the books hang from the name, on its edge Another book
- The edge. In the left menu it is 21 px from the panel's side (8 px of padding and a 13 px gutter), in the right panel 25 px, on Home 28 px, and on a page the 72 px gutter. Within one panel it is a single number: a heading, a tile, a text-only row and a chevron all start on it.
- An indent is 16 px. Each level of nesting steps in by one: a contents entry one level down, a shelf's name after its chevron. A level never steps by another amount, and a child hangs from its parent's text, not from its marker.
- Tile, marker, then label. A tile or a color bar sits on the edge and the label follows it at a fixed gap (10 px). A row with no tile puts its label on the edge; it does not add a blank slot where a tile would be.
- A hover or current-row background reaches out, content stays put. The pill behind a row extends past the edge (2 px in the left menu, 8 px in the right panel) so its text can start on the edge. Never pad a row's content in to make room for its highlight.
- Rows in a card or a table start at the card's or the cell's padding, the same for every row; a link row does not get its own extra inset.
- It is measured.
node tools/check-shell-indent.mjsloads the dashboard and fails if any heading and its content are off the edge, or a level is not one indent.
Quick start
This page is public and is plain HTML: everything on it, including every rule and every token, is text that can be read with no script running. A plain-text index of the files is at /llms.txt, and the tokens as data are at /src/style-tokens.json. If you are building something for Parastrate, this is what to do; each point is explained in the section named.
- Start from the page template. Four shared files from
https://parastrate.com/src/(fonts.css,theme.css,page.css,embed.js),data-theme="auto"on<html>, and the<main data-page>frame with its Purl. - Semantic elements first. Use shallow hierarchy selectors, minimal purposeful classes, and
<div>only where neutral grouping is needed. - Every color is a token (
var(--wb-surface),var(--wb-text),var(--wb-accent)…). The page is white. See color and themes and the token reference. - Outfit to read, JetBrains Mono to label (at most a third of the text); add
button, input, select, textarea { font-family: inherit; }. See typography. - Fill the tab. Content starts at the 72 px gutter and runs to a 32 px edge; no centered column. One Purl hangs in the gutter beside the first heading and links to
/dashboard. See page layout. - A heading and its content share one left edge, and each level of nesting steps in by 16 px. A hover or current-row background reaches out past that edge; it never pushes the content in. See alignment and hierarchy.
- A 4 px grid, 1 px hairlines, corners of 4 px on controls and 8 px on panels, no heavy shadows. No gradients, sheens or banners: a group gets one quiet cue. See spacing and shape.
- Use the site's components (
wb-button,wb-card,wb-tabs,wb-accordion, the dialog service) before making your own, and neveralert()orconfirm(). - Nothing scrolls sideways at 1280 or 390 px; targets are 36 px tall on a desktop and 44 px on a phone; focus is always visible; status is never color alone. See accessibility and motion.
- Scroll bars are thin and Royal Purple, from the theme. Do not restyle them. See color and themes.
- Check it:
node tools/check-style.mjs <your id>from parastrate.com must say Accepted for the visual checks; review the HTML/CSS policy separately.
Semantic elements, shallow selectors
Semantic elements first, shallow hierarchy selectors, minimal classes, and <div> only where neutral grouping is needed. This is the authoring policy for new and revised Parastrate pages. Existing pages move toward it in focused changes, with their appearance and behavior checked along the way.
- Choose an element for its meaning. Use
mainfor the page's main content,navfor navigation, headings and lists for structure,buttonfor actions, andafor destinations. Asectionis a thematic group, usually with a heading; anarticleis self-contained content. Do not use either merely as a layout wrapper. - Keep grouping honest. Remove wrappers that serve no purpose. Use
<div>when a necessary layout or scripting group has no suitable semantic element. A zero-div count is not a goal. - Style elements and local relationships first. Set shared defaults on elements, then use short selectors such as
article > headerornav a[aria-current="page"]. Usually one or two relationships are enough. Avoid selectors that encode the entire path from the page root, or depend on an incidental child position. CSS nesting follows the same rule. - Add a class when it earns its place. A reusable component or a meaningful variation may need one clear hook. Name its role, such as
.product-card, rather than its current appearance, such as.purple-box. Avoid a class on every child when the hierarchy already identifies it. - Use attributes for real meaning and state. Native attributes such as
disabledandhidden, and appropriate ARIA states such asaria-currentandaria-pressed, can drive styling. Keep shared hooks such asdata-page. Replacing every class with adata-*attribute does not add semantics; never add ARIA solely as a styling hook. - Keep behavior stable during cleanup. Check scripts that generate markup or select classes before editing them. Prefer explicit action hooks or stable IDs for JavaScript where practical. Update affected selectors and browser checks together, then verify keyboard behavior and desktop and phone layouts in both themes.
A semantic group, rendered
Recent studies
Choose a resource to explore.
HTML
<section aria-labelledby="studies-heading">
<header>
<h3 id="studies-heading">Recent studies</h3>
<p>Choose a resource to explore.</p>
</header>
<ul>
<li><a href="/books">Books</a></li>
<li><a href="/about">About Parastrate</a></li>
</ul>
</section>
CSS
/* Shared defaults for this page's semantic groups. */
section > header { margin-block-end: var(--wb-space-lg); }
section > header p { color: var(--wb-text-muted); }
li > a { text-underline-offset: 3px; }
/* A component with a distinct purpose may have a class. */
.product-card { border: 1px solid var(--wb-border); }
The visual checker below does not assess semantic correctness or this selector policy. Review these decisions in the markup and styles; an Accepted visual result does not certify them.
HTML/CSS recipes
Start with the page template, then use these patterns inside its main content. The snippets illustrate markup, styles, and hooks; form submissions should use the page's existing handler.
A labeled form without layout wrappers
<form id="profile-form" aria-labelledby="profile-heading"> <h3 id="profile-heading">Profile</h3> <label for="display-name">Display name</label> <input id="display-name" name="display_name" autocomplete="nickname" required> <p id="name-error" role="alert"></p> <button type="submit">Save profile</button> <p id="profile-status" role="status"></p> </form>
The form, label, input, and button already express their roles. Use a fieldset and legend when several controls form a named group; add a neutral wrapper only if the layout requires one.
Element defaults and real states
form { display: grid; gap: var(--wb-space-sm); }
form > h3, form > p { margin: 0; }
input, select, textarea, button { font: inherit; }
input { min-block-size: 36px; padding-inline: 12px;
color: var(--wb-text); background: var(--wb-surface);
border: 1px solid var(--wb-border); border-radius: var(--wb-radius-control); }
input[aria-invalid="true"] { border-color: var(--wb-danger); }
button:disabled { opacity: 0.6; cursor: default; }
:focus-visible { outline: 2px solid var(--wb-focus); outline-offset: 2px; }
@media (max-width: 759px) {
input, select, textarea, button { min-block-size: 44px; }
}
The error message carries the meaning; the border reinforces it. A disabled button is disabled in HTML, so its interaction and appearance agree. Use the site's button component when the form needs its shared button styling.
JavaScript hooks that survive a styling change
// In the existing handler's invalid-name branch:
const name = document.getElementById('display-name');
const error = document.getElementById('name-error');
name.setAttribute('aria-invalid', 'true');
name.setAttribute('aria-describedby', 'name-error');
error.textContent = 'Enter a display name.';
name.focus();
// When that validation error is cleared:
name.removeAttribute('aria-invalid');
name.removeAttribute('aria-describedby');
error.textContent = '';
These IDs identify the field and its error, independently of visual styling. If a field also has help text, retain its ID in aria-describedby when adding or clearing an error. For repeated controls, use a dedicated action hook and scope the handler to the relevant form.
Start from this
Four shared files from parastrate.com, data-theme on <html>, and the page frame. Everything else is your content, in tokens. The frame, page.css, sets the gutter (--page-gutter: 72px), the right edge (--page-edge: 32px), the page title's size and line height (--page-h1, --page-h1-line) and the longest line of running text (--page-measure: 75ch); it styles [data-page], [data-page-head], [data-purl] and [data-label] (a mono caps label), and gives h2, h3, links and code their type. Extend it with semantic elements and shallow selectors; add a class only when it clarifies a reusable role or meaningful variation. See the HTML/CSS policy.
<!DOCTYPE html>
<html lang="en" data-theme="auto">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Mechanical Studies · Parastrate</title>
<link rel="stylesheet" href="https://parastrate.com/src/branding/fonts.css">
<link rel="stylesheet" href="https://parastrate.com/src/components/theme.css">
<link rel="stylesheet" href="https://parastrate.com/src/page.css">
<script src="https://parastrate.com/src/embed.js"></script>
</head>
<body>
<main data-page>
<header data-page-head>
<a data-purl href="https://parastrate.com/dashboard" aria-label="Parastrate home">
<img src="https://parastrate.com/src/branding/purl.svg" alt="" width="26" height="24"></a>
<h1>Mechanical Studies</h1>
<p>What each part does, and why the whole thing works.</p>
</header>
<!-- your content: full width, colors from var(--wb-…) -->
</main>
</body>
</html>
Bringing an existing app in line
Most apps already route their colors through a few variables of their own. Point those at the tokens instead of rewriting every page; that is how Study Guides moved over, all 22 guides at once:
/* the app's own names, now from Parastrate's tokens (theme.css loads first) */
:root {
--bg: var(--wb-surface); --bg2: var(--wb-surface); --bg3: var(--wb-border);
--tx: var(--wb-text); --tx2: var(--wb-text-muted);
--acc: var(--wb-accent); --grn: var(--wb-success); --red: var(--wb-danger);
}
body { font-family: var(--wb-font-family); }
button, input, select, textarea { font-family: inherit; }
html[data-embedded] .app-header, html[data-embedded] .app-sidebar { display: none; } /* or mark them data-chrome */
No variables, only hard-coded colors (the exam apps were like this)? Map each color by its role, not its hue: the page and panels to --wb-surface, hover and insets to --wb-surface-inset, lines to --wb-border, text to --wb-text and --wb-text-muted, the app's brand color to --wb-accent. A color that carries meaning keeps its meaning: a right answer stays --wb-success and a wrong one --wb-warning or --wb-danger, even when the brand color it used to share becomes violet.
Then: data-theme="auto" on <html>, the four shared files, the content from the gutter instead of a centered column, and the Purl beside the first heading. Colors chosen for a dark page (pale greens, light purples) need a darker value for light: give them a light value and a dark one, as tokens do.
Before you ship
- Review the HTML/CSS policy: element meanings, necessary wrappers, short selectors, purposeful classes, and any JavaScript hooks affected by markup changes.
- Run
node tools/check-style.mjs <your id>from parastrate.com (ids as intools/sites.json); it must say Accepted. It judges an app on a desktop as the dashboard shows it, in a tab, with itsdata-chromehidden. - Open it in the dashboard as a tab, and on a phone, in both themes.
- Deploy, and commit the updated
src/style-report.json(the check also rewrites this page's rules and verdicts from it) so this page shows where it stands.
Use the site's components before making your own
- If it looks like a choice, it is one. A card in a "pick one" grid - a title, a line about it, a border - is clicked by people whether or not it is a link. Make the whole card the way in (with a visible "Open →" or the card's own button), or make it plainly not a choice: no border, no hover. Never a card that looks pickable and does nothing.
- One ring at a time. A selected item shows its selection; it does not also draw a focus ring around it when clicked. Keyboard focus on an unselected item still shows.
- Every dialog goes through the dialog service, never
window.alert,confirmorprompt, and never a native<dialog>. A phone opens no dialogs.
Standalone web components in /src/components, themed by the same tokens (load theme.css first, then the component as a module from https://parastrate.com/src/components/<name>/<name>.js; each file documents every attribute, event and part at its top).
| Component | For | Main attributes |
|---|---|---|
wb-button | A button, or a link styled as one (with href). | color primary, secondary, success, warning, danger, info, accent, muted, light, dark · size xs to xl · variant solid, outline, ghost, soft, link · disabled, loading, block, href |
wb-card | A card: header (title, subtitle, badge), body, footer. | variant default, outlined, elevated, flat, inset · size default, compact · clickable, selected, collapsible |
wb-tabs, wb-tab | Sections of a page, one visible at a time. | variant document, compact, underline (for sections of a page) · closable; on a tab: name, icon, active, pinned |
wb-accordion, wb-accordion-item | Folding sections, with the keyboard behavior of a WAI-ARIA accordion. | multiple · variant default, flush, borderless, plain · size · icon-position; on an item: label, description, badge, expanded |
dialogs (wb-dialog) | Every dialog, through dialog-service.js. | dialogs.confirm(message, { okLabel, danger }) → true or false · prompt · alert · info, success, warning, error · question |
wb-shell | The dashboard's own frame (north, west, center, east, south; resizable sides). A page does not use it. | resizable · --wb-shell-west-size, --wb-shell-east-size and their -min and -max |
<script type="module" src="https://parastrate.com/src/components/wb-button/wb-button.js"></script>
<script type="module" src="https://parastrate.com/src/components/wb-tabs/wb-tabs.js"></script>
<wb-button color="primary">Save</wb-button>
<wb-button variant="outline" size="sm">Cancel</wb-button>
<wb-button href="https://parastrate.com/dashboard" variant="ghost">Home</wb-button>
<wb-tabs variant="underline">
<wb-tab name="Overview">…</wb-tab>
<wb-tab name="Details">…</wb-tab>
</wb-tabs>
<script type="module">
import { dialogs } from 'https://parastrate.com/src/components/wb-dialog/dialog-service.js';
if (await dialogs.confirm('Delete this? It cannot be undone.', { okLabel: 'Delete', danger: true })) remove();
</script>
Patterns that are not components
The rest of a page is plain elements styled with tokens. Prefer elements and shallow relationships, as in the HTML/CSS policy. The few classes below identify reusable roles; they are optional hooks for patterns that need to be distinguished from surrounding content.
/* a link: the accent, underlined 3 px away (page.css does this inside [data-page]) */
a { color: var(--wb-accent); text-underline-offset: 3px; }
a:hover { color: var(--wb-accent-hover); }
/* a field */
input, select, textarea { font: inherit; min-block-size: 36px; padding: 0 12px; color: var(--wb-text);
background: var(--wb-canvas); border: 1px solid var(--wb-border); border-radius: var(--wb-radius-control); }
input:focus { outline: none; border-color: var(--wb-accent); background: var(--wb-surface);
box-shadow: 0 0 0 3px color-mix(in srgb, var(--wb-accent) 18%, transparent); }
/* a chip: a small round link or tag */
.chip { display: inline-flex; align-items: center; min-block-size: 26px; padding: 2px 9px; font-size: 0.75rem;
color: var(--wb-text-muted); border: 1px solid var(--wb-border); border-radius: 999px; text-decoration: none; }
.chip:hover { color: var(--wb-accent); border-color: var(--wb-accent); }
/* a table: hairlines, a mono caps header, no zebra */
table { inline-size: 100%; border-collapse: collapse; background: var(--wb-surface); border: 1px solid var(--wb-border); border-radius: 8px; }
th { text-align: start; padding: 10px 14px 8px; border-bottom: 1px solid var(--wb-border);
font: 400 0.64rem/1.3 var(--wb-font-mono); letter-spacing: 0.13em; text-transform: uppercase; color: var(--wb-text-muted); }
td { padding: 10px 14px; border-bottom: 1px solid var(--wb-border); }
/* a status: a word in a pill, tinted from the status color; never the color alone */
.status { display: inline-block; padding: 1px 10px; border-radius: 999px; font-size: 0.78rem;
background: color-mix(in srgb, var(--wb-success) 16%, var(--wb-surface));
color: color-mix(in srgb, var(--wb-success) 70%, var(--wb-text)); }
/* a mark: the two-letter tile for an app or a page */
.mark { display: inline-grid; place-items: center; inline-size: 26px; block-size: 26px; border-radius: 6px;
font: 500 0.64rem/1 var(--wb-font-mono); background: color-mix(in srgb, var(--wb-accent) 11%, var(--wb-surface)); color: var(--wb-accent); }
Inside the shell, a page is a tab
On a desktop, Parastrate is one application: the logo, search, who you are and sign-out across the top; every app and page down the left; a panel on the right that follows what is open; a footer. Your page is the center, one tab among others, in a frame.
| Width | What the shell does | What your page does |
|---|---|---|
| 1100 px and up | Left menu and right panel both open; the two sides can be dragged wider or narrower (left 180–480 px, right 240–640 px), and the middle always keeps at least 320 px. | The 72 px gutter and 32 px right edge. Plan for 760–1300 px. |
| 760 to 1099 px | Left menu only. What the right panel would show opens in a dialog. | The same page, a little narrower. |
| Under 760 px (a phone) | No shell, no tabs, no panels, no dialogs: reading and taking exams only. Desktop-only apps show as a picture. | The gutter is gone; the Purl starts the heading's line. Targets 44 px. |
| Checked at | 1280 px and 390 px. | Nothing may scroll sideways at either (S7). |
- Fill the tab (S4). The page's main container spans the full width. Content starts at the 72 px gutter and runs to a 32 px edge on the right. Never a narrow column centered on a colored ground: inside the shell it reads as a page that does not fit. Running text may stop at 75 characters a line, still flush left.
- Leave the shell its job (S6). Load
embed.js. Mark your own logo, "back to the dashboard" link, sign-out and footer withdata-chrome: in a tab they disappear, because the shell has them; on their own and on a phone they show. Never build your own sign-out into a page. - Links. With
embed.js, a link to another Parastrate page or app opens it as a tab, and a link to/dashboardgoes to Home. Links to other sites open in a new window. Your own app's links stay in your tab. - A main-site page that can stand alone (Admin, Your account) adds
data-tabto theembed.jstag: opened by itself on a desktop, it moves into the dashboard as a tab. A page that anyone may read without signing in (this one, About, Brand) does not, so it stays where it is. - An app's own bar and menus are phone navigation. On a desktop the shell is the navigation: the left side lists every app, and the right panel lists the open app's sections, which open in its tab. So an app's own header, sidebar or library is
data-chrome: hidden in a tab, shown on its own and on a phone, where it is the only way around. - No sideways scrolling (S7) at any width from 390 px up. Wide tables scroll inside their own box; a bar of tabs scrolls sideways only, never up and down.
What the rules cover, for now
- Every page of parastrate.com that opens in the shell, and each app's front page (its hub or landing page, and in Study Guides every guide).
- Not yet: full-window tools and scenes (the Wireframe editor, a 3D mechanism, a flight, a game), whose content is the whole window. Their controls should still use the type, tokens and
embed.js. - Skipped for now, by the owner's decision on 18 October 2026: HESI A2, BIO 140, HEA 133, Leet and Arcade (which keep their own looks). Wireframe's front page is the editor itself, a full-window tool.
- Outside the rules: the signed-out pages (sign-in, register, password reset, verify). They are the front door, never in the shell, and keep their Night design.
Visible focus, calm motion, nothing by color alone
- Focus is always visible:
:focus-visible { outline: 2px solid var(--wb-focus); outline-offset: 2px; }(page.csssets it). A custom control that hides the browser's ring draws its own, in the same color. - Motion is short and quiet: 120 ms for a hover or a press, 180 ms for a panel opening (
--wb-duration-fast,--wb-duration-normal,--wb-easing). Underprefers-reduced-motion: reduceturn transitions and animations off:@media (prefers-reduced-motion: reduce) { * { transition: none !important; animation: none !important; } }. - Contrast: text 4.5:1 or better on its ground, in both themes (S3 measures it in dark). Never convey a status by color alone: use a word (Accepted, Failed) and, if you like, the color with it.
- Names: every control has an accessible name (visible text, or
aria-labelon an icon-only one); every image that carries meaning hasalt, and decorative images havealt="". A page haslang, a viewport meta and atitle(S8): "Page name · Parastrate". - Keyboard: everything reachable by Tab, activated by Enter or Space; the components give tabs and accordions their arrow-key behavior. Targets are 36 px on a desktop and 44 px on a phone.
Every design token, with its light and dark value
These are all the custom properties theme.css defines (/src/components/theme.css; as data, /src/style-tokens.json). Light is the default; the dark value applies under data-theme="dark", or under "auto" on a dark device. "Same" means the dark theme does not change it. This section is written from theme.css by tools/render-style.mjs, so it cannot fall behind it. The colored chip shows the token in the theme this page is showing.
Color
| Token | Light | Dark | Use |
|---|---|---|---|
--wb-canvas | #f5f7fa | #0d1520 | The faint gray behind: wells, the tab strip, insets. Not for the page itself. |
--wb-surface | #ffffff | #151f2c | The page, panels, cards and tables: one white surface (S2). |
--wb-surface-raised | #ffffff | #1b2736 | Something lifted off the page: a dialog, a menu, an open accordion. The same white in light; a step lighter in dark. |
--wb-surface-inset | #eef1f5 | #1f2b3a | An inset area, and the hover of a row. |
--wb-text | #0d1520 | #e6ebf2 | Text (S2). 4.5:1 or better on every ground, in both themes. |
--wb-text-muted | #566374 | #9aa8b8 | Secondary text: leads, captions, labels. Also 4.5:1 or better. |
--wb-border | #d6dde5 | #2a3747 | 1 px hairlines: between rows, around cards and tables. |
--wb-border-strong | #9aa8b8 | #4a5a6e | The edge between major regions only. |
--wb-accent | #473089 | #a98bff | Royal Purple, shared with Home: links, the current item, the one primary button, selection. Sparingly. A lighter purple in dark mode. |
--wb-accent-hover | #3a2672 | #bda6ff | Hover and pressed state of accent links and buttons. |
--wb-on-accent | #ffffff | #0d1520 | Text or an icon on an accent fill. |
--wb-focus | #473089 | #a98bff | The focus ring: 2 px, offset 2 px, on every focusable thing. |
--wb-danger | #b42318 | #f97066 | Failed, destructive, wrong. With a word, never color alone. |
--wb-on-danger | #ffffff | #0d1520 | Text on a danger fill. |
--wb-success | #147a42 | #4ade80 | Done, passed, right. |
--wb-on-success | #ffffff | #0d1520 | Text on a success fill. |
--wb-warning | #a15c00 | #fbbf24 | Needs a look; a wrong answer that is not an error. |
--wb-on-warning | #ffffff | #0d1520 | Text on a warning fill. |
--wb-info | #0566b3 | #60a5fa | Information, neutral news. |
--wb-on-info | #ffffff | #0d1520 | Text on an info fill. |
--wb-neutral | #566374 | #9aa8b8 | A status with no judgement in it (a count, "draft"). |
--wb-on-neutral | #ffffff | #0d1520 | Text on a neutral fill. |
Type
| Token | Light | Dark | Use |
|---|---|---|---|
--wb-font-family | 'Outfit', system-ui, -apple-system, 'Segoe UI', Roboto, 'Helvetica Neue', Arial, sans-serif | same | Outfit, then the system sans-serif. Everything people read. |
--wb-font-mono | 'JetBrains Mono', ui-monospace, 'Cascadia Mono', Consolas, Menlo, monospace | same | JetBrains Mono, then the system monospace. Labels, data and code, at most a third of a page (S1). |
--wb-font-size | 0.875rem | same | Text inside components: buttons, fields, cards. (A page sets 15 px itself, below.) |
--wb-font-size-sm | 0.75rem | same | Small text inside components: captions, badges. |
--wb-font-size-lg | 1rem | same | Larger text inside components. |
--wb-font-weight-semibold | 500 | same | Titles: 500. Never 700 or more. |
--wb-line-height | 1.45 | same | Line height inside components. A page sets 1.55 itself. |
Space
| Token | Light | Dark | Use |
|---|---|---|---|
--wb-space-1 | 0.25rem | same | 4 px. |
--wb-space-2 | 0.5rem | same | 8 px. |
--wb-space-3 | 0.75rem | same | 12 px. |
--wb-space-xs | 0.25rem | same | 4 px: the same as --wb-space-1. |
--wb-space-sm | 0.5rem | same | 8 px. |
--wb-space-md | 0.75rem | same | 12 px. |
--wb-space-lg | 1rem | same | 16 px: between related things. |
--wb-space-xl | 1.5rem | same | 24 px. (32 px between sections is written out.) |
--wb-control-block-size | 2rem | same | Height of a control inside a component (32 px). A control you place yourself is at least 36 px tall on a desktop and 44 px on a phone. |
--wb-control-padding-inline | 0.75rem | same | Side padding of a control. |
Shape
| Token | Light | Dark | Use |
|---|---|---|---|
--wb-border-width | 1px | same | The hairline: 1 px. |
--wb-radius-xs | 0.125rem | same | The small corner of a component part: 2 px. |
--wb-radius-sm | 0.125rem | same | 2 px. |
--wb-radius-md | 0.125rem | same | 2 px. |
--wb-radius-lg | 0.125rem | same | 2 px. (Panels and cards use 8 px, written out; there is no token for it yet.) |
--wb-radius-control | 4px | same | A control, a list row and its hover: 4 px. |
Elevation and layers
| Token | Light | Dark | Use |
|---|---|---|---|
--wb-shadow-sm | 0 0.0625rem 0.1875rem rgb(13 21 32 / 0.10) | 0 0.0625rem 0.1875rem rgb(0 0 0 / 0.4) | The most a raised thing gets. No heavy shadows. |
--wb-shadow-md | 0 0.25rem 1rem rgb(13 21 32 / 0.12) | 0 0.25rem 1rem rgb(0 0 0 / 0.45) | A card or popover in a component. |
--wb-shadow-lg | 0 0.75rem 2rem rgb(13 21 32 / 0.16) | 0 0.75rem 2rem rgb(0 0 0 / 0.5) | A dialog. |
--wb-elevation | var(--wb-shadow-md) | same | The default elevation of cards and dialogs: --wb-shadow-md. |
--wb-z-dropdown | 1000 | same | Stacking order for menus and popovers: 1000. |
Motion
| Token | Light | Dark | Use |
|---|---|---|---|
--wb-duration-fast | 120ms | same | Hover, press, a chevron turning: 120 ms. |
--wb-duration-normal | 180ms | same | A panel opening, a dialog appearing: 180 ms. |
--wb-easing | cubic-bezier(0.2, 0, 0, 1) | same | The easing for all of it. Turn motion off under prefers-reduced-motion. |
Scroll bars
| Token | Light | Dark | Use |
|---|---|---|---|
--wb-scrollbar-thumb | #473089 | #8466dc | The thumb of every scroll bar, thin: Royal Purple, a lighter tint in dark. Never restyle it. |
--wb-scrollbar-track | transparent | same | The track: transparent, out of the way. |
Where everything is
All of these are public and need no sign-in. Files under /src/ are served with Access-Control-Allow-Origin: *, so an app on another host can load them.
| Address | What it is |
|---|---|
https://parastrate.com/style | This page. |
https://parastrate.com/llms.txt | A plain-text index of the style files, for language models. |
/src/components/theme.css | The tokens, light and dark. Load it first. |
/src/style-tokens.json | The same tokens as data: name, group, light value, dark value, use. |
/src/page.css | The page frame: gutter, heading, Purl, type, focus ring. |
/src/branding/fonts.css | Outfit and JetBrains Mono. |
/src/embed.js | Makes a page behave as a tab in the dashboard. |
/src/branding/purl.svg | The Purl P (also purl-black.svg, purl-white.svg, and the lockups logo-light.svg and logo-dark.svg). |
/src/components/<name>/<name>.js | The components: wb-button, wb-card, wb-tabs, wb-accordion, wb-dialog (and dialog-service.js), wb-shell. |
/src/style-report.json | The latest check of every page and app, as data. |
https://parastrate.com/branding | The brand page: logo variants, clear space and misuse. |
How a page is judged
Nine automated visual checks: node tools/check-style.mjs loads the configured pages of this site the way the dashboard shows them, and configured apps from their source, at a desktop and a phone width. Accepted means all nine checks passed in that run; semantic HTML, selector design, and the other authoring guidelines still need review.
| Rule | What it asks |
|---|---|
| S1 Type | Text is set in Outfit; JetBrains Mono only for labels, data and code (at most a third of the text). No other faces. |
| S2 Color | Colors come from the theme tokens: the page is white, --wb-surface (one surface with the shell’s panels), and body text is --wb-text. |
| S3 Light and dark | The page declares data-theme on <html> and, set to dark, turns dark: a dark ground with text at 4.5:1 or better. |
| S4 Width | The page fills its tab: its main container spans the width and content starts at the gutter (72 px). No centered column. |
| S5 The Purl | One Purl P, 22–32 px wide, hanging in the gutter to the left of the first heading, centered on its first line - never on a line of its own - and linking to the dashboard. |
| S6 In the shell | The page loads embed.js, so in a tab its own chrome hides and its links open as tabs. |
| S7 No sideways scroll | Nothing scrolls sideways at 1280 or 390 px. |
| S8 Document | The page has a lang, a viewport meta and a title. |
| S9 Phone | On a phone the Purl starts the heading’s line, still not a line of its own. |
Where every page stands
From the check of 2026-10-30 02:30 UTC. 11 of 18 accepted.
| Page or app | Verdict | What fails |
|---|---|---|
Adminparastrate.com/admin | Accepted | —All nine
|
Your accountparastrate.com/account | Accepted | —All nine
|
Merchparastrate.com/merch | Accepted | —All nine
|
Brandparastrate.com/branding | Accepted | —All nine
|
Aboutparastrate.com/about | Accepted | —All nine
|
Donateparastrate.com/donate | Accepted | —All nine
|
Style referenceparastrate.com/style | Rejected |
All nine
|
Booksparastrate.com/books | Accepted | —All nine
|
BIO 140 Studybio.parastrate.com | Skipped | Skipped for now (owner’s decision, 18 October 2026) |
Leet — Algorithm Visualizersleet.parastrate.com | Skipped | Skipped for now (owner’s decision, 18 October 2026) |
FlightDeck3Dflightdeck3d.parastrate.com | Accepted | —All nine
|
Study Guidesaws.parastrate.com | Accepted | —All nine
|
Mechanical Studiesmechanisms.parastrate.com | Accepted | —All nine
|
HESI A2 Prephesi.parastrate.com | Skipped | Skipped for now (owner’s decision, 18 October 2026) |
Arcademc3.parastrate.com | Skipped | Skipped for now (owner’s decision, 18 October 2026): the games keep the arcade look |
Certification Study Labcerts.parastrate.com | Accepted | —All nine
|
Wireframewireframe.parastrate.com | Skipped | Not judged yet: its front page is the editor, a full-window tool |
HEA 133 Study Roomhea133.parastrate.com | Skipped | Skipped for now (owner’s decision, 18 October 2026) |