Style
Terminal mono
A dark screen, one monospaced face and a single cursor green; content is set like command output, with prompts, aligned columns and plain rules instead of cards.
See it live
Example: landing page of a command-line backup tool for small studios for Burrowkeep, a fictional brand made up for this explorer. Switch the width to see the style on a phone, a tablet and a desktop screen.
Backups for small studios, from the command line
Your work, kept twice. Every hour. Without asking.
Burrowkeep is one small command that copies your studio's files somewhere safe, seals them with your own key and gets out of the way. Install it once; restore anything from the last ninety days in a single line.
studio $burrow keep ~/work --to cellar
scanning 4 folders, 3,290 files ...
- projects/2,41838.2 GBkept
- type-library/6111.9 GBkept
- invoices/20496 MBkept
- scratch/574.1 GBskipped
done 44.2 GB sealed and kept in 3m 12s
studio $
Four commands. That is the whole tool.
- burrow keep
- Copies every changed file to a second place you choose, a spare drive or a storage bucket, in the background while you work.
- burrow restore
- Brings back one file, one folder or a whole machine as it was at any hour in the last ninety days.
- burrow seal
- Locks each copy with a key only your studio holds. We could not read your files if we wanted to.
- burrow report
- Sends one short line each morning: what was kept, what was skipped and why. No dashboard to check.
Pricing, per studio
| plan | price | includes |
|---|---|---|
| Solo | £4 / month | 1 machine, 30 days of history |
| Studio | £12 / month | Up to 6 machines, 90 days of history, shared restore |
| Workshop | £30 / month | Up to 20 machines, a year of history, two sealed keys |
note Storage is yours: a spare drive or any bucket you already pay for. We never hold your files.
Start a 30-day trialChangelog
v3.2.014 Oct
- +burrow restore --at accepts plain words: "yesterday 6pm".
- ~Morning reports now list skipped folders first.
v3.1.429 Sep
- ~Large video folders are kept 40% faster on slow studio links.
v3.1.002 Sep
- +A second sealed key for studios with two owners.
- !Copies made before 2.0 must be re-sealed once; burrow seal --renew does it.
Copy the idea
Take the style with you as a brief for a person, as instructions for an AI assistant, or as design tokens. It describes the idea and the rules — never the example's code.
The recipe
When to use it and the principles behind it. The palette, type, spacing and the do's and don'ts are drawn below; the brief you copy carries all ten sections.
Use it when
- Developer tools, command-line products and APIs whose users live in a terminal
- Changelogs, status pages and documentation that should read like plain facts
- Brands that want to feel exact, quiet and a little underground
Avoid it when
- The audience is not technical and would read the prompts as noise
- The page needs photographs, warmth or a friendly, rounded feel
- Long reading text where a proportional face would be kinder
Principles
- One monospaced typeface for everything; size and weight carry the hierarchy, never a second family
- A near-black ground with pale green-white text, like a screen in a dim room
- Content reads as a session: a prompt, a command, then its output
- Lists line up in fixed-width columns of keys and values, not boxes or tiles
- Plain 1 px rules and dashed dividers separate sections; no cards, no shadows
- One bright green for prompts, actions and the cursor; amber only for warnings and small notes
Imagery and motion
- Imagery: No photos or illustrations: prompts, command output, aligned tables and a blinking block cursor are the pictures.
- Motion: At most a blinking cursor and lines that appear as if typed; nothing slides or bounces, and all of it stops for reduced motion.
Palette
- Dim screenbackground
#0b100d - Raised linesurface
#121a15 - Phosphor whitetext
#d6f5de - Faded outputmuted
#8fb39a - Cursor greenaccent
#3ddc84 - Warning amberaccent-2
#f2c14e - Grid ruleborder
#2a3b30
Text on background: 16.43:1 — passes AA
Type
The quick brown fox jumps over the lazy dog
Bold, set no bigger than it needs to be; headings read like section banners
The quick brown fox jumps over the lazy dog
Regular for everything else, with generous line height so dense columns stay readable
- 44pxThe quick brown fox jumps over the lazy dog
- 30pxThe quick brown fox jumps over the lazy dog
- 22pxThe quick brown fox jumps over the lazy dog
- 17pxThe quick brown fox jumps over the lazy dog
- 15pxThe quick brown fox jumps over the lazy dog
- 13pxThe quick brown fox jumps over the lazy dog
Spacing and shape
- 4px
- 8px
- 16px
- 24px
- 40px
- 64px
Tight inside lists and tables, with clear blank lines between sections, as in a terminal.
- 0px
- 2px
- Borders
- 1 px rules and dashed dividers in the grid-rule green; frames drawn as lines, never filled boxes
- Shadows
- None; the screen is flat
Do and don't
Do
- Write examples as a short session: prompt, command, output
- Line up keys and values in fixed-width columns
- Put the background colour on green buttons, never white
- Wrap long output lines instead of letting them scroll sideways
Don't
- No second typeface
- No rounded cards, gradients or drop shadows
- No more than one bright colour for actions
- No real command or program names in the copy
Similar styles
The styles closest to this one in mood, density, era, warmth and accent colour.
- Bento techA product told in tiles: a tidy grid of rounded cards of different sizes, each holding one fact, with crisp type and soft depth.See the style
- Neo-brutalistRaw, loud and honest: thick black borders, hard offset shadows, flat clashing colours and unpolished type.See the style
- Classic corporateTrust through order: a calm blue, a clear hierarchy, a conventional layout and nothing that surprises.See the style