Skip to content
Sign inJoin waitlist

Design — Marai Neesu 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 font, 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 navigation, the layout, the cards, the status chip, the patterns (rich text, the tickers, the rolling roles, the accordion) and the forms with their 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-black: #050505; /* [Black] text, the filled buttons; Black 80/60/30/10/05/03 are black/80 … black/3 */
--color-grey: #9fa0a3; /* [Grey] meta text, small labels */
--color-accent: #fc5000; /* [Accent] the e-mail's hover copy, highlights */
--color-background: #f6f6f6; /* [Background] page */
--color-white: #ffffff; /* [White]; White 50/05/03 are white/50 … white/3 */
--color-available: #1fb514; /* the CV's "Available for work" dot */
--color-error: #ff2244; /* the Submit button's fill after a failed send, at 15% */
}

The names in brackets are the colour styles of the original Framer design. Each name becomes a Tailwind class: bg-black, text-grey, text-accent. Swap the hex values for your own palette and the site changes. Accent is the colour links and buttons turn under the pointer, the stars of the testimonials and the e-mail’s second copy: pick one that reads on the light Background. In the demo Black on Background reads at about 19 : 1 and Grey on Background only at about 2.4 : 1, which is why Grey is kept for small labels next to darker text (the place under the logo, the rolling roles); keep body text at 4.5 : 1 or more.

The shades of Black and White are opacity modifiers on a token, as in the Framer design: black/80 (Black 80) for leads and card text, black/60 for meta lines and placeholders, black/30 for the veil over a post’s cover, black/10 for dividers and field borders, black/5 and black/3 for card hairlines, surfaces and field fills, white/50 for the header’s blurred pills. They follow the palette when you change the colour.

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

Colour Where
The header’s background, faded by Motion as you scroll (rgba(246,246,246,…), the Background) src/components/site/Header.tsx
A few Motion hovers that animate a colour (rgba(5,5,5,…), the Black) the components in src/design-system/components/ that animate a colour
The social icons and tool logos keep their own colours public/images/
The browser icons src/app/icon.png, src/app/apple-icon.png
The swatches of the style guide repeat the hex values as text src/app/style-guide/tokens.ts

