Admin UX review and design system

Date: 2026-11-05. Scope: packages/admin (the React admin at /admin). Goal set by the product owner: review the admin screens of enterprise Drupal, WordPress and the leading SaaS/headless platforms, and make Spillway's admin look and feel enterprise, stay accessible, and lead on user experience.

This document has four parts: (1) what the other platforms do, (2) a critique of the Spillway admin before this round, (3) Spillway's admin design principles and the concrete spec that was implemented, (4) the accessibility audit and verification results.

1. Platform review

Sources were read on 2026-11-05; vendor documentation and review-site snippets are marked as such. Where a claim could not be verified it is flagged.

Drupal: Claro, Gin, Navigation, Drupal CMS

• Navigation model. Drupal core committed the Navigation module as the default admin navigation in place of Toolbar (March 2026): a collapsible vertical sidebar with submenu drawers for deeper levels and a top bar built with the Experience Builder, Gin and core teams (The Drop Times, DrupalCon Atlanta session, Drupal CMS track). Gin offers Sidebar, Vertical toolbar (default), Horizontal and Legacy layouts (Gin settings).
• Density, typography, spacing. Claro uses a 16 px base, system fonts, a small modular scale, 14 px form labels / 16 px values, tall table rows and smaller buttons for tables, and a neutral palette with one vivid blue for primary actions (Claro design system). It is deliberately airy, which editors describe as comfortable but low-density.
• Tables and lists. Views-driven lists with exposed filters, bulk actions (VBO) and sticky table headers; column choice is a site-builder task, not an editor affordance.
• Content editor. Gin keeps Save, Preview and the published state in a sticky top bar; secondary actions fold into an overflow menu; the "meta" sidebar (author, URL alias, menu, revisions) sits on the right and can be collapsed; a toggle shows or hides field descriptions (Gin docs, Drupal.org Gin).
• Status and workflow. Content Moderation states appear as a select in the sidebar; the Moderation Dashboard contrib module gives per-user blocks for "needs review" and "my drafts" (moderation_dashboard).
• Dashboard. Drupal CMS ships a Dashboard module built on Layout Builder (Varbase documents the same pattern) with blocks for recent content, moderation and shortcuts (Varbase dashboards).
• Search / command palette. Coffee (contrib) is the de-facto command palette (Alt+D); it is not in core.
• Dark mode. Gin: light, dark and auto (follows the OS) (Gin settings).
• Accessibility posture. Claro states WCAG 2.1 AA conformance, consistent focus areas, contrast-checked text, high-contrast mode testing and 24×24 px icon targets (Claro accessibility). Gin carries an open accessibility meta issue from the accessibility team's audit, including a dark-mode layout defect and the note that automated tools cannot check contrast of semi-transparent colours (Gin a11y meta).
• Praise / complaints. Praised: Gin's focus on the editing form, sticky actions, accent and focus colour settings (ImageX). Complaints: regulated sites still default to Claro because contrib themes need extra review (Vardot); the admin remains page-reload heavy and visually dated next to SaaS tools.

WordPress 7.0 ("Armstrong", May 2026)

• First admin redesign since 2013: the "Modern" palette becomes the default, a ⌘K command palette sits in the top bar, screen changes use the View Transitions API, and DataViews replaces WP_List_Table on Posts, Pages and Media (AlternativeTo, Yoast, WPBrigade).
• DataViews brings table/grid/list layouts, saved filters, column visibility and bulk actions to every list; this is the closest open-source benchmark for Spillway's DataTable.
• The block editor adds viewport visibility controls, per-block CSS, Breadcrumbs and Icons blocks and a visual revision diff with a slider (green additions, yellow changes, red deletions) (Yoast).
• Complaints: the admin still keeps the 2013 information architecture (left menu of everything), plugin screens do not follow the new palette, and real-time collaboration slipped to 7.1 (Raidboxes).

Contentful

• Navigation: top bar (Space, Content, Media, Content model, Apps) with a left sidebar inside Content holding private and shared saved views grouped in folders; admins can customise the sidebar per role (Saved views, Content tab).
• Entry editor: fields in the centre, a right sidebar with status/publish, versions (past published versions now listed in the sidebar for comparison), links, translations; the sidebar is configurable per content type (changelog, custom sidebar).
• Praise: fast editor onboarding, saved views. Complaints (G2/Capterra, review sites so treat as anecdotal): "confusing at first", hard to find a page or paragraph on large sites, rigid form-based editing with no front-end context, drafts that never get published, data model "optimised for Contentful's internal reasons" (G2, Capterra).

