Styleguide
Patterns
How components come together: the shape of a page, the header, the booking row and the illustrations.
Page structure
- Opening block: small label, H1 and a lead, with .page-head spacing. Inner pages start like this; the home page has its hero.
- Sections: one idea each, with .section padding and .section-body between heading and content. Sections alternate the page background and the panel band, never two bands in a row.
- Closing band: Want to work together? with the one big Book a call button, then the footer. The memorial, legal pages and the styleguide leave it out.
Header and menu
One bar everywhere (SiteNav): logo, Portfolio, Studio, the language as a pill with a globe, and Book a call. The section you are in is blue. The bar hides while you scroll down and comes back when you scroll up.
On phones the bar keeps the logo and Book a call. A round menu button sits at the bottom right, in reach of the thumb; it opens a sheet from the bottom (a native popover, no JavaScript) with Home, Portfolio, Studio and the language, and its close X takes the button’s place. Escape or a tap outside closes it too.
Book a call row
Closes What to expect: the home page's one Book a call button (the FAQ uses a text link). The availability line sits beside the button, below it when there isn't room.
Illustrations
What we do: one canvas in three complete states (CapabilityArt.astro). Each builds in once, then loops a small story that shows the work, not decoration.
Plan: A client drops by, comments on a note and approves it.
Build: Design and code change together: a button restyled, an image swapped, a headline cut, each with its code edit.
Automate: Orders run through the workflow; each step ticks off and the count goes up.
Animation guidelines
- 01Build in fastPieces pop in (500ms) and lines draw (600ms), 150ms apart. The whole canvas is finished in about a second.
- 02Then one storyAfter the build (--loop), a single loop shows the work happening: someone approving, editing, processing. No idle wiggles for their own sake.
- 03Slow cycles4 to 8 seconds a cycle. Changes take 300–600ms; everything else holds still long enough to read.
- 04Back to the startEvery loop ends where it began (the Build edits are undone), so a cycle can repeat or pause at any point without a broken frame.
- 05Only while seenDesktop: only the active step plays. Phones: loops pause off screen and carry on when you return; the build never replays.
- 06Same systemPalette tokens only. Labels 13px+ in the 480×300 canvas. Cursors carry name tags: Matt in blue, You in yellow.
- 07Typing reads as typingCode lines appear and disappear in steps, like characters, not as smooth bars.
- 08Still without motionWith reduced motion each canvas rests on a finished frame: every step done, nothing half-built.