Search the code for rgba(5,5,5 and rgba(246,246,246 to find them: Motion can’t animate the colour mixes Tailwind writes for an opacity modifier, so those few values are written out.

The logo is the person: your photo, your name and your city, linking home (src/design-system/components/brand/Logo.tsx, fed by person in src/content/site.ts). On desktop it sits on a blurred white pill with a verified seal, and under the pointer its two lines change to “Back to” / “Homepage” and the seal to a back arrow (person.hoverLines). On tablets and phones it is the photo and the two lines on the bar, without the pill.

To make it yours, change person (the photo is public/images/avatar.png, 180 × 180). To use a drawn logo instead, replace the contents of Logo.tsx with your own <Image> or SVG and keep its props, so the header doesn’t change. The browser icons are src/app/icon.png and src/app/apple-icon.png (180 × 180).

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, with every weight: the displays and paragraphs are 400, the headings, labels, menu and buttons 500, and bold words in rich text 700. theme.css makes --font-manrope the site font (--font-sans).

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

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

A font that isn’t variable needs its 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.

src/design-system/tokens/text.ts holds the 15 text styles, named as in the original design:

Style Framer name Phone Tablet (md:) Desktop (lg:) Used for
display1 Display 01 38 52 64 The Home hero’s title
display2 Display 02 24 36 42 Page titles (a post’s title, the 404)
h1 Heading 1 24 26 28 An inner page’s <h1>
h2 Heading 2 22 24 26 Section titles
h3 Heading 3 20 22 24 Headings in a post, the custom-request row, the newsletter
h4 Heading 4 20 21 22 The course card’s title, the footer’s links
h5 Heading 5 18 19 20 Service, product, experience and question titles
h6 Heading 6 16 17 18 Project, post, tool, module and lesson titles
h6Small Heading 6 Small 14 14 14 The logo’s name, a CV line’s subtitle
big Big Paragraph 18 18 18 A post’s body, leads
paragraph Medium Paragraph 16 16 16 Descriptions, rich text, form labels, breadcrumbs
small Small Paragraph 14 14 14 Meta lines, chips, labels
tiny Tiny Paragraph 12 12 12 The place under the logo
menu Menu 13 13 13 The header’s links
button Button 12 12 12 Button labels, links with an arrow (upper case)

The displays are weight 400, the headings 500, all at line height 1.2; the paragraphs are 400 at 1.4 (big, paragraph) or 1.2 (small, tiny); menu is 500 with 0.03em letter spacing and button 500 in upper case (the copy stays mixed case). 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-black/60")}.

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 at most 1200 px wide. The side padding is 20 px on phones, 30 px on tablets and 40 px on desktops, sections have 40 / 50 / 50 px above and below and 50 px between their blocks (sectionGutters, sectionPadding and sectionGap in src/design-system/components/layout/Section.tsx), and a 1 px line (<Divider />) separates most sections. The fixed header is 74 px tall on phones, 84 on tablets and 92 on desktops; src/app/layout.tsx pads <main> by that (Pages and sections).

src/design-system/tokens/motion.ts holds the transitions measured on the original Framer components, for Motion:

Token Values Used for
spring (S1) spring 0.4 s, bounce 0.2 Nearly every hover: the buttons (the arrow turns 45°), the menu links, the logo, the social tiles, the product buttons, the post and tool cards, the Go Back button, the course modules. Also the default of every Motion element that sets none (MotionProvider).
springFlat (S2) spring 0.4 s, no bounce The header’s scroll look and the phone menu, the project, product and service cards, the questions
springRoll (S3) spring 0.5 s, no bounce The e-mail of the Home hero rolling to its orange copy
slideSpring (SL) stiffness 200, damping 40, mass 1 The rolling roles of the Home hero and the CV, the testimonial slideshow on phones
instant no duration A change the original makes at once (an underline snapping back)

theme.css holds the rest, in CSS: --ease-form (the colours of a form’s button, 0.2 s), --animate-turn (the button’s spinner, one turn a second) and the two ticker belts (--animate-ticker-x, --animate-ticker-y). Lower a spring’s duration for a snappier feel, or raise bounce for a livelier one.

Effect Where to change it
The testimonials move left at 10 px a second, 15 px apart (tablets and up) speed={10} and gapClassName on <Ticker> in src/components/sections/TestimonialsSection.tsx
On phones one testimonial at a time, moving on every 4 seconds, with two arrows src/components/sections/CardSlideshow.tsx
The client logos move left at 20 px a second speed={20} on <Ticker> in src/components/sections/ClientsSection.tsx
A service card’s photos roll at 5 px a second under the pointer (always on phones) src/design-system/components/cards/ServiceCard.tsx
The roles under the greeting change every 4 seconds interval on <WordRoll> (4 by default) in HomeHeroSection.tsx and CvSection.tsx; the roles are roles in home.ts and cv.ts
The first question of each FAQ starts open add defaultOpen to <Accordion> in src/components/sections/FaqSection.tsx (a list of row numbers from 0; [0] when left out, [] for none)
The first course module starts open defaultOpen={index === 0} in src/components/sections/CourseSection.tsx
The Blog shows six posts before “Load More” pageSize in src/content/pages/blog.ts
The desktop header steps aside after 4 px of scrolling down useScrolledDown in src/components/site/Header.tsx

With “reduce motion” switched on in the visitor’s system, the tickers stand still, the spinner stops, the questions and course modules open at once, and MotionProvider (wrapped around every page in src/app/layout.tsx) makes Motion skip its transform and layout animations; fades and colour changes stay. The rolling roles and the testimonial slideshow keep changing, as on the original, but jump instead of sliding.

Corners are 10 px on cards and their photos, 8 px on the experience, testimonial and question cards and the course image, 4 px on the product buttons, form fields and checkboxes, 2 px on the social tiles; buttons, chips, pills and avatars are round. The primary button lifts with a soft shadow stack; other surfaces are flat with a faint hairline. 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 logo, the icons, the cards (project, product, post, service, testimonial, course, course module, experience, tool, CV), the status chip, the breadcrumbs, the social tiles, rich text, the ticker, the rolling words, the accordion, the section layout and title, the form parts and two small utilities (the current year and a clock in a time zone). 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 14 icons (Phosphor shapes) 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" 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.