Sanity Studio

• Structure tool: configurable pane-based navigation (lists → document) built with the Structure Builder; document lists cap at 2000 items (Structure tool).
• Theme: scheme light/dark/system with an Appearance menu; usePrefersDark wraps prefers-color-scheme (StudioProps, usePrefersDark).
• Accessibility: Studio is built on Sanity UI, a component library whose stated aim is accessibility and consistency; no published conformance claim was found (Sanity Studio).
• Praise: speed, real-time, developer control. Complaints: everything is code-configured, marketers depend on developers for list views and workflows.

Storyblok

• Visual editor with live preview and reusable components is the headline feature; marketers praise that non-technical users edit without engineers (G2, Gartner).
• Complaints: pricing, setup still needs developers, limited pipeline visibility and migration pain, weak export (Gartner review Sept 2025).

Sitecore XM Cloud (Pages)

• Pages is a WYSIWYG, auto-saving editor; authors praise the visual editing; Forrester's vendor-commissioned TEI claims up to 60 % faster page creation (TrustRadius, Forrester TEI).
• Complaints: features from XP/XM missing in the new authoring experience, documentation gaps, limited mobile experience (G2). One university page says XM Cloud was renamed SitecoreAI on 10 Nov 2025 (single source).

Adobe Experience Manager Sites

• Universal Editor: in-context WYSIWYG for pages and content fragments; Content Fragments Console: a dense tabular view that maximises fragments per screen, with multi-select actions limited to what applies to all selected items (Universal Editor, CF console).
• Complaints: navigation entries missing between environments (KB 39866), editing fragments without leaving the page still needs setup (community thread).

Payload 4 (beta)

• Redesigned admin on a new design system with unified tokens for colour, typography, spacing, radius and elevation; collapsible sidebar open by default; sidebar tabs for folders and tags; better table cells and bulk actions; query presets to save and share filters, columns and sort; improved focus states and an enhanced-contrast mode; Sass removed (Payload 4 beta, List view docs, Admin overview). A June 2026 tracker still lists 4.0 as not stable.

Directus

• Collection pages have layouts (table, cards, calendar, map); presets store sort, filter and layout per user/role/global, and a named preset becomes a bookmark; defaults resolve user → role → global (Presets & bookmarks, Layouts).

Webflow

• Praise: visual building without code. Complaints: steep learning curve and an overwhelming interface for new adopters, CMS limits (60 fields, 10 reference fields), designer performance on large projects, tangled pricing (G2, Capterra, TrustRadius).

HubSpot Content Hub

• Praise: approachable drag-and-drop editor, CRM integration. Complaints: templates need HubL, weak blog editor, limited version control below Enterprise, generic-looking output, and "frequent updates can be overwhelming" (interface churn) (Capterra, TrustRadius, G2).

Linear and Notion (the density and polish benchmark)

• Linear: Cmd+K as the universal entry point with fuzzy search; mnemonic single-key shortcuts taught through tooltips; high density with low clutter through consistent spacing, muted colour and progressive disclosure; keyboard-first on desktop, with mobile explicitly secondary (925 Studios, buildmvpfast, DEV).
• Notion: a blank default state with power behind the keyboard, an understated type scale (40/30/24/20/16) and 16 px body at 1.5 line height, a restrained palette where each colour has a semantic role (Notion shortcuts, design study).

What marketers consistently praise and complain about

2. Critique of the Spillway admin before this round

Screenshots of the previous build are in docs/screenshots/before/. The design:design-critique framework (first impression, usability, hierarchy, consistency, accessibility) was applied to the dashboard, content list, entity editor, page builder, settings, media and the mobile dashboard.

Overall impression

Clean and quiet, but generic: every sidebar entry rendered as a blue hyperlink, no icons, no grouping affordance beyond a label, no global search, and a dashboard that led with a counts table rather than what the signed-in person should do next. It read as a competent internal tool, not an enterprise product.

Usability

Visual hierarchy

What drew the eye first was the sidebar (a column of blue links), not the page title or the primary action. Reading flow on the dashboard went counts table → tasks → traffic zeros → review item; the thing a reviewer needs (the review queue) came fourth. Cards had equal weight regardless of importance.

