Skip to content
Sign inJoin waitlist

Design — Catchup Astro

The look of this Astro template comes from a small set of tokens: change one and nearly every page, component and state follows.

So you rarely need to touch a component. This guide covers the colours, the logo, the fonts, the text styles, the spacing, the motion, the components and the icons.

Run npm run dev and open http://localhost:4321/style-guide. It shows the colours, the text styles and the motion tokens, then every component in its states, each with its name: the buttons and links, the logo and the icons, the menu button and the footer links, the layout pieces, the cards, the counter, the patterns (the ticker, the check list, rich text, the word-by-word title, the spinner) and the form with its fields, chips and button states. When you want to know what a change will affect, look there.

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

src/design-system/theme.css:

@theme {
--color-ink: #000000; /* [Black] headings, the black buttons and cards */
--color-body: #444a46; /* [Body] paragraphs on light backgrounds */
--color-accent: #7ce3ac; /* [Accent] the mint buttons, icons and cards */
--color-orange: #ff7e5d; /* [Orange] the orange cards */
--color-soft: #dadada; /* [Soft Grey] placeholders and quiet fills */
--color-page: #f5f5f5; /* [Background] the page */
--color-white: #ffffff; /* [White] cards, text on photos */
/* …and the spinner's, the form button's error and hover colours */
}

Each name becomes a Tailwind class: bg-ink, text-body, bg-accent. Swap the hex values for your own palette and the site changes. The template is black and grey on a light grey page, with white cards, a mint accent (the header’s Contact button, the “Start a Project” buttons of Work and Services, Home’s call-to-action card, the check discs) and an orange one (a number card on Home, the hover of links in text). Keep text on its background at 4.5 : 1 or more, or the site becomes hard to read: Black on the page is about 19 : 1, Body on the page about 8 : 1.

Faded colours are opacity modifiers, named as in the original design:

Modifier Framer name Used for
ink/80 Black 80 the dark number card on Home
ink/50 Black 50 the award years, a project’s detail labels
ink/30 Black 30 the fields’ placeholders, the veil over the Home hero, the gradients over photos
ink/20 Black 20 dividers, a field’s bottom line, the carousel’s arrows
ink/5 Black 05 the track of the pricing switch
white/20 White 20 the footer’s lines, the hero’s glass buttons and card

They follow the palette when you change ink. The placeholders of the fields (Black 30) are light by design: a darker value reads better.

A few colours sit outside the tokens, so change them too when you change a colour:

Colour Where
The page colour behind the header bar, as rgba(245, 245, 245, …) (the bar fades it in on Home) src/components/site/Bar.astro, src/components/site/header.ts
The service card’s panel turning black on hover, and the project tags turning mint, as hex values (Motion animates values, not theme variables) src/design-system/components/cards/ServiceCard.astro, src/design-system/components/actions/MetaTag.astro
The browser icons: black for a light browser theme, white for a dark one public/icon-light.png, public/icon-dark.png, public/apple-icon.png
The client logos (black SVG files) src/assets/images/logo-*.svg
The swatches of the style guide repeat the hex values as text src/components/style-guide/tokens.ts

The “Catchup” wordmark is drawn as an SVG path in src/design-system/components/brand/Logo.astro, in the current text colour: black in the header, white over Home’s hero, in the footer and on photos. The caller sets its size; it is 176 × 30 in the header on desktop (147 on tablets, 117 on phones), 440 wide in the footer (293 / 176), and it also appears on About’s wide photo, in Home’s intro, on Home’s orange number card and on Home’s call-to-action photo. To use your own:

  • As an SVG: replace the <path> with your logo’s path data, and set the viewBox="0 0 176 30" to your artwork’s size. The places that show it set a width and a height: change the h-… and w-… classes that go with <Logo> if your logo has other proportions (search for <Logo).
  • As an image file: put it in public/ and replace the <svg> with an <img> of it; keep a white version for the places on black and on photos.

In the header and the footer the logo links to Home, named for screen readers with site.name.

The browser icons are public/icon-light.png and public/icon-dark.png (180 × 180, for light and dark browser themes) and public/apple-icon.png (200 × 200, the home screen).

The template loads Manrope with the Astro Fonts API, in astro.config.mjs:

