Skip to content
Sign inJoin waitlist

Design — Metuo 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, the motion vocabulary with a track to play each curve, the buttons and links, the logo and the icons, the menu button and the social icons, the layout pieces, the cards, the numbers, the patterns (the service rows, the steps, the questions, the plans, the lists that light up or load on scroll, the pinned stories, rich text), the video band and the scroll effects, 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; /* [Green] headings, body text on light, the dark buttons and cards, the founder quote */
--color-black: #000000; /* [Black] text typed into a field; Black 30 / Black 05 as black/30, black/5 */
--color-grey: #707070; /* [Grey] leads, descriptions, meta, labels */
--color-brown: #ae8c73; /* [Brown] the hero's second button */
--color-orange: #f98b31; /* [Orange] the button hover fill, stars, "(32% off)", link hovers */
--color-soft-grey: #b4b4b4; /* [Soft Grey] the pricing switch when off, the open FAQ row's minus */
--color-background: #fcfbf6; /* [Background] the page, text over photos */
--color-white: #ffffff; /* [White] cards, light buttons */
--color-pressed: #333333; /* the Submit button while pressed */
--color-error: #ff2244; /* the Submit button's error label (and its 15% fill) */
--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. The template is dark green on a warm off-white: green is the text, the headings and the dark buttons, background the page and the text on photos, white the cards. Keep text on its background at 4.5 : 1 or more, or the site becomes hard to read; Green on Background is about 12 : 1 in the demo, Grey on Background about 4.8 : 1.

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

Modifier Framer name Used for
black/30 Black 30 the fields’ placeholders, a focused field’s hairline, the middle of the photo veils
black/10 Black 10 the footer’s hairline
black/5 Black 05 the fill and hairline of the fields, the checkboxes
white/10 White 10 the hairline in the Home hero
white/5 White 05 the header’s pill and menu button over a photo, behind a blur
error/15 — the Submit button’s fill after a failed send

They follow the palette when you change a colour. The placeholders of the fields (Black 30 on the fields’ light fill) are light by design, about 2 : 1: a darker value reads better.

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

Colour Where
Green, White and Soft Grey written as hex, because Motion animates them as values: the button tones, the plus-minus box, the team card’s “+” src/design-system/components/actions/button.ts, components/actions/PlusMinus.astro, scripts/plus-minus.ts, components/cards/TeamCard.astro, scripts/team-card.ts
The dark veil over the page titles’ photos (transparent → black at 30 % → black, written as rgba() values) src/components/sections/PageTitleSection.astro (the hero, the founder quote and a post’s cover use the same veil as Tailwind classes)
The browser icons: the Green leaf for a light browser theme, a light leaf for a dark one public/icon-light.svg, public/icon-dark.svg, public/apple-icon.png
The logo as files src/assets/images/logo.png (Green), src/assets/images/logo-white.svg
The swatches of the style guide repeat the hex values as text src/components/style-guide/tokens.ts

The leaf mark and the “metuo” wordmark are drawn as SVG paths in src/design-system/components/brand/Logo.astro, in the current text colour (White over a photo, Green on the solid header and in the footer), and link to Home. To use your own:

  • As an SVG: replace the strings in paths with your logo’s path data, and set the viewBox="0 0 372 100" to your artwork’s size.
  • As an image file: put it in public/ and replace the <svg> with an <img> of it. A file has one colour, so check it over the photos (the header is transparent there) and on the light header.

It is 92 × 25 px everywhere: change h-[25px] w-[92px] in Logo.astro to fit your proportions. Its name for screen readers is site.name. The same artwork is in src/assets/images/logo.png and logo-white.svg for use elsewhere; the site itself draws the logo from Logo.astro.

