Design — Lookis 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 springs and
timings, the buttons and links, the logo and the icons, the menu button, the section layout, the cards, the numbers,
the patterns (the ticker, the slideshow, the gallery, the questions, the list that loads on scroll, rich text) 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; /* text, the black buttons and the Submit button, label dots */ --color-line: #ececec; /* dividers, card and field borders, the line under the header */ --color-paper: #fafafa; /* the page, the header, the footer card, text on photos, the white button */ --color-spinner: #999999; /* the ring of the loading spinner */ --color-error: #ff2244; /* the Submit button's error label */ --color-error-fill: rgb(255 34 68 / 0.15); /* the Submit button's fill after a failed send */}Each name becomes a Tailwind class: bg-ink, text-paper, border-line. Swap the hex values for your own palette and
the site changes. The template is black on near-white: Ink on Paper reads at 20 : 1. If you change Paper to a dark
colour, change Ink to a light one, because the white button, the text over the photos and the cards use the same two
tokens. Keep text on its background at 4.5 : 1 or more, or the site becomes hard to read. The error red on Paper is
3.6 : 1, the original design’s colour; a darker red reads better.
Faded blacks are opacity modifiers on Ink, as in the original design:
| Class | Used for |
|---|---|
ink/80 |
Roles, answers, prices, a section label |
ink/60 |
The footer’s column labels |
ink/50 |
Question numbers, a focused field’s border, the Submit button’s hover, the veil over the testimonials photo |
ink/30 |
Outlined circles and pills, the placeholders of the form |
ink/20 |
The slideshow’s arrows |
ink/2 |
The cards’ fill: numbers, awards, services, the contact form, the tinted “See what I do” band |
They follow Ink when you change it. On Paper, ink/60 reads at 5.7 : 1, ink/50 at 3.9 : 1 and ink/30 at 2.1 : 1.
A few colours sit outside the tokens, so change them too when you change a colour:
| Colour | Where |
|---|---|
| The browser icons: a light and a dark version | public/icon-light.png, public/icon-dark.png, src/app/apple-icon.png |
| The logo file for use elsewhere (black) | public/images/logo.svg |
| The slideshow’s arrows: a white chevron | src/design-system/components/patterns/TestimonialSlider.tsx |
| The swatches of the style guide repeat the hex values as text | src/app/style-guide/tokens.ts |
The “Daniel Mercer” wordmark, on two lines, is drawn as an SVG path in
src/design-system/components/brand/Logo.tsx, in the current text colour (black in the header). To use your own:
- As an SVG: replace the
wordmarkstring with your logo’s path data, and set theviewBox="0 0 330 162"and theaspect-[330/162]class to your artwork’s size. - As an image file: replace the
<svg>with an<Image>of your file.
It is 72 × 35 px from tablets up and 62 × 30 on phones: change w-[72px] and w-[62px] 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. The same artwork is in public/images/logo.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 Inter once, through next/font in src/app/layout.tsx:
const inter = Inter({ variable: "--font-inter", subsets: ["latin"], axes: ["opsz"],});Inter is one variable font here: every weight and its optical-size axis. The text styles pin that axis to 14, Inter’s
text cut, written as [font-variation-settings:'opsz'_14] in src/design-system/tokens/text.ts. theme.css makes
--font-inter the site font (--font-sans). Only Inter’s upright style is loaded: the italic phrases of the projects
and services are the browser’s slanted version of the regular text; add style: ["normal", "italic"] to the call to
load the real italic.
To use another Google font, import it by name from next/font/google and keep the variable name:
import { Manrope } from "next/font/google";const inter = Manrope({ variable: "--font-inter", subsets: ["latin"] });Leave out axes: ["opsz"] unless the new font has an optical-size axis: Next.js stops with an error otherwise. Without
the axis, the font-variation-settings in the text styles simply do nothing. Everything is set in weight 400, except
the hero’s name ticker and the header’s clock (500) and the bold words of rich text (700); a font that isn’t variable
needs those weights listed (weight: ["400", "500", "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.
Text styles
Section titled “Text styles”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 |
60 | 100 | 150 | The name that runs across the Home hero |
h1 |
30 | 40 | 54 | Page titles |
h1Small |
24 | 26 | 28 | The hero’s introduction |
h2 |
28 | 38 | 48 | Section titles, the big numbers |
h3 |
26 | 30 | 36 | About’s block titles, the contact card’s title, “Overview”, “Perfect for” |
h4 |
22 | 26 | 30 | The price of a service page, “404” |
h5 |
20 | 24 | 28 | Card and row titles, questions, the footer’s “Let’s Connect” |
h6 |
20 | 22 | 24 | Quotes, award titles, numbered rows |
big |
18 | 18 | 18 | Leads, descriptions, rich text, prices, the footer’s links |
paragraph |
16 | 16 | 16 | Card text, roles, small print |
menu |
16 | 16 | 16 | The header’s links and clock, button labels |
label |
12 | 12 | 12 | The upper-case labels with a dot above section titles |
Everything is Inter at weight 400 with no letter spacing (display is 500). The headings have a line height of 1.1
(h1Small, h4, h5 and h6 1.2), the 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-paper")}.
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: |
Sections run the full width of the window; a few blocks (Home’s “About me”, “My numbers” and “My Services”) stop at
1440 px, and the two-column pages at 1728 px. The side padding is 10 px on phones, 20 px on tablets and 30 px on
desktops, and most sections have 40 / 60 / 80 px above and below and 50 px between their blocks (sectionGutters,
sectionPadding and sectionGap in src/design-system/components/layout/Section.tsx). The header sticks to the top,
70 px tall on phones and 95 px from tablets up (Pages and sections).
Motion
Section titled “Motion”src/design-system/tokens/motion.ts holds three springs, for Motion, and the timings of the template:
| Token | Values | Used for |
|---|---|---|
spring (S0) |
no bounce, 0.4 s | Nearly every hover and change: the buttons’ rolling label, the links, the phone menu and its button, the project cards’ cover, the service rows dimming, the hero’s words |
springSoft (S2) |
bounce 0.2, 0.4 s | The questions opening, the Portfolio cards moving after a filter, the gallery tiles, the arrow circles, the footer’s links dimming |
slideSpring (SL) |
stiffness 200, damping 40 (about 1.35 s) | The testimonial slideshow’s step |
hoverDelay |
500 ms | The second stage of a link’s hover: the solid underline, the arrow’s turn |
wordStagger |
0.05 s | The hero’s words appearing one after the other |
slideInterval |
4000 ms | The slideshow moving on |
nameTickerSpeed |
30 px a second | The name running across the hero |
filterDelay |
420 ms | Portfolio: the cards move this long after a tab is pressed |
theme.css holds S0 and S2 as CSS curves for what runs without Motion (--ease-s0, --ease-s2, run over 400 ms), and
--ease-form for the Submit button’s colours (0.2 s) and the spinner’s fade (0.3 s). 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.
The template has no scroll animations and no page transitions: the hero’s words are the only animation on load.
| Effect | Where to change it |
|---|---|
| The name runs across the hero at 30 px a second, 30 px between the copies | nameTickerSpeed in tokens/motion.ts; gapClassName on <Ticker> in src/components/sections/HomeHeroSection.tsx |
| The hero’s introduction appears word by word | <WordAppear> in HomeHeroSection.tsx (wordStagger); a plain <p> with the same className shows at once |
| The slideshow moves every 4 s | slideInterval in tokens/motion.ts |
| Portfolio shows four projects, then four more as the visitor scrolls | pageSize in src/components/sections/PortfolioProjects.tsx |
| Home shows six projects | projects.count in src/content/pages/home.ts |
| The Home hero and the 404 photo are as tall as the window (80 % on tablets) | h-svh md:h-[80svh] lg:h-svh in HomeHeroSection.tsx and NotFoundSection.tsx |
| Every question on Services starts closed and opens on its own | src/design-system/components/patterns/FaqList.tsx |
Reduced motion
Section titled “Reduced motion”With “reduce motion” switched on in the visitor’s system, movement is left out: the name ticker and the spinners stand
still, the hero’s words fade in without rising, the slideshow doesn’t move by itself and changes without sliding, the
questions open at once, and hover transitions happen without animation. Fades and colour changes stay.
MotionProvider makes Motion skip its transform and layout animations; the ticker, the spinners and the hover
transitions check the setting in CSS (motion-reduce:), and the slideshow and the questions check it themselves.
Corners, spacing, shadows
Section titled “Corners, spacing, shadows”Corners are 10 px on photos, project frames, cards, gallery tiles and the hero, 4 px on the form fields, the Submit
button, the service rows’ photos and the testimonial portraits, and round on buttons, pills and arrow circles. 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 box that opens and closes, the
cards (project, service row, service card, testimonial, award), the numbers and the numbered lists, rich text, the
ticker, the slideshow, the gallery, the word-by-word text, the list that loads on scroll, the questions, the menu
button, the section layout and the two-column page shell, 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-up-right (links, service rows and cards, awards) and plus (the questions), are
Phosphor shapes 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:
-
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.