fonts: [
{
provider: fontProviders.google(),
name: "Manrope",
cssVariable: "--font-manrope",
weights: ["200 800"],
styles: ["normal"],
subsets: ["latin"],
fallbacks: ["sans-serif"],
},
],

Manrope is one variable font here, with every weight from 200 to 800. The <Font> line in src/layouts/Layout.astro loads it on every page, and theme.css makes --font-manrope the site font (--font-sans). The text is set in weights 400, 500 and 600, and bold runs in rich text in 700. Only the upright style is loaded: an italic run in a post is the browser’s slanted version of the regular text; add "italic" to styles to load the real italic if your font has one.

To use another Google font, change name and keep cssVariable:

name: "DM Sans",
cssVariable: "--font-manrope",
weights: ["100 1000"],
styles: ["normal"],

Give a variable font its own range, or list ["400", "500", "600", "700"] for a font that isn’t variable. For a font you have licensed yourself, use fontProviders.local() with your files, for example in src/assets/fonts/ (see the Astro fonts guide). Astro downloads the font when the site builds and serves it from your own domain either way, so there is no request to Google at runtime.

src/design-system/tokens/text.ts holds the sizes and line heights, named as in the original design:

Style Phone Tablet (md:) Desktop (lg:) Weight Used for
display 42 52 62 600 The Home hero’s title, “404 Error”
h1 40 46 54 600 Page titles
h2 32 38 44 600 Section titles
h3 28 32 36 500 The numbers’ units, a project’s story titles, the headings of posts and legal pages
h4 24 26 28 500 The leads under the inner pages’ titles
h5 20 22 24 500 Card titles, the logo row’s title
h6 18 19 20 500 The numbers’ captions, post card titles
huge 40 46 54 500 The counters, the prices
big 18 18 18 400 Leads, quotes
paragraph 16 16 16 400 Body text, card text, the footer links, form labels
small 14 14 14 400 Small print, the notes under a price
menu 16 16 16 500 The header’s links, button and chip labels
tiny 12 12 12 400 Tags, the post’s category and date, client roles
subtitle 14 14 14 400 The labels before section titles and over the footer columns (upper case, 3 % letter spacing)
caption 14 14 14 400 The captions over a post’s date and category and a legal page’s date

Everything is Manrope. The display and heading styles have a line height of 1.2, the paragraph styles 1.4, Menu, Tiny, Subtitle and Caption 1.2. Change the numbers in text.ts rather than in the components, and text stays consistent across the site. Use a style as class={text.h2} or combine: class={cn(text.h6, "text-white")}.

Three sizes, set in theme.css:

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

The side padding is 15 px on phones, 20 px on tablets and 30 px on desktops, and most sections have 60 / 80 / 100 px above and below and between their blocks (sectionGutters, sectionPadding and sectionGap in src/design-system/components/layout/section.ts). Content is at most 1440 px wide (the width prop of Section); the header, the Home hero and the footer go to 1728. The header is fixed at the top, 60 px tall on phones, 90 on tablets and 100 on desktops; inner pages start with HeaderSpacer, which takes the same room (Pages and sections).

src/design-system/tokens/motion.ts holds the transitions and timings, named as in the original design. The scripts in src/design-system/scripts/ (and the header’s, src/components/site/header.ts) play them with Motion:

Token Values Used for
tweenAppear (T1) 1 s, cubic-bezier(0.59, 0.25, 0.12, 1.17) (overshoots about 3 %) Blocks rising into view and on load, the title words, the Home intro
tween (T4) 0.4 s, cubic-bezier(0.44, 0, 0.56, 1) The card hovers, the menu links’ underline, the menu button
tweenDelayed (T4d) T4 after 0.2 s The fixed header fading in on Home, the phone menu opening
spring (S0) no bounce, 0.4 s The button arrow’s turn, the project tags’ fill; every part without a transition of its own
springSoft (S2) bounce 0.2, 0.4 s The footer links’ roll and the dimming of the others, a project’s detail links
appearOffset, appearThreshold 18 px, 0.5 Blocks rise 18 px into place once half of them is in view
wordStagger 0.05 s The words of a page title, one after the other
introDelay, loadRiseDelay 0.2 s, 0.15 s The lead under a title, the blocks that rise on load
logoTickerSpeed, slowTickerSpeed 20 and 15 px a second The client logos; the faces and the testimonial rows
heroInterval 6000 ms The Home hero moves on every 6 s on tablets and phones
counterStep 5 ms The numbers count up one step every 5 ms
intro start 100, step 300, hold 1000 ms, cover 0.3 s The Home intro’s photos, logo and black cover

