Design — Catchup Next.js
The look of this Next.js 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.
See everything first
Section titled “See everything first”Run npm run dev and open http://localhost:3000/style-guide. It shows the colours, the text styles, the motion
tokens, the buttons and links, the logo and the icons, the menu button and the footer’s link columns, the section
layout, the cards, the counters, the patterns (the tickers, rich text, the check list, the loading spinner, the
word-by-word title) and the form with its states, each with its name. When you want to know what a change will affect,
look there.

Colours
Section titled “Colours”src/design-system/theme.css:
@theme { --color-ink: #000000; /* headings and text, the black buttons and cards, the footer */ --color-body: #444a46; /* paragraphs on light backgrounds: leads, card text, roles */ --color-accent: #7ce3ac; /* the mint buttons, the Contact button, check discs, the category pills */ --color-orange: #ff7e5d; /* the orange number card on Home; links in rich text and on Contact on hover */ --color-soft: #dadada; /* quiet fills (defined, not used by a component yet) */ --color-page: #f5f5f5; /* the page and the header */ --color-white: #ffffff; /* cards and panels, text on photos and on black */ --color-spinner: #999999; /* the ring of the loading spinner under the blog list */ --color-error: #ff2244; /* the Submit button's error label */ … /* error-fill, ink-hover, ink-pressed: the Submit button's other states */}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 on a light grey page with mint for actions; keep text on its background at
4.5 : 1 or more, or the site becomes hard to read. Black text sits on the mint buttons: if your accent is dark, the
buttons’ labels need a light colour (Button in src/design-system/components/actions/Button.tsx).
Faded colours are opacity modifiers, as in the original design: ink/80 (the dark number card), ink/50 (the award
years, a project’s detail labels), ink/30 (placeholders, the hero’s veil, gradients), ink/20 (dividers, a field’s
bottom line, the carousel’s arrows), ink/5 (the pricing switch’s track) and white/20 (the footer’s lines, the hero’s
glass buttons). They follow Ink and White when you change them.
A few colours sit outside the tokens, so change them too when you change a colour:
| Colour | Where |
|---|---|
| The browser icons: a dark and a light mark | public/icon-light.png, public/icon-dark.png, src/app/apple-icon.png |
| The header’s background, written as the page colour with its opacity (Motion fades it) | src/components/site/Header.tsx (rgba(245, 245, 245, …)) |
| The service cards’ panel turning black on hover (black, white and the Body colour) | src/design-system/components/cards/ServiceCard.tsx |
| The project cards’ service tags turning mint on hover | metaFill in src/design-system/components/actions/Button.tsx |
| The client logos (black SVG files) | public/images/logo-*.svg |
| The swatches of the style guide repeat the hex values as text | src/app/style-guide/tokens.ts |
The “CATCHUP®” wordmark is drawn as SVG paths in src/design-system/components/brand/Logo.tsx, in the current text
colour: white over the Home hero, black in the fixed header, white in the footer, on the orange number card, on Home’s
call-to-action photo and on About’s wide photo, and in the Home intro. To use your own:
- As an SVG: replace the
<path>elements with your logo’s, and setviewBox="0 0 176 30"to your artwork’s size. - As an image file: replace the
<svg>with an<Image>of your file (it then keeps its own colours).
Each place sets the logo’s size with className: 117 / 147 / 176 px wide (phone / tablet / desktop) in the header
(src/components/site/Header.tsx) and 176 / 293 / 440 in the footer (src/components/site/Footer.tsx); the heights
follow the 176 : 30 proportions, so change them for artwork of other proportions. The logo links are named for screen
readers by site.name (src/content/site.ts). The browser icons are described in Editing the content.
The template loads Manrope once, through next/font in src/app/layout.tsx:
const manrope = Manrope({ variable: "--font-manrope", subsets: ["latin"],});Manrope is one variable font here, every weight in one file. theme.css makes --font-manrope the site font
(--font-sans). The text styles use weights 400, 500 and 600, and the bold words of rich text 700. Manrope has no
italic: the italic phrases of the posts are the browser’s slanted version of the regular text.
To use another Google font, import it by name from next/font/google and keep the variable name:
import { Inter } from "next/font/google";const manrope = Inter({ variable: "--font-manrope", subsets: ["latin"] });A font that isn’t variable needs its weights listed (weight: ["400", "500", "600", "700"]), and one with a real
italic can load it with style: ["normal", "italic"]. For a font you have licensed yourself, use next/font/local and
point it at the files in src/app/fonts/. Next.js serves the font from your own domain either way, so there is no
request to Google at runtime.
Text styles
Section titled “Text styles”src/design-system/tokens/text.ts holds the sizes, line heights and weights, 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, headings in posts and legal pages, the project page’s story titles |
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’s links, the text of posts |
small |
14 | 14 | 14 | 400 | Small print |
menu |
16 | 16 | 16 | 500 | The header’s links, button and chip labels |
tiny |
12 | 12 | 12 | 400 | Tags, a post’s category and date, client roles |
subtitle |
14 | 14 | 14 | 400 | The upper-case labels before section titles and over the footer columns (3 % letter spacing) |
caption |
14 | 14 | 14 | 400 | The captions over a post’s date and category and a legal page’s date |
Headings have a line height of 1.2, paragraphs 1.4. Change the numbers in text.ts rather than in the components, and
text stays consistent across the site. Use a style as className={text.h2} or combine:
className={cn(text.h6, "text-white")}. The design system’s README lists all 16 with
where each is used.
Breakpoints and spacing
Section titled “Breakpoints and spacing”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: |
Content is centred and stops at 1440 px; the header, the Home hero and the footer at 1728 px. 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.tsx). The header is fixed at the top, 60 px tall on phones, 90 on tablets
and 100 on desktops; inner pages start with a spacer of the same height (HeaderSpacer in
src/components/sections/PageTitle.tsx) (Pages and sections).
Motion
Section titled “Motion”src/design-system/tokens/motion.ts holds the transitions and timings, copied from the original design:
| Token | Values | Used for |
|---|---|---|
tweenAppear (T1) |
1 s, overshoots about 3 % and settles | Blocks rising into view, page titles appearing word by word, the Home intro |
tween (T4) |
0.4 s, ease in and out | Card hovers, the menu links’ underline, the menu button |
tweenDelayed |
T4 after 0.2 s | The fixed header fading in on Home, the phone menu opening |
spring (S0) |
no bounce, 0.4 s | The buttons’ rolling label and turning arrow, the project cards’ tags |
springSoft (S2) |
bounce 0.2, 0.4 s | The footer’s links rolling and dimming, a project’s service links |
appearOffset, appearThreshold |
18 px, half in view | How far a block rises and when |
wordStagger, introDelay, loadRiseDelay |
0.05 s, 0.2 s, 0.15 s | Page titles’ words, the lead under a title, the blocks that rise on load |
logoTickerSpeed, slowTickerSpeed |
20 and 15 px a second | Home’s client logos; the clients’ faces and the testimonial rows |
heroInterval |
6000 ms | The Home hero’s slideshow on tablets and phones |
counterStep |
5 ms | The numbers counting up |
intro |
photos 300 ms apart, held 1 s | The Home intro |
theme.css holds the same curves for CSS (--ease-t1, --ease-t4, --ease-s0, --ease-s2, run over 400 ms) and
--ease-form for the Submit button’s colours and the spinner’s fade. MotionProvider (wrapped around every page in
src/app/layout.tsx) makes spring the default of every Motion element that sets no transition of its own.
| Effect | Where to change it |
|---|---|
| The Home intro plays once per visit | src/components/sections/HomeIntro.tsx; delete <HomeIntro … /> from src/app/page.tsx to drop it |
| The hero changes slide on hover (desktops) and every 6 s (tablets, phones) | heroInterval in tokens/motion.ts; src/components/sections/HomeHero.tsx |
| Blocks rise into view as you scroll | <Appear> (src/design-system/components/motion/Appear.tsx); appearOffset for the distance |
| Page titles appear word by word | <WordAppear> in the sections; a plain heading with the same className shows at once |
| The numbers count up | <Counter>; the start of each number in the page copy (Editing the content) |
| The process steps on About light up together | src/components/sections/AboutProcess.tsx |
| Blog loads four posts at a time | pageSize in src/content/pages/blog.ts |
There is no page transition, no parallax and no custom cursor, as in the original design.
Reduced motion
Section titled “Reduced motion”With “reduce motion” switched on in the visitor’s system, movement is left out: the Home intro is skipped, the tickers
stand still, the numbers show their final value, titles and blocks fade in without rising or blurring, and transforms
and layout animations are skipped. Fades and colour changes stay. MotionProvider makes Motion skip its transform and
layout animations; the tickers check the setting in CSS (motion-reduce:), and the intro, the counters and the titles
check it themselves.
Corners, spacing, shadows
Section titled “Corners, spacing, shadows”Corners are 10 px on photos, cards, panels and the footer, 5 px on the team’s social chips and the project tables’
labels, and round on buttons, tags, chips and discs. There are no drop shadows. 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.
Components
Section titled “Components”src/design-system/components/ holds the buttons and links, the logo and the icons, the scroll and load animations,
the cards (service, project, testimonial, post), the menu button and the footer’s link columns, the counter, rich text,
the tickers, the check list, the spinner, the section layout and the form parts. Its
README lists every component with its props and where it is used. 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, arrow-up-right (buttons, project cards), arrow-up (the engagement card on Home), arrow-right (the
links on Contact), check (lists) and star (ratings), are Phosphor shapes stored as path
data in src/design-system/components/icons/paths.ts; <Icon name="check" /> draws one in the current text colour. To
add one:
-
Open the icon on phosphoricons.com and copy the SVG.
-
Take the
d="…"of its<path>. -
Add a line to
iconPaths:"my-icon": "M128,24A104,104,0,1,0,…",
Then use <Icon name="my-icon" className="size-5" />. Paths use a 256 × 256 grid, which is what Phosphor exports. If you
keep the style guide, add the new name to icons in src/app/style-guide/tokens.ts too: that list is exhaustive on
purpose, so npm run build stops until you do.