The browser icons are public/icon-light.svg and public/icon-dark.svg (for light and dark browser themes) and public/apple-icon.png (180 × 180, 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, every weight from 200 to 800; the site uses 400 (text), 500 (headings and the menu) and 600 (buttons). The <Font> line in src/layouts/Layout.astro loads it on every page, and theme.css makes --font-manrope the site font (--font-sans). There is no italic in the template.

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

name: "Inter",
cssVariable: "--font-manrope",
weights: ["100 900"],
styles: ["normal"],

Give a variable font its own range (["100 900"] for Inter), or list ["400", "500", "600"] for a font that isn’t variable; a range the font doesn’t have makes Google Fonts refuse the request, and the build warns No data found for font family … and leaves the site on the fallback font. 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. Every text style sets a letter spacing of −0.03em, which suits Manrope; loosen it in tokens/text.ts for a wider font.

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
h1 42 48 54 Contact’s and a post’s titles, prices, the numbers
h2 32 36 40 Section titles
h3 28 32 36 The founder quote, rich-text headings, the 404’s title
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 headlines of Client Stories (the tablet size is smaller than the phone’s, as in the original design)
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
button 14 14 14 Button labels, the Submit button

Everything is Manrope at −0.03em. Headings are weight 500 with a line height of 1.1 (1.2 for h6), the paragraph styles weight 400 at 1.2 (menu 500, button 600). 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 (sectionGutters and sectionPadding in src/design-system/components/layout/section.ts); the gap between a section’s blocks is set per section (the gap prop of Section). Content is at most 1200 px wide and stays centred on wider screens. 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 springs and tweens; the scripts in src/design-system/scripts/ (and the header’s, src/components/site/header.ts) play them with Motion, and theme.css holds the CSS curves and the load animations:

Token Values Used for
spring (S0) no bounce, 0.4 s Nearly every hover and change: the buttons, the links, the header’s looks and pill, the menu button, rows opening, the price roll, the client photos rising; also --ease-spring-a in CSS
springSoft (S2) bounce 0.2, 0.4 s A post card’s photo, the social icons, the plus-minus turning, the pricing switch, the points lighting up; also --ease-spring-b
cardTween (TT) 0.4 s, an ease-in The team card’s “+” and bio panel
scrollSpring (SP) stiffness 500, damping 60 Smooths the zoom of Home’s small “About us” photo
animate-appear (TA) 0.6 s, after a delay per part The header’s parts (18 px) and the hero’s pill and buttons (35 px) rising in on load
animate-zoom-in (TZ) 0.8 s after 0.5 s The Home hero’s photo growing from 20 % on load
animate-word-in (TW) per word, spring S0, 0.05 s apart The Home hero’s title, text and foot line, word by word

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 another transition (soft, card). A part without a transition of its own moves with spring. Lower a spring’s duration for a snappier feel, or raise bounce for a livelier one. There are no page transitions and nothing counts up.

Effect Where to change it
The Home hero’s photo grows on load, then scrolls at half speed HomeHeroSection.astro (animate-zoom-in, <Parallax>)
The hero’s words appear one by one <WordEffect> in src/components/sections/HomeHeroSection.astro (its delay and stagger); a plain element with the same class shows at once
The page titles’ photos and a post’s cover move at half the scroll <Parallax> in PageTitleSection.astro and PostArticleSection.astro
The header turns solid when the section after the photo reaches the middle of the screen src/components/site/header.ts; a section marks itself with headerSwitch on Section (data-header-switch)
Home shows four services, four stories and three posts service.count and stories.count in src/content/pages/home.json; slice(0, 3) in src/pages/index.astro
The Journal shows six posts, then six more as the visitor scrolls list.pageSize in src/content/pages/blog.json
A post ends with three related posts count in src/content/pages/post.json
The videos grow from 60 % and rise into place scale and y of <ScrollTransform> in src/design-system/components/media/VideoBand.astro
The footer rises 200 px into place at the end of the page <ScrollTransform y={[-200, 0]}> in src/components/site/Footer.astro
Home’s client story card stays pinned while the stories change src/design-system/components/patterns/StoryCards.astro and scripts/story-cards.ts
Client Stories’ cards stop at the top and the next slides over (CSS only) src/components/sections/TestimonialStoriesSection.astro

With “reduce motion” switched on in the visitor’s system, movement is left out: the header’s parts and the hero’s buttons fade in where they stand, the hero’s photo doesn’t zoom, the words fade in without rising, the parallax, the scroll zooms and rises stand still, and moves, turns and size changes jump. Fades and colour changes stay, and the videos still play. play() in src/design-system/utils/play.ts, which every script animates through, makes moves, turns and sizes jump; the CSS animations check the setting with motion-reduce:.

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; 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 (with the rolling label), the plus-minus box and the pricing switch, the logo and the icons, the scroll and word effects, the menu button and the social icons, the section layout and its label, the cards (post, price, service, team, testimonial), the numbers, the points and the client ratings, the rows (steps, questions, services), the plans, the lists that light up or load on scroll, the pinned stories, rich text, the images and the video band, 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 two icons (the Phosphor arrow and star) are stored as path data in src/design-system/components/icons/paths.ts; <Icon name="arrow-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 icons are image files (src/assets/images/icon-*.svg), listed with their links in socialLinks (src/content/pages/shared.json).