theme.css holds the same curves for the hovers that run without a script (--ease-t1, --ease-t4, and the springs as --ease-s0 and --ease-s2 over 400 ms: the award rows, the team cards, the contact links’ arrows, the chips, the pricing switch) and --ease-form (the form button’s fills). The buttons’ label roll uses Motion’s own default spring. There are no page transitions, no parallax and no custom cursor.

Hovers are attributes in the markup. data-hover marks the element you point at and data-motion gives each part that changes its two states (rest and hover), played by src/design-system/scripts/hover.ts; data-transition names the token a part moves with.

Effect Where to change it
The Home intro plays once per visit and is skipped for reduced motion src/components/sections/HomeIntro.astro and scripts/home-intro.ts (the visit is remembered in sessionStorage as catchup-intro); to remove it, delete <HomeIntro … /> from src/pages/index.astro
The Home hero changes slide when the pointer enters a title on desktop, every 6 s on tablets and phones heroInterval in tokens/motion.ts; scripts/hero-slideshow.ts
The client logos, faces and testimonial rows move sideways logoTickerSpeed, slowTickerSpeed in tokens/motion.ts
Page titles appear word by word <WordAppear> in src/components/sections/TitleBlock.astro and the other title sections; a plain text shows at once
Blocks rise into view as you scroll <Appear> around them in the sections; remove the wrapper (keep its class) to show a block at once
Blog shows four posts, then four more as you scroll pageSize in src/content/pages/blog.json
Home shows the three newest posts posts.slice(0, 3) in src/pages/index.astro
“More Blog” shows two posts, “Other works” two projects the limit of getRelatedPosts and getOtherWorks in src/lib/content.ts
About’s process steps light up together when half of the block is in view scripts/process-steps.ts

With “reduce motion” switched on in the visitor’s system, movement is left out: blocks and title words fade in where they stand, the tickers stand still, the numbers show their final value at once, and the Home intro doesn’t play. Fades and colour changes stay. play() in src/design-system/utils/play.ts, which every script animates through, makes moves, turns and sizes jump; the tickers and the spinners check the setting in CSS (motion-reduce:).

Corners are 10 px on photos, cards, panels and the footer card, and 5 px on the hero’s project card, the team’s social chips and the Details pills; buttons, tags, chips and discs are round. Spacing is Tailwind classes on the components (gap-5, p-5, gap-[50px]). Tailwind’s scale is 4 px per step, so gap-5 is 20 px. Change them where you see them; the style guide shows the result immediately.

src/design-system/components/ holds the buttons and links (with the rolling label and the turning arrow), the logo and the icons, the menu button and the footer’s link columns, the section layout and heading, the cards (service, project, testimonial, post), the counter, the check list, rich text, the ticker, the word-by-word title, the spinner and the form parts. Their behaviour is in src/design-system/scripts/: each component with state calls an init*() function from its own <script>. The README lists every component with its props and where it is used, and every script with what it does. The sections that make up a page are one level up, in src/components/sections/, and are listed in Pages and sections.

The five icons (the Phosphor arrow-up-right, arrow-up, arrow-right, check and star) are stored as path data in src/design-system/components/icons/paths.ts; <Icon name="arrow-up-right" /> draws one in the current text colour. To add one:

  1. Open the icon on phosphoricons.com and copy the SVG.

  2. Take the d="…" of its <path>.

  3. Add a line to iconPaths:

    "my-icon": "M128,24A104,104,0,1,0,…",

Then use <Icon name="my-icon" class="size-5" />. Paths use a 256 × 256 grid, which is what Phosphor exports; an icon drawn on another grid gets its viewBox in iconViewBoxes. If you keep the style guide, add the new name to icons in src/components/style-guide/tokens.ts too: that list is exhaustive on purpose, so npm run check reports it until you do. The social links are text, not icons; the team’s social chip shows an image from the content (/images/icon-instagram.png).