Skip to content
Sign inJoin waitlist

Design — Catchup HTML

Catchup is styled with Tailwind CSS classes and a few colour, font, breakpoint and motion tokens. Most changes are HTML edits; a new colour or font needs a CSS rebuild.

The pages are styled with Tailwind CSS classes written in the HTML (class="flex flex-col gap-2.5 text-body"). assets/css/style.css contains exactly the classes the pages use, generated from src/css/style.css.

That means two kinds of change:

Change Rebuild the stylesheet?
Move, copy or delete elements; use classes that already appear somewhere in the site No
Change a colour, a font, a breakpoint; use a class that appears nowhere yet (say mt-7) Yes

Once, install the tools (needs Node.js 20 or newer):

Terminal window
npm install

Then, after a change:

Terminal window
npm run build:css # one build
npm run watch:css # rebuilds on every save while you work

Both write assets/css/style.css. The build scans the .html files in the root folder and one folder down (work/, service/, blog/, legal/), and assets/js/main.js, so a class you add there is picked up. Upload the new style.css with your pages.

In src/css/style.css:

@theme {
--color-ink: #000000; /* headings, the black buttons and cards, the footer card */
--color-body: #444a46; /* paragraphs on light backgrounds */
--color-accent: #7ce3ac; /* the mint buttons, icons and cards */
--color-orange: #ff7e5d; /* the orange card on Home, the hover of links in the text */
--color-soft: #dadada; /* quiet fills (no component uses it yet) */
--color-page: #f5f5f5; /* the page */
--color-white: #ffffff; /* cards, text on photos and on black */
--color-spinner: #999999; /* the ring of the blog's loading spinner */
--color-error: #ff2244; /* the Submit button's error label */
…
}

Each name becomes a class (bg-ink, text-body, bg-accent). Change the values, rebuild, and the whole site follows. The palette is black and mint on a light grey page, with the photos carrying the rest of the colour. Keep text on its background at 4.5 : 1 or more, so it stays readable: black on mint passes easily, white on mint would not. The last tokens (error-fill, ink-hover, ink-pressed) are the Submit button’s fills.

The greys are opacity modifiers on Ink and White, so they follow them when you change them:

Class Used for
ink/80 The dark number card on Home
ink/50 The award years, a project’s detail labels
ink/30 The fields’ placeholder text, the veil over the hero, the gradients over photos
ink/20 Dividers, a field’s bottom line, the carousel’s arrows
ink/5 The track of the pricing switch
white/20 The footer’s line, the hero’s glass cards

A few colours sit outside the tokens:

Colour Where
The browser icons for light and dark browser themes, and the home-screen icon icon-light.png, icon-dark.png, apple-icon.png
The client logos assets/images/logo-*.svg (drawn in their own colours)
The swatches of the style guide repeat the hex values as text style-guide.html

The logo, the word “CATCHUP” with its mark, is an <svg viewBox="0 0 176 30"> drawing. Its shapes are filled with currentColor, so it takes the text colour (black in the header, white in the footer and on photos). It appears in the header and the footer of every page (Home has two headers), and on Home in the intro, the orange card and the closing band, and on About over the wide photo. Each copy sets its own size with the classes on the <svg>: in the header h-5 w-[117px] md:h-[25px] md:w-[147px] lg:h-[30px] lg:w-[176px], in the footer 176 / 293 / 440 px wide.

To use your own, keep each <svg …> tag with its classes and replace what is inside it, and its viewBox, with your logo’s shapes. VS Code’s Replace in Files does every page at once: turn on regular expressions (.*), search for

<svg\s+viewBox="0 0 176 30"([^>]*)>(.|\n)*?</svg\s*>

and replace it with your logo on one line, keeping $1 (the attributes of each copy):

<svg viewBox="0 0 200 40"$1><path d="…" /></svg>

Give your shapes fill="currentColor" (or none, since the <svg> carries it). For a logo of other proportions, change the widths in those classes to match your artwork (here 200 : 40 is 5 : 1, so h-5 needs w-[100px]), and rebuild the stylesheet if a class is new. Then replace aria-label="Catchup" on the links with your name.

icon-light.png and icon-dark.png (180 × 180 px) are the icons in the browser tab, for light and dark browser themes; apple-icon.png (200 × 200) is the icon on a phone’s home screen. Replace the files, keeping the names.

The interface icons are inline SVG from Phosphor: the arrows (up-right in the buttons and cards, up on the engagement card, right in the contact details and the carousel), the check of the lists and the star of the ratings, drawn on a 256 × 256 grid in the current text colour. To use another icon, open it on phosphoricons.com, copy its <path d="…"> and paste it in place of the old one. The Instagram glyph on the team cards is an image, assets/images/icon-instagram.png.

Manrope ships in assets/fonts/ as one variable file, manrope-variable.woff2 (weights 200 to 800), declared at the top of src/css/style.css:

@font-face{font-family:"Manrope"; src:url("../fonts/manrope-variable.woff2") format("woff2"); font-display:swap; unicode-range:…; font-weight:200 800; font-style:normal; }
:root{--font-manrope:Manrope,"Manrope fallback: Arial",sans-serif; }

Every page uses it through font-sans on the <body>. Titles are set in weight 600, the smaller headings, numbers, buttons and menu in 500, the text in 400. An italic word is the browser’s slanted version of the regular font.

