Skip to content
Sign inJoin waitlist

Design — Metuo 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.

Run npm run dev and open http://localhost:3000/style-guide. It shows the colours, the text styles, the motion, the buttons and links, the logo and the icons, the menu button and the social icons, the section layout, the cards, the figures and the rating, the patterns (the rows that open, the plans, the lit lists, the story card, the list that loads on scroll, rich text), the video band and the form with its states, each with its name. 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-green: #2f3724; /* headings and text, the dark buttons and cards, the founder quote */
--color-black: #000000; /* text typed into a field; black/30, black/5 for veils, hairlines, field fills */
--color-grey: #707070; /* leads, descriptions, meta, labels */
--color-brown: #ae8c73; /* the hero's second button */
--color-orange: #f98b31; /* the button hover fill, stars, "(32% off)", link hovers */
--color-soft-grey: #b4b4b4; /* the pricing switch when off, an open row's minus */
--color-background: #fcfbf6; /* the page, the solid header, text over photos */
--color-white: #ffffff; /* cards, rows, light buttons */
--color-pressed: #333333; /* the Submit button while pressed */
--color-error: #ff2244; /* the Submit button's error label, a failed field's message */
--color-spinner: #999999; /* the ring of the loading spinner */
}

Each name becomes a Tailwind class: bg-green, text-grey, border-soft-grey. Swap the hex values for your own palette and the site changes. Green on Background reads at 12 : 1 and Grey at 4.8 : 1; keep text on its background at 4.5 : 1 or more, or the site becomes hard to read. Orange is used for hovers and the stars, not for text that must be read (2.3 : 1 on the page colour); White on Brown, the hero’s second button, is 3.1 : 1, the original design’s colours.

Translucent colours are opacity modifiers on a token, as in the original design: black/30 (placeholders, a focused field’s hairline, the photo veils), black/10 (the footer’s hairline), black/5 (field fills and hairlines), white/10 (the hero’s hairline) and white/5 (the header’s pill over a photo, behind a blur). They follow their token when you change it.

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

Colour Where
Green, White and Soft Grey repeated as hex values, because Motion animates them src/design-system/components/actions/Button.tsx, PlusMinus.tsx, src/design-system/components/cards/TeamCard.tsx
The browser icons: a Green and a light leaf public/icon-light.svg, public/icon-dark.svg, src/app/apple-icon.png
The logo files for use elsewhere public/images/logo.png (Green), public/images/logo-white.svg
The social icons (black) public/images/icon-*.svg
The swatches of the style guide repeat the hex values as text src/app/style-guide/tokens.ts

The Metuo logo, the leaf and the wordmark, is drawn as SVG paths in src/design-system/components/brand/Logo.tsx, in the current text colour: White over the photo at the top of a page, Green once the header turns solid and in the footer. To use your own:

  • As an SVG: replace the paths list with your logo’s path data (one string per <path>), and set the viewBox="0 0 372 100" to your artwork’s size.
  • As an image file: replace the <svg> with an <Image> of your file. A file has one colour, so the header’s White version over the photos needs a second file, or a logo that reads on both.

It is 92 × 25 px everywhere: change h-[25px] w-[92px] in Logo.tsx to fit your proportions. The link’s name for screen readers is site.name (src/content/site.ts), passed in src/components/site/Header.tsx and Footer.tsx. The same artwork is in public/images/logo.png and logo-white.svg for use elsewhere; the site itself draws the logo from Logo.tsx. 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 uses weight 400, the headings and the menu 500, the button labels 600, and the bold words of rich text, the team bios and the e-mail link 700.

To use another Google font, import it by name from next/font/google and keep the variable name:

import { DM_Sans } from "next/font/google";
const manrope = DM_Sans({ variable: "--font-manrope", subsets: ["latin"] });

A font that isn’t variable needs those weights listed (weight: ["400", "500", "600", "700"]). 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. Every text style sets a letter spacing of −0.03em (src/design-system/tokens/text.ts): change it there if your font looks cramped.

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

Style Phone Tablet (md:) Desktop (lg:) Used for
display 52 58 64 The Home hero’s title, the page titles over a photo, the 404’s title
h1 42 48 54 Contact’s and a post’s titles, prices, the figures
h2 32 36 40 Section titles
h3 28 32 36 The founder quote, rich-text headings
h4 24 26 28 A plan’s name, a story’s headline on Home, the form’s title
h5 20 19 24 The page titles’ lead, the Testimonial page’s headlines
h6 18 19 20 Row, card and question titles, quotes on story cards
paragraph 16 16 16 Leads, descriptions, rich text, the footer’s links
small 14 14 14 Section labels, field labels, meta, number bubbles
tiny 12 12 12 The hero’s foot line, a plan’s “Perfect for” note
menu 14 14 14 The header’s links (weight 500)
button 14 14 14 Button labels, the Submit button (weight 600)

