A free, open-source, self-hosted place to write a novel.
Fablewright DESIGN.md
65 kB · 677 lines
Markdown
at main


name: Fablewright description: A self-hosted novel-writing floor where the heat in the prose is the save state. colors: surface-base: '#110402' surface-secondary: '#230905' surface-elevated: '#340d07' surface-highlight: '#46120a' surface-hot: '#7a2012' accent: '#af2e1a' accent-hover: '#b74230' border-control: '#c76c5e' border-container: '#691b0f' border-warm: '#d4a759' heading: '#cf8175' heading-sub: '#d7968c' text-primary: '#f7eae8' text-secondary: '#efd5d1' text-quiet: '#e7c0ba' text-muted: 'rgba(239, 213, 209, 0.55)' heat-hot: '#d3ae6e' heat-warm: '#a07e43' danger: '#bf5747' danger-text: '#cb6353' success: '#8fa667' warning: '#d4a759' info: '#6fa5a0' focus: '#d4a759' cursor: '#d4a759' shadow: '#46120a' typography: display: fontFamily: 'Cabin, sans-serif' fontSize: 'clamp(3rem, 5.5vw, 5.5rem)' fontWeight: 600 lineHeight: 0.98 letterSpacing: '-0.025em' page-heading: fontFamily: 'Cabin, sans-serif' fontSize: '1.75rem' fontWeight: 600 headline: fontFamily: 'Literata, Georgia, serif' fontSize: '1.25rem' fontWeight: 500 title: fontFamily: 'Cabin, sans-serif' fontSize: '0.875rem' fontWeight: 600 letterSpacing: '0.08em' button: fontFamily: 'Cabin, sans-serif' fontSize: '0.875rem' fontWeight: 600 lineHeight: 1.2 letterSpacing: '0.04em' key: fontFamily: 'Cabin, sans-serif' fontSize: '0.75rem' fontWeight: 600 letterSpacing: '0.08em' body: fontFamily: 'Literata, Georgia, serif' fontSize: 'clamp(1.0625rem, 1.35vw, 1.1875rem)' fontWeight: 400 lineHeight: 1.87 letterSpacing: '0em' body-alternate: fontFamily: 'Lexend, sans-serif' fontSize: 'clamp(1.0625rem, 1.35vw, 1.1875rem)' fontWeight: 400 lineHeight: 1.86 letterSpacing: '0em' label: fontFamily: 'Cabin, sans-serif' fontSize: '0.75rem' fontWeight: 600 letterSpacing: '0.12em' readout: fontFamily: 'Inconsolata, monospace' fontSize: '0.75rem' fontWeight: 400 letterSpacing: '0em' base: fontFamily: 'Literata, Georgia, serif' fontSize: '1rem' fontWeight: 400 wordmark-sm: fontFamily: 'Cabin, sans-serif' fontSize: '1rem' fontWeight: 700 letterSpacing: '0.1em' wordmark-md: fontFamily: 'Cabin, sans-serif' fontSize: '1.125rem' fontWeight: 700 letterSpacing: '0.09em' wordmark-lg: fontFamily: 'Cabin, sans-serif' fontSize: '1.5rem' fontWeight: 700 letterSpacing: '0.08em' wordmark-masthead: fontFamily: 'Cabin, sans-serif' fontSize: '2.25rem' fontWeight: 700 letterSpacing: '0.08em' wordmark-masthead-mark: fontFamily: 'Cabin, sans-serif' fontSize: '2.75rem' fontWeight: 700 glyph-key: fontFamily: 'Cabin, sans-serif' fontSize: '1.125rem' fontWeight: 400 pane-key: fontFamily: 'Cabin, sans-serif' fontSize: '1.1rem' fontWeight: 400 command: fontFamily: 'Inconsolata, monospace' fontSize: '1.125rem' fontWeight: 400 read-title: fontFamily: 'Cabin, sans-serif' fontSize: 'clamp(1.6rem, 3vw, 2.2rem)' fontWeight: 600 read-book: fontFamily: 'Cabin, sans-serif' fontSize: 'clamp(1.5rem, 2.6vw, 2rem)' fontWeight: 600 read-part: fontFamily: 'Cabin, sans-serif' fontSize: '1.35rem' fontWeight: 600 read-chapter: fontFamily: 'Cabin, sans-serif' fontSize: '1.15rem' fontWeight: 600 read-outline-book: fontFamily: 'Cabin, sans-serif' fontSize: '1.6rem' fontWeight: 600 read-outline-part: fontFamily: 'Cabin, sans-serif' fontSize: '1.1rem' fontWeight: 600 landing-section: fontFamily: 'Cabin, sans-serif' fontSize: 'clamp(1.75rem, 3vw, 2.5rem)' fontWeight: 600 error-heading: fontFamily: 'Cabin, sans-serif' fontSize: 'clamp(1.5rem, 4vw, 2rem)' fontWeight: 600 rounded: hairline: '1px' # a mark on a 2px track, never a component corner sm: '2px' md: '4px' card: '5px' lg: '6px' spacing: xs: '4px' sm: '8px' md: '16px' lg: '24px' xl: '40px' 2xl: '64px' 3xl: '96px' components: button: backgroundColor: '{colors.surface-elevated}' textColor: '{colors.text-secondary}' typography: '{typography.button}' rounded: '{rounded.md}' padding: '8px 24px' button-primary: backgroundColor: '{colors.accent}' textColor: '{colors.text-primary}' typography: '{typography.button}' rounded: '{rounded.md}' padding: '8px 24px' button-ghost: backgroundColor: 'transparent' textColor: '{colors.text-secondary}' typography: '{typography.key}' rounded: '{rounded.md}' padding: '5px 10px' button-danger: backgroundColor: '{colors.surface-elevated}' textColor: '{colors.danger-text}' typography: '{typography.button}' rounded: '{rounded.md}' padding: '8px 24px' field: backgroundColor: '{colors.surface-base}' textColor: '{colors.text-primary}' typography: '{typography.body}' rounded: '{rounded.md}' padding: '8px 12px' tab: backgroundColor: 'transparent' textColor: '{colors.text-secondary}' typography: '{typography.key}' padding: '8px 16px' tab-current: backgroundColor: '{colors.surface-elevated}' textColor: '{colors.text-primary}' typography: '{typography.key}' padding: '8px 16px' panel: backgroundColor: '{colors.surface-secondary}' textColor: '{colors.text-primary}' typography: '{typography.body}' rounded: '{rounded.lg}' card: backgroundColor: '{colors.surface-secondary}' textColor: '{colors.text-primary}' typography: '{typography.body}' rounded: '{rounded.md}' padding: '24px' chip: backgroundColor: 'transparent' textColor: '{colors.text-secondary}' typography: '{typography.readout}' rounded: '{rounded.sm}' padding: '3px 7px' tree-row: backgroundColor: '{colors.surface-elevated}' textColor: '{colors.text-secondary}' typography: '{typography.body}' rounded: '{rounded.card}' padding: '0 16px' dock-pill: backgroundColor: 'transparent' textColor: '{colors.text-secondary}' typography: '{typography.readout}' rounded: '{rounded.sm}' padding: '4px 7px' #