To use another font:

  1. Put its .woff2 files in assets/fonts/.
  2. Change the @font-face rule (font-family, src, font-weight) and the first name in --font-manrope. A font that isn’t variable needs one @font-face rule per weight file (400, 500, 600).
  3. Rebuild the stylesheet.

The Manrope fallback: Arial rule sizes Arial like Manrope while the font loads; with another font, you can delete it and its name in --font-manrope. The font file covers Western European languages (the rule’s unicode-range); for other alphabets, use files that include them and remove the unicode-range. Fonts from Google Fonts can be downloaded as files with https://gwfh.mranftl.com, so they are served from your own domain, which is faster and needs no consent banner.

Text sizes are classes with a phone value first and the tablet (md:) and desktop (lg:) values after: text-[32px] md:text-[38px] lg:text-[44px]. The style guide lists every text style:

Style Phone Tablet Desktop Used for
Display 42 52 62 The Home hero’s title (weight 600)
H1 40 46 54 Page titles (600)
H2 32 38 44 Section titles (600)
H3 28 32 36 The numbers’ units, the headings of posts and legal pages
H4 24 26 28 The leads under the inner pages’ titles
H5 20 22 24 Card titles, the logo row’s title
H6 18 19 20 The numbers’ captions, post card titles
Huge 40 46 54 The numbers
Big paragraph 18 18 18 Leads, the text of a project or a service
Paragraph 16 16 16 Body text, card text, the footer’s links, form labels
Small paragraph 14 14 14 Small print
Menu 16 16 16 The header’s links, button and chip labels
Tiny 12 12 12 Tags, a post’s category and date, client roles
Subtitle 14 14 14 The labels before section titles and over the footer’s columns (upper case, letter spacing 0.03em)

Line heights are 1.2 for headings and the menu, 1.4 for paragraphs.

Spacing uses Tailwind’s scale (4 px per step, so gap-5 is 20 px) or exact values in brackets (gap-[50px]). Sections have 15, 20 and 30 px at the sides (px-[15px] md:px-5 lg:px-[30px]) and 60 / 80 / 100 px above and below; their content is at most 1440 px wide (max-w-[1440px]), the header and the footer 1728 px. Corners are 10 px on photos and cards, 5 px on the hero’s small cards and a few smaller items; buttons, tags and chips are round. There are no drop shadows.

Width Prefix
Phone below 810 px (none)
Tablet 810–1199 px md:
Desktop 1200 px and up lg:

max-md: and max-lg: apply below those widths.

The style guide page: the colours and text styles, then every component with its name

style-guide.html shows the colours, the text styles, the motion (with buttons to play each curve), the actions (buttons, tags, links), the logo and the icons, the navigation (the menu button, the footer’s link columns), the layout, the cards (service, project, testimonial, post), the numbers, the patterns (tickers, the carousel, the process steps, the pricing switch, rich text, loading on scroll) and the form with its button’s states, each with its name. To reuse one, copy its markup from there or from the page that shows it.

Elements with data-… attributes are wired to the site script, so keep those attributes when you copy them: data-header, data-header-fixed, data-bar, data-hamburger, data-phone-menu, data-nav-link, data-home-intro, data-hero-slideshow, data-appear, data-delay, data-counter, data-ticker-root, data-ticker, data-ticker-copy, data-carousel, data-process, data-step, data-pricing-switch, data-plan, data-blog-grid, data-more, data-load-spinner, data-hover, data-motion, data-link-column, data-form, data-current-year, …

The effects are in assets/js/main.js, which carries Motion; a few hovers are CSS. A few settings are written in the HTML:

Effect Where
The Home intro: four project photos rise in a small window, the logo comes up, a black cover lifts; once per browser session data-home-intro (Editing the site)
The Home hero changes project every 6 s on tablets and phones; on desktops, pointing at a title shows it data-interval="6000" on data-hero-slideshow
The header on Home comes back fixed after the hero, fading in data-header-fixed
Page titles appear word by word, out of a blur, 0.05 s apart; the lead and the block under the title rise just after data-appear="word" and data-delay on each word, data-appear="rise"
Blocks below the top rise 18 px into view once half of them is on the screen, once data-appear="view" ("tall" for blocks taller than the screen)
Numbers count up while they are on the screen data-counter (Editing the site)
The client logos run at 20 px a second, the faces and testimonials at 15; the testimonial rows stop under the pointer data-ticker="20" / "15" on the row, data-ticker-pause on its box
About’s process steps light up (the discs turn mint) while the list is on the screen data-process
Button labels roll up to a second copy and the arrow turns 45° on hover; project and post photos zoom, service cards turn black data-hover on the element, and data-motion on its parts: the rest and hover values the script moves between
The footer’s links roll and dim their neighbours data-link-column
The Blog loads four posts at a time as the visitor scrolls data-page-size on data-blog-grid

The two springs of the CSS hovers are in src/css/style.css (--ease-s0, no bounce, and --ease-s2, a slight overshoot, run over 400 ms), with Framer’s two tweens (--ease-t1, --ease-t4). The tweens and springs of the script, the intro’s timing and the counter’s step are at the very top of assets/js/main.js (tokens/motion.ts).

With “reduce motion” switched on in the visitor’s system, movement is left out: the Home intro doesn’t play, the tickers stand still, the numbers show their final value, page titles and blocks fade in without rising or blurring, and the hovers change without moving. Fades and colour changes stay.