Everything is Manrope at −0.03em. The headings are weight 500 with a line height of 1.1 (h6 1.2), the paragraph styles 400 at 1.2. h5 is smaller on tablets than on phones, as measured in the original design. 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")}.

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 content stops at 1200 px and stays centred on wider screens; photos, videos and the coloured bands run the full width. 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 (sectionGutters and sectionPadding in src/design-system/components/layout/Section.tsx; the gap between a section’s blocks is set per section). The header is fixed to the top, 65 px tall on phones and 82 px from tablets up (Pages and sections).

src/design-system/tokens/motion.ts holds the transitions Motion uses:

Token Values Used for
spring (S0) no bounce, 0.4 s Nearly every hover and change: the buttons, the links, the header, the menu button, the rows opening, the price roll, the client photos
springSoft (S2) bounce 0.2, 0.4 s The post cards’ photo, the social icons, the plus turning, the pricing switch, the lit points
cardTween (TT) 0.4 s, an ease-in The team card’s “+” and bio panel

theme.css holds the same springs as CSS curves (--ease-spring-a, --ease-spring-b) and the animations that run on load without Motion: --animate-appear (the header’s parts and the hero’s pill and buttons rising into place, 0.6 s), --animate-zoom-in (the hero’s photo growing from 20 %, 0.8 s after 0.5 s) and --animate-word-in (the hero’s words); --ease-form is the curve of the Submit button’s colours and the spinner’s fade. Lower a spring’s duration for a snappier feel, or raise bounce for a livelier one. MotionProvider (wrapped around every page in src/app/layout.tsx) also makes spring the default of every Motion element that sets no transition of its own.

There are no page transitions and no count-ups. What moves, and where to change it:

Effect Where to change it
The header turns from transparent to solid when the section after the photo reaches the middle of the screen src/components/site/Header.tsx; the section that switches it carries headerSwitch (data-header-switch)
The hero’s title, text and foot line appear word by word <WordEffect> in src/components/sections/HomeHeroSection.tsx (delay, stagger); a plain element with the same className shows at once
The photos at the top of the pages (and a post’s cover) move at half the scroll speed <Parallax> in HomeHeroSection.tsx, PageTitleSection.tsx, PostArticleSection.tsx
The small photo of Home’s “About us” zooms from 150 %, the founder quote’s photo drifts, the footer rises 200 px into place <ScrollTransform> in HomeAboutSection.tsx, FounderQuoteSection.tsx, src/components/site/Footer.tsx (y, scale: from, to)
The videos grow from 60 % and rise 160 px into place src/design-system/components/media/VideoBand.tsx
“Why choose us” and “Our core values” light a point as its photo passes the middle of the screen; phones show the photos in a strip moving at 10 px a second src/design-system/components/patterns/ScrollSpyList.tsx (speed={10})
Home’s story card turns to the next story as the page scrolls src/design-system/components/patterns/StoryCards.tsx; how many stories: stories.count in home.ts
The Testimonial page’s cards stop at the top and the next one slides over src/components/sections/TestimonialStoriesSection.tsx (plain CSS, sticky)
The process steps: the first starts open, one open at a time; the questions: the first open, each on its own defaultOpen of Accordion and FaqList in src/design-system/components/patterns/Accordion.tsx
Blog shows six posts, then six more as the visitor scrolls list.pageSize in src/content/pages/blog.ts

With “reduce motion” switched on in the visitor’s system, movement is left out: the words and the parts that appear on load fade in without rising, the hero’s photo doesn’t zoom, the parallax and scroll effects stand at their end positions, the phone strip of photos stands still (it can still be dragged), the rows open at once, the prices and the story portraits change without sliding, and the spinners stand still. Fades and colour changes stay, and the videos still play. MotionProvider makes Motion skip its transform and layout animations; the CSS animations check the setting with motion-reduce:, and the scroll effects and rows check it themselves.

Corners are 10 px on cards, rows and photos, 5 px on buttons, fields, the plus box, the arrow box, the menu button and the portraits, 4 px on the checkboxes, and round on bubbles, dots, avatars and the switch. 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.

src/design-system/components/ holds the buttons and links, the plus mark and the pricing switch, the logo and the icons, the motion helpers (the word effect, scroll transforms, parallax), the menu button and the social icons, the section layout, the cards (post, price, service, team, testimonial), the figures, the points and the client rating, the patterns (the rows that open, the questions, the plans, the service rows, the lit lists, the story card, the list that loads on scroll, rich text), the video band 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 two icons, arrow-right (the buttons’ arrow box and the footer’s links) and star-fill (the rating’s stars), are Phosphor shapes stored as path data in src/design-system/components/icons/paths.ts; <Icon name="arrow-right" /> draws one in the current text colour. The social marks are image files, not icons (Editing the content). To add an icon:

  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" 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.