Design System: Fablewright #

Overview #

Creative North Star: "The Plotting Floor"

Fablewright is a floor you work on, not a set of drawers you open. Everything a writer needs lies on one plane: the manuscript runs down the middle like a line laid across it, the outline is wired down the left edge, and every reference surface — planning, notes, plot beats, versions, lookup, pace — is a board that slides in from the right. Nothing is hidden behind a maze of windows. The room is lit like a machine shop at night: a rust-ramp shell, ink that glows a little, and walls measured in single pixels.

The floor has one idea, and the rest of the system exists to keep it clear. Words go in hot and set as they are saved: the heat in the prose is the save state. That is not a badge sitting next to the text — it is the colour of the text itself. A writer asking "is my work safe" never has to move their eyes off the sentence they just wrote. Everything that competes with that answer is removed: no scanline band across the page, no texture behind the paragraph, no second celebration, no decoration in the warm colour.

The floor is quiet by default and answers to the pointer. Peripheral widgets rest a step back — the outline, the scene's own actions, the boards peeking at the right margin, the previews of the scenes above and below — then come up to full strength as the cursor approaches or something inside them takes focus. The writing surface itself never fades and never moves. It is the calm centre of the plane, and the plane arranges itself around it.

Key Characteristics:

  • One plane, three axes: a vertical manuscript stream, a wired outline to the left, a stack of context surfaces to the right.
  • The heat in the prose carries the save state; no separate indicator competes with it.
  • Walls are thin (1px) and shadows are solid offsets. Nothing blurs, glows, or floats in glass.
  • Controls physically press: a bevel, an offset, and real travel in both directions.
  • The warm accent is rationed to three jobs and never used as decoration.
  • Peripheral chrome fades with pointer proximity; the prose does not.

Colors #

The palette is the Digital Rust rust ramp in both modes, plus its six failure accents. PRODUCT.md pins it and src/lib/styles/tokens.css generates it from the specification; no hex value is hand-written in this document's place of truth. src/lib/styles/fablewright.css holds the roles this product adds — the two heat stops and the plane's geometry.

The strategy is Restrained: a tinted rust neutral shell, with colour doing specific jobs and nothing else.