Consistency

Accessibility (before)

Contrast: --text-faint (#9a9aa3) on white was 2.9:1, used for timestamps and group labels (fail). Focus rings were present. Target sizes: several 20 px controls. Touch: the off-canvas sidebar existed but the topbar had a text "Menu" button only. Screen reader: tables had captions and labelled checkboxes (good); icon-only controls were few.

3. Spillway admin design principles

1. Lead with the work, not the structure. The dashboard greets the person and shows what needs doing (review, scheduled, drafts). Lists lead with the primary action. The sidebar is grouped by job (Content, Marketing, Structure, System), not by module.
2. Dense, not cramped. 14 px body, 13 px in tables, 34 px controls, 4 px spacing scale. Density is a user choice on every table (compact/normal/comfortable) and is remembered.
3. One header, one primary action. Every screen has a trail, a title, a one-line description and actions aligned right with the primary action last. Editors keep actions in a sticky bar so Save is never off-screen.
4. Keyboard first, pointer complete. Ctrl/Cmd+K reaches any screen or action; arrow keys move through rows and sidebar links; every dialog traps focus and returns it. Nothing requires dragging (the builder's drag and drop has a click path through the component list).
5. State is never colour alone. Status badges carry a dot and a label; sort direction has an arrow and aria-sort; unsaved state has a dot and text.
6. Two themes, one contract. Every colour is a semantic token with a light and dark value; both pass WCAG AA for the pairs they are used in (table in section 4). prefers-color-scheme wins until the person chooses.
7. Nothing moves unless asked. All motion is 120–180 ms and switched off under prefers-reduced-motion.
8. Preferences are local and cheap. Column visibility, density, sidebar state, media layout and theme live in localStorage per browser; nothing about them needs a server round trip.

4. The spec (as implemented)

Design tokens (src/styles.css)

Type scale (px): 11 caption · 12 meta · 13 table/body-small · 14 body · 16 lead/h3 · 18 h2 · 22 h1 · 28 display. Line height 1.5 (1.25 for headings). Font: Inter if installed, then the system stack; monospace for keys, paths and code. No web font is downloaded (privacy and offline installs).

Spacing (4 px base): 4, 8, 12, 16, 20, 24, 32, 40, 48 (--sp-1 … --sp-12). Page gutter 28 px (16 under 900 px, 12 under 420 px).

Radii: 4 (controls, chips), 6 (buttons, inputs, menu items), 10 (cards, tables), 14 (dialogs, palette), 999 (badges, avatars).

Elevation: --shadow-1 (cards: 1 px ambient + hairline), --shadow-2 (menus, popovers, sticky bars), --shadow-3 (dialogs, toasts, palette). Dark values use heavier black and a faint white edge.

Layout: sidebar 248 px (60 px collapsed), top bar 52 px, content max-width 1280 px (1360 for editors).

Semantic colours and their measured contrast ratios (WCAG 2.x relative luminance; computed from the tokens by scratchpad/contrast.mjs on 2026-11-05):

Light

Dark

--border and --border-strong are decorative dividers (cards, table rows) with no contrast requirement; inputs use --border-input. Theme selection: prefers-color-scheme by default; html[data-theme="light|dark"] overrides it; the choice is stored under spillway.admin.theme and applied before first paint (initTheme() in main.tsx). The page builder maps the tokens onto Puck's --puck-color-* variables so the builder follows the theme.

Layout

• Sidebar (shell/Shell.tsx): grouped sections with icons (Dashboard / Review queue with a waiting count / Analytics; Content: one entry per content type, Media, Collections, Shared blocks, Vocabularies, Alerts; Marketing; Structure; System). Collapsible to a 60 px icon rail with CSS tooltips (hover and keyboard focus) and aria-labels; the state is remembered (spillway.admin.sidebar) and toggled by the top-bar button, the footer button or [. Arrow keys, Home and End move between links. Under 900 px it becomes an off-canvas drawer with a scrim and a Menu button; it works down to 360 px.
• Top bar: sidebar toggle, site switcher (menu with the current site, View site and a Fleet placeholder), global search field (opens the palette, shows ⌘K), View site, Notifications (review-queue count; placeholder for a feed), account menu (theme radio group, API tokens, preferences, shortcuts, log out).
• Breadcrumbs: screens declare a trail through PageHeader crumbs or useBreadcrumbs(); otherwise the shell derives Dashboard › Group › Screen from the sidebar. The trail respects the unsaved-changes guard.
• Page header (components/PageHeader.tsx): eyebrow, title, meta badges, description, actions (primary last), optional tabs; level="sub" for section headers inside tabbed screens.
• Right rail: editors keep a 320 px sticky rail (URL, Checks, Comments, Revisions, Details) that stacks under the form below 900 px.
• Skip links: "Skip to content" and "Skip to navigation".

Components

• DataTable (components/DataTable.tsx; Table is the compatibility export): sortable columns (aria-sort, client sort or controlled server sort, used server-side on the content list), a View menu with density (compact/normal/comfortable) and a column chooser (menuitemcheckbox), per-table persistence (spillway.table.<key>), sticky header, row selection with an indeterminate select-all, expandable rows (submissions), skeleton rows while loading, icon + title + description + action empty states, a pagination footer with "Showing x–y of n", ArrowUp/Down/Home/End between rows and Enter/Space to open, and a card layout under 720 px driven by data-label. Adopted by: content lists, media (list view), form submissions, redirects, collections, users, review queue and scheduled, modules, experiments, audiences, vocabularies, menus, shared blocks, alerts, kits (list view), content types and the dashboard's recent list.
• Form layout (components/Form.tsx): FormSection (titled, described, aria-labelledby), FormGrid, FormActions (sticky bottom bar with a live "Unsaved changes / Saving… / All changes saved" status and the actions, primary last). Adopted by the site settings tab, the content-type editor, the form editor and the collection editor; the entity editor keeps its sticky top action bar (status, saved state, Preview, Schedule, Unpublish, Reject, Submit, Save draft, Publish).
• Status badges (components/Badge.tsx): draft/review/published/archived plus neutral/info/success/warning/danger tones, each with a dot.
• Empty, loading and error states (components/EmptyState.tsx): EmptyState with icon and heading level, Skeleton/SkeletonCard (shimmer, hidden from AT, off under reduced motion), LoadingState, ErrorState with retry.
• Toasts (components/Toast.tsx): polite live region; success/info are status, errors are alert; icon, left accent, dismiss button.
• Dialogs (components/Modal.tsx): rendered in a portal, the app root is inert while any dialog is open (nested dialogs share a counter), focus trapped and restored, Escape closes, aria-labelledby/aria-describedby.
• Command palette (shell/CommandPalette.tsx): Ctrl/Cmd+K or /; groups Content (FTS search over published and, with content.view_drafts, draft content), Go to (every permitted screen) and Actions (New <type> with content.create, Upload media with media.upload, Invite a user with users.manage, theme, sidebar, View site, API tokens, preferences, shortcuts, log out); combobox + listbox semantics with aria-activedescendant; fuzzy ranking; the unsaved guard applies to navigation.
• Icons (components/icons.tsx): 68 hand-drawn 24 px outline icons, 1.75 px stroke, decorative by default, title for named use.
• Keyboard shortcuts: Ctrl/Cmd+K palette, / search, ? help dialog, [ sidebar, arrows in lists and the sidebar, Esc everywhere.

Interaction rules

• Unsaved guard: editors set a dirty flag; sidebar links, breadcrumbs, the palette and beforeunload ask before leaving. (Still window.confirm; a styled dialog needs an async guard, see "Not finished".)
• Optimistic updates: list mutations (toggle, delete, rename) update the local list immediately and reconcile with the response; bulk actions reload.
• Loading: skeletons for tables and dashboard cards; spinners only on buttons that are busy (aria-busy).
• Density: a per-table preference, never global.
• Motion: 120–180 ms ease-out for menus, dialogs, toasts; none under reduced motion.

Accessibility requirements (WCAG 2.2 AA, ATAG 2.0 Part A)

5. Audit and verification

Run on 2026-11-05 against the built admin with Playwright (scratchpad/audit.mjs). axe-core is not available offline in this environment, so the audit is checklist-driven.

Route crawl: all 40 routes from App.tsx (lists, editors with real ids, every settings tab, the page builder, the 404) loaded with 0 page errors and 0 console errors (apart from expected 4xx responses the UI handles).

Per route (same result on every route unless noted): one h1; 0 unnamed buttons/links; 0 unlabelled inputs; tabbing through the first 20 focusable elements: 0 without a visible ring, 0 obscured; no positive tabindex; no horizontal scroll. The page builder is excluded from tabbing (Puck owns it) and reports one unlabelled control inside Puck's own UI (its viewport zoom select).

Scenarios:

Build and tests: pnpm --filter @spillway-cms/admin typecheck and build pass; node e2e/smoke.mjs 14/15 (the known drag-and-drop limitation); node e2e/smoke-phase2.mjs 34/34. The smoke scripts were not changed: every label and button name they rely on was kept.

6. What changed (files)

• src/styles.css: rewritten design system (tokens, light/dark, shell, components, screens, responsive, print).
• src/components/icons.tsx (new), DataTable.tsx (new; Table.tsx re-exports it), Form.tsx (new), PageHeader.tsx (trail, eyebrow, meta, tabs, sub level), Button.tsx (icons, icon-only), Badge.tsx (dots, tones), EmptyState.tsx (icons, skeletons, heading level), Modal.tsx (portal, inert, focus trap), Toast.tsx (icons, roles).
• src/shell/Shell.tsx (rewritten), shell/CommandPalette.tsx (new), shell/breadcrumbs.tsx (new), hooks/useTheme.ts (new), lib/inert.ts (new), main.tsx (theme init).
• Screens: Dashboard (rewritten), ContentList (server-side sort, selection, saved columns), MediaScreen (grid/list, empty state), SettingsScreen (tabs under title, sections, sticky save), SubmissionsScreen (expandable DataTable), every list screen (DataTable features), TypeEditor/FormEditor/CollectionEditor (sections + sticky actions + trail), EntityEditor/EntityActions/EntityRail/LockBanner (trail, icons, unsaved dot, h1), LayoutEditor (custom Puck header), Login/Setup (brand), NotFound.
• Two pre-existing type errors from shared-contract additions (workstream.merged, sites.manage) were fixed in the admin label maps.
• README.md screenshots table; docs/screenshots/ replaced, previous set kept in docs/screenshots/before/.

7. Not finished / follow-ups

• Audit-log activity feed. The dashboard's "Recent activity" derives verbs from entity timestamps (created / updated / submitted / published) because core exposes no GET /api/audit. When core adds one, replace activityVerb() in Dashboard.tsx with the feed.
• Styled unsaved-changes dialog. The guard is still window.confirm; replacing it needs an async confirmLeave and a router blocker.
• Saved filters. Column and density preferences are saved per table; named saved views (Contentful/Directus style) need a server-side store so they can be shared per role.
• Settings tabs other than Site, Languages, Media and Forms keep their Save button in the tab's sub-header rather than a sticky bar (Theme, Brand, AI, Notifications, Integrations, Sign-in); the content area already uses cards. Converting them is mechanical (Media and Forms were converted in the Phase 4 pass below).
• Notifications feed. Done in Phase 3: the bell polls the review queue, the user's returned drafts and the items scheduled for today (shell/useNotifications.ts); an audit-backed feed can replace the polling when core exposes one.
• Site switcher. Done in Phase 3: shell/SiteSwitcher.tsx lists GET /api/me/sites, stores the choice and sends X-Spillway-Site on every call; the workstream switcher and banner sit beside it.
• Axe. Run @axe-core/playwright in CI once the package is available; until then e2e/a11y-crawl.mjs (section 8) is the gate.

8. Phase 4 accessibility crawl (e2e/a11y-crawl.mjs)

Date: 2026-11-05, over the screens added in Phase 4. The Phase 3 audit lived in a scratch script; this one ships in the repo and runs against the built server: pnpm build && node e2e/a11y-crawl.mjs. It exits non-zero on any serious or critical finding and prints every finding as a table (route, element, WCAG criterion, severity, check, detail). A11Y_QUICK=1 runs light/1280 only, A11Y_ONLY=<regex> picks states, A11Y_COMBOS=light:390,dark:1280 picks theme and width, A11Y_OUT=<file> writes JSON, A11Y_DEBUG=1 adds computed styles and screenshots of obscured controls.

How it runs. The script starts the built app in its own process (packages/core/dist/app.js plus the ticker) with REGISTRY_HOST=1 and SPILLWAY_ALLOW_PRIVATE_URLS=1, and points the DAM connector at the in-process Cloudinary fake from packages/core/src/test/fake-dam.ts (Node 22.18+ strips the types; when that import fails the two DAM states are skipped and the log says so). It then seeds through the API: three languages and the manual XLIFF provider, a translation job over two pages, a Cloudinary DAM, a two-step contact form with a condition and a public page that renders it, a disabled Okta provider (so the SSO dialog shows the SCIM section), a saved view on the page list, four registry packages (the trusted one waits in the review queue) and an advisory, and an import of the fixture site (e2e/fixtures/import-site) crawled, classified, approved, converted, themed and landed.

States (36, each in light and dark theme at 1280 and 390 px): Import list, New import, the five wizard steps, the cancel dialog and the Compare drawer; Registry review queue, its drawer and approve dialog, Packages with the Deprecate and Add advisory dialogs, Publishers, Namespaces, Advisories, Publisher; Translations, the Send to translation dialog (with a search typed) and a job report; Settings: Media (DAM form), Forms (CAPTCHA with Turnstile selected), Languages (TMS section), the Sign-in provider dialog with the SCIM section; the media picker's From Cloudinary tab and the library's DAM dialog; the content list, the saved Views menu and the Save view dialog; the unsaved-changes dialog (title edited, then a guarded sidebar link, through the drawer at 390 px); the form builder with a field's condition editor open and the steps editor; Kits and the install plan modal; the public page with the Form block.

Checks (axe-core is not a dependency, so they are written in the script):

Findings and fixes (first run, before the fixes: 28 findings at light/1280, 52 over the four combos; all fixed in packages/admin and packages/blocks):

Not changed: the 18 px row checkboxes (24 px row pitch, no adjacent target) and inline links in table cells pass under the 2.5.8 exceptions; Tabs keeps aria-current="page" on in-page tab buttons; the stepper's done state in the public form is visual only (the step title and count are read).

Result after the fixes: 0 findings over 36 states × 4 combos (node e2e/a11y-crawl.mjs exits 0), 0 page errors. Screenshots at 2× in docs/screenshots/: import-wizard.png, translations.png, dam-picker.png, saved-views.png, unsaved-dialog.png.

Known limits. The fake DAM's thumbnails point at res.cloudinary.com, so the picker shows alt text instead of images in the crawl. Focus scrolling: besides scroll-padding on html, FormActions listens for focusin and scrolls a control out from under the sticky bar, because browsers only scroll a focused control into the viewport, not clear of overlays.

9. Page builder accessibility, Puck's interface included

Date: 2026-11-07. Until then the crawl audited only the page builder's Style field (a region, at 1280 px), because the rest of the builder is Puck's own interface. The builder, builder-outline and builder-style-field states now audit the whole builder in light and dark at 1280 and 390 px, with 80 tab stops each, and the crawl gained a check for anything that shows a pointer cursor but is not a control the keyboard can reach (2.1.1, serious). A one-off axe-core 4.10.2 run over the same states (WCAG 2.2 A and AA plus best practices) found the last four rows. Every fix stays outside Puck: overrides first, CSS scoped under .builder-screen next, and attributes set after mount (screens/content/puckA11y.ts) only where no override or prop reaches. The issue text for Puck is upstream/puck-accessibility.md.

Findings and fixes (first run: 51 findings over the two states and four combos, 6 critical, 39 serious, 6 moderate):

Not fixed: adding and moving blocks needs a pointer, because Puck registers no keyboard sensor for dragging, and the Outline row is a draggable role="button" around the row's buttons (axe nested-interactive). Both are Puck's to fix; a keyboard path of our own is an open decision.

390 px. The builder works in Puck's phone layout instead of showing a "needs a wider screen" notice: once the header stopped setting the layout's width, Puck's own phone layout (canvas on top, the rail at the bottom opening Blocks, Outline and Fields as a panel) passes every check.

Result after the fixes: 0 findings in the three builder states over the four combos, and none in the rest of the crawl; the axe run reports only nested-interactive on Outline rows. e2e/smoke.mjs clicks the builder's Publish by its role now. Screenshot: docs/screenshots/page-builder-dark.png (dark mode, a Hero selected, 2×).

Spillway 0.1.0 · Edit this page on GitHub