Primary #

  • Digital Rust (#af2e1a): the one warm accent. It does three jobs and no others — unsaved words, the single primary action on a view, and where the writer is (the open scene, the current row, today's tick). It does not change between modes, because its jobs do not change.
  • Firewall Breach (#b74230): the accent on hover and on a destructive hover fill. Ghost Pixel on it measures 4.66:1; raw Amber Alert does not.

Secondary #

The six failure accents mark planning, never prose: Memory Leek (#8fa667), Stack Overglow (#d4a759), Blue Screen (#8791b0), Fractured Shell (#ba5a7d), Dead Thread (#6fa5a0) and Thermal Throttle (#d78556). Each appears as a swatch on a tree row, a card mark, a storyline heading or a note-type chip, and each carries its dim and bright variants in the palette. They are identity, not status: a scene's colour tells a writer which thread it belongs to.

Heat is the fourth family and belongs to this product alone. On the dark theme #d3ae6e (hot) and #a07e43 (warm) carry a warm chroma against the cooler white of body ink, so unsaved words read as lit while still clearing AA (9.6:1 and 5.3:1 on Event Horizon). In Safe Mode they become #8c2414 and #6c4d06: dark, warm values on the lit page, so a word in flight reads as pressed rather than glowing (7.5:1 and 6.6:1 on Ghost Pixel).

Neutral #

  • Event Horizon (#110402): the page and every recessed well.
  • Null Pointer (#230905): chrome — the header band, the rail, the surfaces that hold a panel.
  • Core Meltdown (#340d07): a raised card, menu row, or tree row.
  • Bad Sector (#46120a): hover fills, active list rows, and the shadow colour in both modes.
  • Bricked Board (#7a2012): the hot panel — the landing demonstration's status strip, and the only surface that stays dark in both modes. It is a specimen, not a workspace control.
  • Ghost Pixel (#f7eae8) and Phosphor Smoke (#efd5d1): primary and secondary ink. Phantom Current (#e7c0ba) is the quiet ink; muted text is Phosphor Smoke at 55%, which still clears AA on every dark surface.
  • Rouge Signal (#c76c5e) walls a control; Dark Packet (#691b0f) walls a container. The two are not interchangeable: a control identifies itself by its wall, a container is identified by its content.

Named Rules #

The Three Jobs Rule. The warm accent means unsaved words, the one primary action, and where you are. A fourth use is a bug, not a preference. Filters, hovers, selections, chosen colours, proofreading marks and checked controls all reach for something else. A checked box takes the machined fill and its check mark; a switch shows its thumb moved.

The Heat Is Text Rule. Heat is a text colour and never a background. Saved prose cools in one step (60ms), not a fade. The one state that overrides heat is a failed save, which turns the words to --dr-danger-text and keeps them.

The Two Modes Rule. Both modes are always reachable: the saved preference first, then the operating system, then the dark theme, applied by an inline script in src/app.html before first paint. A page the script never reaches still answers the system preference, because prefers-color-scheme: light overrides the same roles on :root:not([data-scheme]), and src/lib/styles/contrast.spec.ts pins that fallback block to the Safe Mode values. Safe Mode overrides role values only; the named ramp stops never change, because other tokens derive from them. Both modes clear WCAG 2.1 AA, and the same spec holds the three text surfaces above 4.5:1 so a future tint fails the suite rather than shipping.

Typography #

Display Font: Cabin (with Gill Sans, Trebuchet MS, sans-serif), set at 75% width Body Font: Literata (with Georgia, Times New Roman, serif), or Lexend when the account asks for it Label/Mono Font: Inconsolata (with ui-monospace, SF Mono, Menlo, Consolas, monospace)

Character: a humanist sign-painter for the room's labels, and a warm book face for everything the writer wrote. The pairing says the machine is not the work: chrome speaks in uppercase and tracking, prose speaks in serif at a fixed measure. The mono face is a readout — counts, times, key hints — and never a voice.

Lexend is the one alternate voice. A writer can choose it on Your account for prose, notes and fields; it has wider spacing and simpler letterforms, is designed for reading proficiency, and some dyslexic readers find it easier. It replaces the body role only, so the room's chrome and readouts still read as the floor. The choice belongs to the account and is painted into the first response, not read from browser storage.

All four are variable fonts, self-hosted as WOFF2 under static/fonts, declared in src/lib/styles/fonts.css, and cut to the Latin range the app ships. Nothing loads from another host, so the first viewport makes no third-party request. Lexend ships roman only, so its italics are the browser's slant.

Cabin carries a width axis from 75% to 100%, and chrome text takes it at --dr-font-stretch-heading (75%), the condensed end. The value inherits from body so no component has to repeat it. Literata, Lexend and Inconsolata declare a single width, so a browser pins their width axis and only Cabin narrows.

Hierarchy #

  • Display (Cabin 600, clamp(3rem, 5.5vw, 5.5rem), 0.98, -0.025em): the landing page's opening promise. Nothing inside the app uses it.
  • Page heading (Cabin 600, 1.75rem, Ghost Pixel ink): the library, admin, account, note-type, recovery, sharing and help titles. One role, one step, one colour: the sharing page used to render it at 2.5rem in the heading red, which read as a different product's page. The secret link at /s/[id] keeps 2.5rem, because a guest's first view of the project is not app chrome.
  • Headline (Literata 500, 1.25rem): the scene title in the workspace head. The title is the writer's words, so it takes the book face.
  • Title (Cabin 600, 0.875rem, 0.08em–0.1em tracking, uppercase): rail headings, storyline names, dialog titles and project word totalling.
  • Button (Cabin 600, 0.875rem, 0.04em, uppercase): the standard action label.
  • Key (Cabin 600, 0.75rem, 0.08em, uppercase): the small ghost buttons in the chrome — Scene, Notes, Find, Search, Progress, Project, Focus.
  • Body (Literata, or Lexend on an account that chose it, 400, clamp(1.0625rem, 1.35vw, 1.1875rem), 1.87 or 1.86): every word of prose and excerpts at the full measure. The measure is 66 characters (--fw-measure), resolved at the prose size. Notes and panel editors sit at a 21rem measure and keep 1.62, because the model returns a shorter line height there.
  • Label (Cabin 600, 0.75rem, 0.1em–0.12em, uppercase): tabs, field labels, captions. --fw-text-2xs (0.75rem) is the floor: nothing renders smaller.
  • Readout (Inconsolata, 0.75rem–0.875rem, tabular figures): word counts, dates, file names, key hints, the version count.

Named Rules #

The Measure Rule. Prose never runs past 66 characters. The measure is declared as a multiple of the prose size (--fw-measure: calc(var(--fw-prose-size) * 33)) and never in pixels or in ch, so it holds when the size changes and the column is the same width on every surface: the scene head, the stream previews, the read-through and the guide all resolve to one edge.

ch was the obvious unit and the wrong one. It measures the advance of 0, and a digit is wider than the average letter, so 66ch rendered about 74 characters in Literata and 82 in Lexend while the token said 66. The multiplier is the average advance of the shipped faces at the prose size, about 0.51em, which puts both faces within a character of 66. src/lib/styles/measure.spec.ts holds the shape of the token and e2e/measure.e2e.ts measures the rendered lines.

The Leading Rule. Prose leading comes from Golden Ratio Typography at the shipped measure. At the 19px cap the model reads the measure as 70 characters in Literata and returns a 1.868 base line height; Lexend reads 68 and 1.856. --fw-prose-leading carries 1.87 and the Lexend selector carries 1.86. The model's x-height correction is not used: both faces have a high x-height, so it lifts the leading to 2.18 and 2.25, which overshoots. src/lib/styles/leading.spec.ts pins the token and the surfaces that read it.

The Readout Rule. A number a writer compares with another number takes tnum and the mono face. Words today, a total, a word count, a version count: all of it lines up in columns even when the digits change.

Page-local steps #

A few surfaces set their own type sizes. The frontmatter records these sizes so a scan can distinguish a choice from drift. The wordmark takes 1rem, 1.125rem or 1.5rem, depending on its home. The landing masthead sets it at 2.25rem beside a 2.75rem Cooling Caret mark.

The read-through sets its own reading scale: clamp(1.6rem, 3vw, 2.2rem) for the title and clamp(1.5rem, 2.6vw, 2rem) for a book. Parts take 1.35rem, chapters take 1.15rem, and scene labels take 1rem. The outline uses 1.6rem for books and 1.1rem for parts.

Landing section headings take clamp(1.75rem, 3vw, 2.5rem), and its command readout takes 1.125rem. The error page takes clamp(1.5rem, 4vw, 2rem). The pane key takes 1.1rem.

Layout #

The workspace (/p/[id]) is a three-column plane under a single 52px chrome band.

  • Left axis (20rem): the manuscript outline in ManuscriptTree.svelte. Cards for book, part, chapter and scene, wired top to bottom with SVG beziers (.wire-svg, .wire-line), the active path in --dr-accent. Titles wrap without a line limit and rows grow to hold them. At 17rem with one-line rows, 43 of the seeded book's 51 titles were ellipsized. Below 60rem the column becomes a drawer over the stage, opened from the chrome, at the same 20rem. On a coarse pointer the actions key occupies the word-count column.
  • Centre (1fr): the stage. The scene head, then the writing surface, which is the only part of the page that never fades, never scales and never moves.
  • Selector (6.5rem, only while a board is open and above 80rem): the dock. It floats in the stage's trailing gutter at rest, where no prose reaches. A board adds this column so the dock sits between the prose and the board instead of on top of the words.
  • Right axis (21rem, or min(42rem, 50vw) when surfaces are stacked): the surface deck. Below 68rem it floats over the trailing edge of the stage instead of taking a column.

The vertical axis is a stream, not a page. Previews of the previous and next scene (.stream-ghost.above, .stream-ghost.below) sit directly above and below the active prose inside the writing surface, set in Literata at 85% scale and unboxed, so they read as the manuscript continuing past the edge of the view. Scrolling past the top or bottom boundary accumulates pull and scales the preview toward 1.0; crossing the threshold steps to that scene. The friction is deliberate: 160px between scenes of the same chapter, 420px across a chapter boundary. A dashed rule separates same-chapter neighbours; a solid rule marks the chapter boundary.

The right axis is a deck. Slot 0 is the on-hand surface, sitting directly beside the prose. Every surface to its right carries Bring forward and a close key in a small floating group, so any board can be dragged to the front of the plane without a menu. With Shift held, the wheel pans the deck horizontally and pulls the next surface in. Below 68rem only one surface shows, because an overlay cannot stack on an overlay.

Proximity decides how loud the edges are. Each peripheral widget reads its own custom property, a 0–1 distance score, and resolves it in CSS against a floor that belongs to the mode: --fw-fade-rail, --fw-fade-head-titles, --fw-fade-head-actions, --fw-fade-dock and --fw-fade-stream in src/lib/styles/fablewright.css. The floor is a contrast decision rather than a taste one, so Safe Mode sets a higher one. The stream previews are the exception: they are aria-hidden decoration rather than controls, so --fw-fade-stream keeps its 0.52 floor in both modes and the rule applies it directly, with no second multiplier to undo. At rest the kicker and excerpt measure 2.06:1 on the dark theme and 2.10:1 in Safe Mode, and the heading 4.38:1 and 3.30:1. That is deliberate: the preview is a peripheral cue, not content, and the Previous and Next keys in the scene head carry the same navigation for every input. A hover or a pull raises the preview to full opacity, where the text is readable. The rail's rows fade one by one and the scene that is open stays at 1.0. A side panel never fades, because a note's prose is read rather than glanced at. Hover or focus raises a widget to 1.0.

Spacing comes from --dr-space-*: 0.25, 0.5, 1, 1.5, 2.5, 4, 6rem. Dense chrome uses a 4px rhythm between the keys of one cluster; that repetition is the rhythm, not an accident.

Breakpoints: 80rem drops the dock while a board is open, because four columns below that leave the stage under 45 characters, and narrows the rail and the board to 18rem until that width returns; 68rem drops the surface deck to an overlay; 60rem turns the rail into a drawer; 56rem folds the chrome's actions into a disclosure; 40rem stacks the scene head, makes a side surface a full-width sheet, transposes the plot grid and moves the colour mode into the page actions; 24rem lets the drawer fill the screen and drops the word from the menu key. Four page-local steps sit between them: 64rem turns the feedback rail and composer into sheets, 46rem collapses the recovery split, 42rem stacks the landing product details and installation band, and 30rem moves the find field to its own row on a fine pointer. Coarse pointers get 44px targets: buttons and fields grow to 44px, and smaller parts keep their drawn size while a .tap-area overlay grows the hit area. An overlay is centred on its control, so where neighbours sit closer than 44px the control grows a real box instead — a menu row, an inline confirm's Delete and Keep — and two targets never overlap. On a fine pointer, the grid's move pair and an administration confirmation take a 24px floor. The outline's actions key takes 32px. The 18px checkbox stays small and relies on its spacing. A coarse pointer gives it the 44px overlay.

Elevation & Depth #

Depth is material, not atmosphere: solid offsets, hard edges, and a bevel that catches light from the top left. There is no blur shadow anywhere in the system, no backdrop filter and no glass. A raised object casts a solid Bad Sector offset down and to the right, stacked with a 1px inner highlight so the top edge reads as lit.

Recessed objects go the other way. Inputs, wells and the machined track of a switch take --dr-shadow-inner-lowlight and the darkest available fill; they carry no offset, because a well does not rise.

The whole system rests on one behaviour: the press cycle. Rest has a 2px offset. Hover lifts the object translate(-2px, -2px) and grows the shadow. Active drives it translate(2px, 2px) and collapses the shadow to nothing. A control that skips a step reads as broken, because every other control on the plane does it.

Shadow Vocabulary #

  • Resting offset (2px 2px 0 0 var(--dr-shadow-color) + inset 0 1px 0 rgba(255,255,255,0.1)): buttons, checks, small keys, the tree's action menus.
  • Raised offset (3px 3px 0 0): the primary action at rest, a drawer.
  • Hover offset (4px 4px 0 0): the same object under the pointer, with the travel that goes with it.
  • Collapsed (0 0 0 0): the pressed state.
  • Raised panel (--fw-shadow-card, 2px offset plus bevel): the move dialog and a destructive confirmation rail. The outline's rows and the library cards sit on the plane and carry no offset.
  • Dialog (6px 6px 0 0 plus bevel): a modal, which is the furthest thing off the plane.
  • Inner highlight / lowlight: the bevel on a raised object, and the recess of a well.

Named Rules #

The Solid Offset Rule. Light comes from the top left and shadows are solid. A blur radius is a different design system, and a gradient on a wall is a different one again. The direction is not a preference: the offset falls down-right on every raised thing.

The Press Cycle Rule. Every interactive surface answers a press with travel and a shadow change. If a control has a wall, it has an offset; if it has no wall, it is a ghost and stays flat, which is the one honest exception.

Shapes #

Corners are small and machined. --dr-radius is 4px and is the default; 2px is the small key, 5px is a card on the plane (--fw-radius-card) and 6px is a surface (--fw-radius-surface). Nothing exceeds 6px and nothing is a pill. A rounded shape reads as a soft product, and this floor is built out of panels.

Walls come in two tiers for components, with one heavier rule reserved for page chrome:

  • 1px is the wall. Ordinary controls and containers sitting on the plane draw 1px: buttons, fields, panels, chips, cards, notices and the tree's rows. --dr-border-color walls a control, --dr-border-color-container a container. This is the default and the house style.
  • 2px is for the edge that has to say something. It survives on a part too small to read at 1px: the 18px checkbox, the preference switch and the 24–32px keys. It also edges a recessed well where darkness alone is ambiguous, such as the tab rack, a command block or the search tally. It marks a layer that has left the plane: the project menu, the find bar, the search panel, the proofreader popover, the read-through's export popover and a dialog. It states a condition, such as a drop target's inset edge, the danger rail on a confirm row or a structural section rule. It does not make an ordinary control heavier.
  • 4px belongs to page and site chrome. The foot of the header band, the rule between landing sections, and the separator under a book title. Never on a component.

A divider carries one of two weights. A quiet divider inside a dialog or a panel takes 1px --dr-border-subtle. A structural boundary takes the 2px container rule: between scenes, above a diff, between sharing sections. Neither takes a colour from the accent ramp.

Components #

Buttons #

  • Shape: 4px radius, 1px wall, 0.5rem 1.5rem padding, and an uppercase 0.875rem label on 1.2 leading with 0.04em tracking, so it renders 35px tall.
  • Default: Core Meltdown fill, Phosphor Smoke ink, 2px offset and bevel. On hover the wall moves to Firewall Breach, the object lifts 2px and the shadow grows to 4px.
  • Primary (.btn-primary): Digital Rust fill, Ghost Pixel ink, 3px offset. Hover takes it to Firewall Breach and adds the small glow on the dark theme only, which the palette switches off on a lit page.
  • Ghost (.btn-ghost): no wall, no offset, no travel. Hover paints --dr-surface-highlight. This is the language of the chrome's dense rows — Scene, Notes, Find, Search, Progress, Project, Focus.
  • Small (.btn-sm): 5px by 10px padding at the 12px label, which renders 26px tall. Same physics, less metal.
  • Danger (.btn-danger): the danger wall and danger ink at rest; the Firewall Breach fill and Ghost Pixel ink on hover, exactly like the shared destructive treatment everywhere else.
  • Disabled: the highlight fill, muted ink, no shadow, no travel, not-allowed.

Fields #

  • Style: a recessed well. Event Horizon fill, 1px control wall, 4px radius, Literata at 1rem, inset 0 -1px 0 lowlight, no offset.
  • Placeholder: muted and italic, at 55% ink, which still clears AA.
  • Focus: the wall moves to the hover value and the shared 2px focus ring appears at a 2px offset — Stack Overglow in the dark theme, Digital Rust in Safe Mode.
  • Focus in the writing surface: no ring. The prose editor is not a field a writer visits but the place they live, so its caret is the only focus mark. Notes, note types and feedback keep the shared ring, because each is a smaller field the writer enters and leaves.
  • Invalid: the wall turns Amber Alert. Disabled: the wall disappears and the ink goes muted.

Tabs and filter keys #

  • Rack (.tabs): a recessed well — 2px container wall, Null Pointer fill, 2px gaps — because darkness alone would not edge the row. One tab language serves the whole app: the read-through's views, the plot grid's orientation, the recovery sections, the feedback views and the search panel's scene/note switch, so a writer learns it once.
  • Key (.tab): Cabin 600 at 12px with 0.08em tracking, uppercase, no wall, transparent at rest in secondary ink. Hover paints the highlight fill and primary ink. The current one reads as a key that is down: elevated fill, inner highlight, primary ink, and a 44px minimum on a coarse pointer. A tab with an href is navigation and reports aria-current; one without is local state and reports aria-pressed. A count rides beside its label in the muted mono readout and steps up to secondary ink when the key is down.
  • Filter key (.filter-key): the recovery list's version filters — the same language as a link, with a transparent 1px wall and 2px radius so the plate reads at rest, answering aria-current.
  • Neither takes the warm accent: a tab or a filter is a choice, not where the writer is.

Chips and marks #

  • Wordmark (.wordmark, .mark): the instance name in uppercase Cabin 700 (1rem in the workspace chrome and footer, 1.125rem on the landing header and sign-in panels, 1.5rem at large), preceded by the brand mark (0.88em by 0.92em). The mark pairs two manuscript revision symbols as pure CSS polygons (clip-path: polygon(...)) over a hard 2px Bad Sector offset (filter: drop-shadow(2px 2px 0 var(--dr-shadow-color))): a lower proofreader's insertion caret (^) in Digital Rust (::before) and an upper six-spoke editorial asterisk (*) in Stack Overglow (::after), reading together as both a margin correction mark and a spark above crossed logs. At 1rem (.wordmark.sm), the asterisk's inner valleys deepen and its spoke span widens slightly so all six spokes stay distinct at 16px instead of closing into a cluster; static/favicon.svg draws the same simplified geometry on a 32×32 Event Horizon tile. When the wordmark is a link, hover moves the caret to Firewall Breach and indexes the asterisk 60° (one spoke) upward in Bright Stack Overglow. With full heat, an editor holding words the server has not confirmed holds the same lift and flare, then settles the asterisk back into the caret's apex when the save lands. A reduced-motion request keeps both colour changes and leaves the geometry still; reduced heat does not lift the spark at all.
  • Chip (.chip): a small machined plate — 1px container wall, 2px radius, 3px by 7px padding, mono at 12px, no fill, never a pill. It renders 22px tall.
  • Swatch (.swatch): an unrounded 9px square of a storyline or note-type accent; the library card draws its project mark at 10px. It is the only place a planning colour appears at full strength.
  • Count (tnum): the mono figure inside a chrome key, the outline or the status bar. It has no plate of its own: the key is the plate.

Panels and cards #

  • Panel (.panel): 1px Dark Packet wall in both modes, 6px radius, Null Pointer fill, inner highlight only. A container does not cast; it is part of the plane. The class sets no padding, so a panel that holds prose pads itself at 16px or 24px.
  • Outline row: Core Meltdown fill, 1px container wall, 5px radius, no offset. The row is the plane, not a card floating above it.
  • Library card: Null Pointer fill, 1px container wall, 4px radius, inner highlight and no offset. The title is Literata at 1.25rem, the subtitle takes secondary ink, and the blurb clips to three lines.
  • Plot card: Core Meltdown fill, 2px container wall, 2px radius, 7px by 8px padding, no offset. The heavier wall is what makes a 2px corner read at that size; hover moves the wall, never the card.
  • Dialog: a 2px-walled panel on a 65% black scrim, 4px radius and a 6px solid offset, with a surface-base header band under a 2px rule and one primary action in the foot. Below 40rem the details dialog becomes a bottom sheet so fields keep the width of a phone; the shortcut dialog tightens at 26rem.

The manuscript tree row #

Each node is a card on the plane rather than a line of text. Book and part labels use uppercase Cabin at 14px. Chapter and scene titles use the body face at 16px with 1.4 line height. Rows have a 44px minimum height, 4px gaps, and room to grow when titles wrap. Coarse pointers get a 52px minimum row. Expand controls use an 18px chevron, and scenes carry a 10px planning swatch. A 5px dot sits on every row's left edge, joined by the wire above and below it. The wire anchors on each row's centre, so a taller row moves nothing but itself.

The open scene takes --dr-surface-highlight and inset 3px 0 0 var(--dr-accent). One 32px actions key replaces the word count on hover or focus. The title keeps its width when the key appears. On a coarse pointer the key stays visible and takes a real 44px target, and the inline confirm's Delete and Keep grow real boxes rather than overlays, because the two keys sit closer together than 44px and centred overlays would overlap across their gap. The menu names each command and includes Move up and Move down, because HTML5 drag does not fire from touch. Each row remains one tab stop. Shift+F10 opens its menu, and Escape returns focus to the row. F2, Insert, Delete, M, and Alt+Arrow keep their direct commands.

The outline is one spine, wired top to bottom, and there is no second layout to switch into. A map of the book's shape is a different job from finding a scene, and it already has three homes at full width: the outline in the read-through, the plot grid, and the scene list. Keeping the rail linear is what lets a writer trust it at any window size.

Front and back matter #

A matter group is the book's endpaper, not a chapter in the story. Once a group holds a page, it draws a band on --dr-surface-base between two 2px rules, and its page rows sit flat inside it without the chapter card. The label and Add page keep their places in the band's header. An empty group keeps only that header, so an unused shelf stays quiet until the first page arrives. The 2px rules mark the section boundary: the structural-section use of a heavier rule, not a heavier container wall.

The stream ghost #

The previous and next scene sit above and below the active prose at 85% scale, unboxed, in Literata. Each preview has a mono kicker naming the chapter (gentle scroll ↑ or momentum scroll ↑), the scene title, a two-line excerpt, and a 2px pull track that fills with digital rust. The previews sit inside the scroll surface, so they travel with the words.

The preview takes no click or focus, and it is aria-hidden in full. It used to open the neighboring scene when pressed, but a screen reader could not see it and a keyboard could not reach it. Navigation lives in the scene head's Previous and Next keys, which name the scene they open, and in the wheel pull that crosses the threshold.

The surface slot #

A surface in the deck is a 21rem column that fills the height. Slot 0 carries no chrome of its own: it is simply the surface beside the prose. Slots to its right float a small Bring forward and × group at the bottom-right, on a 1px wall, so promotion is available exactly where the eye already is. The button names the surface it moves ("Bring Scene versions forward") rather than the internal id, and the verbs are the ones a writer already knows: on-hand is the deck's word for slot 0, not a word the page asks them to learn.

The dock pill #

The right-margin dock is a narrow vertical strip of six mono keys — Scene, Notes, Grid, Versions, Search, Progress — each with a 5px dot. The names are the header's names, so the dock is a second place to reach a surface rather than a second vocabulary for it. A dot turns Digital Rust when its surface is on-hand; a stacked surface takes a 1px control wall. Click promotes, Shift+click stacks, and the pill reports aria-pressed for either state. It is the one control that admits the plane is two-dimensional, and it hides entirely below 68rem where the deck becomes an overlay.

With a board open the dock takes a track of its own between the stage and the deck, so the plane reads rail · prose · selector · board. It used to stay at the stage's trailing edge, which put six buttons on top of a writer's own sentence; the prose column ends there, and the board's own arrival is what made the overlap visible. Opening a board therefore narrows the stage by the track, which is the same deal the deck already made with the prose.

Below 80rem the four columns stop leaving a readable measure, so the dock steps aside while a board is open and the plane returns to rail · prose · board. Nothing is lost that the width could support: the board's own header carries Bring forward and its close key, the chrome switches surfaces, and stacking a second board needs more room than 80rem gives.

A project has up to eight destinations. One menu in the same place on every page leads to them: Project. Write, Read-through, Feedback, Plot grid, Recovery and Export are identical destinations with different names on different pages. Sharing appears for the owner. Scene versions appears in the workspace while a scene is open. That is how the workspace header once reached twelve buttons.

The destination you are on reads as a key that is down — highlight fill, primary ink and a 2px bar of secondary ink on its leading edge — and so does the Scene versions item while its panel is open. Neither spends the warm accent; the accent's "where you are" is the open scene, not a page.

The menu keeps the five frequent controls in the writing cluster beside it (Scene, Notes, Find, Search, Progress) and one that leaves the chrome (Focus). Nothing else competes with the prose. Below 56rem the chrome has its own disclosure and the menu renders its items flat inside it.

The status bar #

A 30px strip of chrome sits at the foot of the writing surface. It takes --dr-surface-secondary in both modes, with a 1px container rule above it. The type is mono at 0.75rem in muted ink with tabular figures. A 6px square mark sits before the save state. The save state is on the left. On the right sit the proofreading and read aloud controls, the scene's word count, and the words added today against the goal. With no goal set the last readout says so (today 132 · no goal): a count with no denominator reads as a fraction that lost its other half. A deadline without a daily target is still a goal, so the readout shows the count alone; the deadline's own figures belong to the Progress panel. A dot in the container colour separates the last two. A failed save turns the mark and the save-state line to danger ink and adds Retry and Download. The bar is flat hardware, not a hot panel. The only hot surface in the product is the landing page's editor demonstration (HeatDemo), and it is a specimen rather than a workspace control.

Named Rules #

The Down Key Rule. A selected mode — a tab, a filter, a destination in a menu — reads as a key that is down: the elevated fill, the inner highlight, and where a leading edge exists, a bar of secondary ink. It never takes the warm accent. The accent's "where you are" is the open scene, not a choice in a menu.

Do's and Don'ts #

Do: #

  • Do let the prose carry the save state. Heat is the answer to "is it safe", and it arrives without the writer moving their eyes.
  • Do draw an ordinary control or container at 1px, and save 2px for a part too small to read at 1px, a recessed well that needs an edge, a layer that has left the plane, or a rule that states a condition.
  • Do give every raised control the full press cycle: bevel, solid offset, -2px/-2px on hover, 2px/2px and a collapsed shadow when pressed.
  • Do keep the accent to three jobs — unsaved words, the one primary action, where you are — and audit any fourth appearance.
  • Do derive the measure from the prose size (calc(var(--fw-prose-size) * 33)), never from ch, so the head, the measure and the status line stay on one edge.
  • Do keep peripheral chrome faded rather than hidden, and raise it on hover and focus-within.
  • Do measure a resting fade against its own background before shipping it. The floor is a token per zone and per mode, because Safe Mode's dark ink loses contrast faster than the dark theme's light ink. Every text a writer reads under a fade clears 4.5:1 in both modes.
  • Do prefer ink and a 1px rule over a thick coloured edge when a surface needs to say something.

Don't: #

  • Don't implement heat as a background highlight, an underline, or a badge beside the prose. The colour of the words is the signal.
  • Don't add a second celebration, a completion flourish, or a confetti state. The system has one authored moment: the cooling of saved words.
  • Don't use a blur shadow, a drop shadow with radius, a gradient on a wall, a backdrop blur, or a pill radius. Digital Rust has none of them.
  • Don't put a global scanline or grain overlay on the app body or on any interactive text surface. --dr-texture-overlay exists for decorative specimens; a paragraph is not one.
  • Don't put the warm accent on a filter, a hover fill, a selected chip, or a proofreading mark.
  • Don't let a peripheral widget's fade reach the prose, the tree's selected row, or body copy.
  • Don't treat --dr-border-color and --dr-border-color-container as interchangeable. A control's wall identifies the control; a container's wall stays recessed.
  • Don't hardcode a product name in a title or a wordmark: the instance name comes from src/lib/instance-name.ts.

Appendix: surface decisions #

These are the per-surface calls behind the system above. They are kept here because a later change should be measured against them, not because they are tokens.

Surfaces and their modes #

Surface Route Mode What success looks like
Landing / Persuade A visitor understands what this is and tries the editor.
Sign in / sign up /signin, /signup Operate One task, done without a second thought.
Library /library Operate A writer finds their project and resumes in one click.
Workspace /p/[id] Operate The prose is the page. Everything else is at the edge.
Plot grid /p/[id]/grid Operate A writer sees the shape of the book and fills a hole.
Reading and outline /p/[id]/read Operate A writer reads continuously, then judges the shape of the book.
Feedback /p/[id]/feedback Operate A writer works through what readers said, then opens the scene to act.
Sharing /p/[id]/share Operate An owner hands out access, copies a secret once, and revokes it.
Secret link /s/[id] Operate A guest reads or comments with no account, and knows what it allows.
Note types /p/[id]/types Operate A writer defines the shape a note starts from.
Search panel /p/[id] + search Operate A writer finds a name or a line, and lands in the scene.
Recovery /p/[id]/recovery Operate A writer previews deleted or earlier work, then restores it or copies it.
Account /account Operate A writer changes their own name, password or sessions.
Admin /admin Operate An admin changes two settings and leaves.
Admin accounts /admin/accounts Operate An admin adds a writer or ends access without locking anyone out.
Help /help Read A writer finds the key or the rule without leaving the app.

Operate surfaces get precision and restraint. Only the landing page is trying to persuade, and even there the persuasion is a working editor rather than a claim about one. Help is the one Read surface inside the app.

Feedback #

Two tabs, because reviewing and reading are different jobs. A reader who can comment but cannot open the workspace sees one list and no tabs, because a queue would hand them a key to a 404.

Responses is the default. The queue separates chapter responses from scene and passage responses without rendering the manuscript. Open scene leads to the workspace. Open chapter leads to its read-through. The queue keeps each quotation. Open and All are link filters, so a reload keeps the chosen list.

The actions name their outcome: Open scene, Resolve, Delete. Resolving takes the row out of the open list, so the queue's length is the answer to "how much is left". At zero the page says so and offers the resolved list.

Reading shows the manuscript at the existing measure, with a scene index and a 21rem feedback rail. Selecting words reveals Comment on passage. Scene feedback and Chapter feedback collect responses about the whole section.

An active passage response stays in a viewport-local panel beside the prose. On a phone, it becomes a nonmodal bottom sheet with a visible Close control. Show passage reveals the selected words above that sheet. Only one copy of the active response renders, so its controls and keyboard target stay unique.

The composer uses the same desktop rail. Below 64rem it becomes a modal sheet, because writing a response needs protected focus. Dismissal keeps the draft. A fresh selection can update a stale draft's context without replacing its message or suggestion. Resume alone never changes the passage target.

A suggestion takes the readout face under a rule, never a bordered band. Six bands under six responses turn the queue into a stripe pattern and compete with the message, which is what the writer reads first.

The tab bar is sticky. A writer who has scrolled into the last chapter must not have to climb back to change views.

Sharing and guest access #

Sharing is a page because access is a decision made rarely and read carefully, not a control pressed mid-sentence. It uses a 56rem column and separates Invite, Link, Members, Pending invitations and Secret links with 2px page-level rules; each section carries one action and states its outcome in words.

The secret is shown once. Copy is a button with a status line under it. If a browser refuses the clipboard, the page says so and selects the field instead of doing nothing. A permission names what the holder can do ("read and comment"), never a role name. Revocation stops future requests and says that it cannot recall a copy already saved.

A new link appears inside the section that made it, directly above the form, with its field selected. A confirmation rendered at the top of a 56rem page is a confirmation the writer never scrolls back to, and the one value they must copy before leaving would be the one thing above the fold.

The Label is optional, because it is a note to the owner rather than a decision to make while granting access; an empty one is stored as "Secret link" and the list still names the permission and the expiry. The sentence under the form answers the permission select in front of it: granting read-only access while a paragraph explains what editing does argues about a power nobody granted.

What the link opens chooses the link's scope: the whole project, or one book, chapter or scene. The consequence sentence names the scope in every permission ("The holder can edit the prose in this chapter…"), and the list of links carries the scope beside the permission, because a link to one chapter is a different grant from a link to the series. Share this book on the read-through opens Sharing with that scope already selected.

A secret link opens /s/[id]. The page names the scope first — a chapter or scene link titles itself with the scoped name, with a breadcrumb of its parents above the project title — then the permission and expiry before the manuscript index. Its 84rem frame holds the reading column and feedback rail. On narrow screens, responses follow the prose and the active passage response uses a bottom sheet. A link scoped to a scene offers no chapter feedback, because its holder cannot read the chapter around it. Guest names are unverified. Drafts and names stay scoped to that link in the browser tab.

The guest gets no project menu or help key. The page is noindex and sends no referrer. Direct prose editing stays separate from feedback and must save successfully before the reader leaves that mode.

The search panel #

The panel is an instrument for a writer who is mid-sentence, so it opens focused and is driven from the field: arrows move through the list, Tab switches between scenes and notes, Enter opens the scene.

The warm colour appears here only in roles it already owns. The selected row takes the same inset 3px 0 0 var(--dr-accent) the outline gives the open scene, because it answers the same question. Its fill is --dr-surface-highlight thinned toward the panel. A search result holds several lines of prose, so the full tree-row fill turns the column into a red block.

A matched word takes --dr-editor-find-match-highlight-bg, the palette's own find token: a warm tint with the word in ink and weight, never a colour block. The excerpt renders from segments, never a markup string, because a scene can contain a literal <mark>.

The find bar #

Find and replace floats over the top of the scene rather than taking a column, because reflowing the text you are about to search for moves the line you were reading. It covers the scene head, which says nothing a writer needs while looking for a word, and sits on --dr-surface-secondary — elevated is too close to the page below it for the bar to keep an edge.

Replace is folded away until asked for. ALL is the single primary action on the row; REPLACE is a normal key beside it.

Progress #

A goal answers a question the writer asks between sentences, so the answer sits in the status bar beside the scene's word count: today 132 / 500. The panel sets the target, the days off and the streak, and shows the same numbers larger.

The gauge is not a sparkline. One column is one day, all fourteen share a scale, and the day is a 2px tick under the column — which is why a day off leaves a gap. The target is a dashed line drawn in a text role, because it carries a value. The warm accent appears once, on today's tick, because today is where the writer is.

Proofreading #

Harper runs as WebAssembly in the browser. The proofreading check sends no manuscript to another service, and its 20 MB binary downloads only when a writer turns it on. A mark is an underline on the words, never a fill behind them: spelling takes --dr-danger-text and everything else --dr-info. Neither is warm.

Read aloud #

Read aloud is a text control in the status bar beside proofreading. It adds no surface or dock key, and the status control takes no warm accent. Its nonmodal popover is a 2px layer with a solid offset. It groups voices by on-device and online, and asks for confirmation before using an online voice when no matching on-device voice is reported. Playback covers the open scene only and never advances to the next scene. The control keeps its popover inside the viewport when the status bar wraps.

Recovery #

Recovery is a page because a restore needs room for the stored words and the decision. Three sections share one shape: a dated list beside a preview under one set of tabs. The current tab takes --dr-surface-elevated and the inner highlight, the way a key that is down reads; the selected row keeps the highlight fill and the inset bar. The version filters — All items, Notes, Plot cards — are filter keys that answer aria-current and grow to 44px on a coarse pointer, and they never take the warm accent: a filter is not where the writer is. Each section has exactly one primary action. A project version opens as a new project, so its preview also offers a copy.

Scene history #

The panel beside the prose holds the whole history of a scene, so it must not become a wall of timestamps: the newest fifty versions arrive with the workspace, and Show older versions asks for the page below while a readout says where the list stands. Named only narrows the list to bookmarks. Neither state takes the warm accent: a filter is not where the writer is. A preview states its scope above the changes — name or origin, when, word count, and what the scene holds now — because a diff otherwise answers "what changed" instead of "what would this put back". An origin names what kept the words: saved by you, before a restore, set aside after a conflict, before a structure change, or automatic. The panel also locks while a split or a merge replaces the scene, so a version is never taken of words in flight.

Note types #

Note types is a list beside an editor, the same list-beside-preview shape as Recovery. The accent is a 9px swatch shown at full strength. A row that moves under a keyboard gives no feedback, so reordering uses explicit move buttons and announces the new position. The selected type travels in the query string, so a reload or a shared address opens the same one.

Help #

Help is the app's one Read surface: a manuscript-measure column of body prose under the same chrome, a 1px rule above each section, and no cards. Its headings step from 1.75rem to 1.25rem to 1rem so a writer can scan for the command they need, and nothing on the page is a control except the chrome.

The first writing visit #

The writing tutorial belongs to the account, not a project or browser. Its five steps introduce the manuscript, formatting, autosave, planning beside the draft, and focus mode. The writer follows the real workspace without changing any manuscript text. The tutorial opens the manuscript drawer or Notes when a step needs them.

The tutorial is a nonmodal coach beside its current target. It carries a step count, Back, Next, and an explicit Skip tour. Typing and outside clicks leave it open. Escape skips the tutorial alone. A phone uses the available viewport without a backdrop that blocks the workspace. The panel uses the existing palette, walls, and solid offset. No separate animation or celebration competes with saved words.

Keyboard shortcuts offers Writing tutorial inside the workspace, so a writer can replay it without another permanent toolbar control. Start writing returns focus to the prose.

The tutorial keeps previous panels mounted. Skip restores the previous layout. On a phone, Start writing closes untouched panels to reveal the prose. Notes stays open if the writer edits it during the tutorial. Planning saves still guard every panel change.

The library card #

A card answers "which project is this" before "where was I". The title is the page's h2 for that project, so a writer can move between projects by heading instead of by list; the link around it is the card's door. The colour square beside the title is the project's own mark and carries no status; it takes a rust-ramp stop by default and one of the six failure accents when the writer picks one. The subtitle belongs to the title, so it takes secondary ink; the description is orientation, so it sits a step quieter and clips to three lines, which keeps a row of cards the same height.

The card carries one control: More. The title opens the project and the resume line says where the writer stopped, so everything else — Details, Feedback, Sharing, Recovery, Export and Delete — is a menu item. The workspace header was cut to one Project menu because it once held twelve buttons; the card reintroduced the same wall at the one place where a slip costs a novel, with Delete a few pixels right of Export. A reader keeps Feedback inline, because a menu that hides a single item hides it from the only person it serves.

Delete this project closes the menu and opens the confirm in the card's own action row, where the trigger was. The confirm names the safety net: the project moves to Deleted projects and can be restored from there. The rail takes focus when it appears, and carries role="group" with its own label, because a confirmation that nothing announces is a confirmation a screen reader never hears.

Details opens the title page as a dialog rather than a page, because those values are read on the card and nowhere else.

The plot grid #

A matrix of storylines against scenes, or against chapters. The first column and the first row stay pinned, so a writer scrolling across the book keeps the thread they are following and the scene they are in. One cell is one beat: a card with a title and a note, or a target that opens an empty card. The cell is one snippet, rendered by both orientations, so a card's fields and actions cannot drift between them.

Below 40rem the matrix is transposed rather than shrunk. The book's sequence runs down the page — every scene, numbered, under its chapter — and the storylines run across as columns that scroll sideways. The other way round, a 12rem column beside a 12.5rem row head left exactly one scene visible on a phone and no shape at all. Two threads stay readable beside the scene title, every cell keeps its add target, and the pinned row head keeps the writer's place. A phone can still fill a hole; it just reads the book first.

The landing demonstration #

The signed-out homepage uses an open split layout, without a card around the introduction. A narrow headline column sits beside the working editor. A 1px container rule separates them. Below 60rem, the editor follows the introduction and the rule becomes horizontal.

Product details lead with what writers can do: build a manuscript, plan beside the prose, revise, and export. They form a two-column list under “A home for your whole novel”. Hosting details sit in a narrower sidebar behind a 1px container rule. The sidebar links to the source and installation guide, without a command block or a second sign-up action. Below 60rem, hosting follows the product details and its rule becomes horizontal. Below 42rem, the feature list becomes one column.

The landing page's proof is a specimen, not a mock: a real editable scene with the real save machine behind it, writing to nothing. Its status strip is the product's one hot panel, Bricked Board in both modes. The sentence types its last clause once on arrival, and the panel carries no line under it: the status strip and the field's aria-label are what say the scene is editable.

Import and export #

Export and Delete sit in each project card's More menu. Import sits beside New project in the library header, because it is about the library. New project keeps the accent and Import is a ghost button: starting a draft is the common action, arriving with one is the occasional one.

The import control is a dashed well, not a card — darker than its panel, no rise — so it reads as a target. The confirmation after an import is a status line with the editor's square success mark, not a bordered callout, and its two links are words inside the sentence. The project card afterwards carries the report and the file it came from on one mono line: a fact about the card, so it takes the muted readout, with underlined links because nothing else in the row says the words are pressable.

The read-through answers a scope, not only the whole project: one book, one chapter, or one scene, reached from the outline or from a scene's Read alone key. A scope bar states what is showing and links one step outward — the scene's chapter, the chapter's book, the project — so a reader climbs back at their own pace. A writer reading a scope can export it: an Export key opens a popover offering the Word manuscript and the EPUB of the live words in that scope only, a 2px-walled layer with the 4px offset that marks a thing off the plane. The owner sees Share this noun — book, chapter or scene — beside it, which opens Sharing with that scope selected. A scene keeps its title inside front and back matter when it is the scope, because a lone page still needs its name.

/p/[id]/read also serves printing:

  • Chrome removal: under @media print, chrome, navigation, outline toggles and readouts are display: none !important.
  • Pagination: each chapter starts on a fresh page.
  • Typography and measure: printed prose uses the body face (Literata by default, or Lexend when the account chose it) at 38rem, 11pt, 1.6 line height, 1.5em paragraph indents and 1-inch margins.
  • Print is paper, not a mode. The print rules set ink and font size on the prose, the part heading and the chapter heading themselves, and give the manuscript its own font size, rather than leaving them to inherit from a container. They reset the frame, the panels and the Write keys. Ink is plain black on unpainted paper: the palette governs the screen, and a writer's colour mode must not change the page that comes out of the printer. A change here is verified by rendering both modes, not by reading @media print.
  • Page guards: widows and orphans are constrained to 3 lines.
  • Heading depth follows the tree: a chapter under a part is an h4, a chapter under a book is an h3, and its scenes sit one level below, so a book without parts never jumps from h2 to h4. A section is marked by a tag beside its title, not a kicker above it.

Motion #

One authored moment: the cooling of saved words, and its inverse on a save in flight. The wordmark's spark rides the same state: it rises and flares while words are unsaved and settles into the caret's apex when they set. Everything else is the 150ms press cycle and 250ms for a pane to change state. The stream previews add a 120ms scale and a 160ms opacity change as pull builds. prefers-reduced-motion cuts every transition except the two the system exists for — the cooling of saved words and the wordmark's spark — so the colour answers keep their timing while spatial travel stops; reduced heat leaves the spark at rest. The interface stays understood in both cases.

Known limitations #

  • A board costs the stage its dock track. Above 80rem an open board gives the stage up to 6.5rem before the deck's own 21rem, so a scene title may take a second line at a width where it fitted on one; below 80rem the dock hides instead. The trade is deliberate: chrome sits beside the words, never on them.
  • The pointer fade has a floor per mode. The dark theme rests secondary ink at 0.62 and Safe Mode at 0.8, which measure 5.9:1 and 7.7:1 against their own pages. The scene's position caption takes secondary ink rather than the heading role, because the heading red lands on the AA floor at 12px under the fade. The stream previews rest at 0.52 and are aria-hidden decoration, so the floor is a cue rather than a reading size; that number does not transfer to a button.
  • --swatch-color is the one custom property with no declaration. It is set inline per swatch and falls back to --dr-info, which is the intended pattern rather than a missing token.