Skip to content
Sign inJoin waitlist

Editing the content — Metuo Next.js

All the words, images and videos of this Next.js template live in src/content/, in plain TypeScript files you edit while npm run dev shows the result.

No CMS is needed: text goes between quotes and items are separated by commas. If you would rather manage content in Sanity, Payload, Strapi or Directus, see Using a headless CMS.

src/content/
site.ts name, title, description, domain, menu, the "Book a session" button, contact details, socials, footer
pages/home.ts the copy of the home page
pages/about.ts …and of every other page
pages/shared.ts the founder, her quote, the call to action band and the client rating, shown on several pages
pages/pricing.ts the plans (Home, Service)
pages/faq.ts the questions (Home, Service, Contact, every post)
pages/book.ts the booking form (Home, Service, Contact)
collections/*.ts posts, legal pages, services, client stories (testimonials.ts) and the team
routes.ts the URL of every page
types.ts the fields each kind of item has

Not sure which file holds a piece of text? The page maps label every section of every page with its file.

src/content/site.ts holds what appears on every page:

Export Shown where
site.name The browser title suffix (“About | Metuo”), share cards, the logo link’s name for screen readers
site.title The browser title of Home, and of any page that sets none of its own
site.description Search results and share cards of Home (and of any page without its own description). It describes the template: write yours.
site.url Set this to your domain before publishing. Canonical links, share links, sitemap.xml and robots.txt are built from it.
navigation The header’s links (and the phone menu): Home, About, Services, Stories, Journal. The footer’s Quick links are the same list.
bookLink “Book a session”: the header’s button, the phone menu’s and the footer’s (it opens /contact)
contact E-mail, phone and address, with their labels (“Email:”, “Phone:”, “Location:”): the footer’s Contact column. The e-mail is also the “send us an email” link of the call to action band and the “Contact support” button of the questions.
socials The social links: their names in the footer’s Social media column, their icons (icon, a file in public/images/) in the call to action band and the booking section
footer The footer: the line under the logo (about), the titles of its three columns (contactLabel, quickLinksLabel, socialLabel), the copyright line (note, where {year} becomes the current year), the legal links (legalLinks) and the photo behind it (image)

The demo’s e-mail (hello@example.com), phone number and London address are placeholders: replace all three. The phone’s link is built from the number ((555) 123-4567 calls tel:5551234567), so write it the way people should read it, with your country code if visitors call from abroad. The social links open the networks’ home pages: point them to your own profiles, and remove the ones you don’t use.

Links that start with https:// open in a new tab in the footer; mailto: and tel: links open the visitor’s mail app or phone; links inside the site (/contact) open in the same tab.

The practice’s name, its founder and its town appear in many places: site, the footer’s note, the copy of every page, the founder (shared.ts), the client stories and the legal pages. The logo draws the name too (Making it look like your brand). Search src/content/ for “Metuo”, “Amelia” and “London” to find them all.

There is one file per page in src/content/pages/. Each exports the blocks of that page and, for most pages, a meta entry:

export const meta = {
title: "About", // browser tab: "About | Metuo"
description: "Meet Metuo: our vision and mission, …", // search results and share cards (80–160 characters)
};
export const pageTitle = {
title: "About Metuo",
lead: "Helping you build clarity, confidence, …",
image: { src: "/images/about-hero.jpg", alt: "…" },
};

Change the text between the quotes, keeping the field names: the sections read them by name. Apostrophes are safe inside double quotes, and the demo uses both ’ and the typographic ’. A double quote inside a double-quoted string needs a backslash before it (the founder’s quote and the client stories are written that way, with their quotation marks).

File Page
home.ts Home: the hero (hero: the “Available for treatment” pill, the title, the text, “Start your journey” and “Explore programs”, the line and the place at its foot, the photo), “About us” (about: the title, two paragraphs, “Learn more about us”, the small photo and “What we believe” with four points), the intro of “How we can help” (service, with count, how many services show), “Why choose us” (why: four points and four photos), “Our process” (step: four steps and two photos), the video, the intro of “Client stories” (stories, with count, how many stories the card turns through), the four figures (stats) and the intro of “Our journal” (blogIntro). Home has no meta: its title and description are site.title and site.description.
about.ts About: the photo title (pageTitle), “Vision & Mission” (vision: two cards, the line “We’ve Got Something For Everyone.” with “Book a session”, two photos), “Our core values” (values: five points and five photos), the video and the intro of “Meet the team” (teamIntro)
service.ts Service: the photo title; facts are the figures under the services, the same object as Home’s stats
testimonial.ts Testimonial: the photo title, the name of the list for screen readers (storiesLabel) and “Key Outcomes:” (outcomesLabel)
blog.ts Blog: the photo title and the list (list: its name for screen readers, pageSize, how many posts show at a time, and what screen readers hear while more load)
post.ts Every post page: “More insights for you.” (related: the label, the title, the text and count, how many related posts show)
contact.ts Contact: its title and description only. The page itself is the booking form (book.ts) and the questions (faq.ts).
legal.ts Every legal page: “Last Updated:” (updatedLabel) and the search description of each page by its slug (descriptions; a page missing there gets fallback)
not-found.ts The 404 page: its browser title, the title, the text and “Back to homepage”
shared.ts The founder, her quote, the client rating, the e-mail line and the call to action band (below)
pricing.ts The plans (below)
faq.ts The questions: the intro, the “Still have questions?” card (its person, photo and “Contact support”) and six questions with their answers (the first starts open)
book.ts The booking form: the intro, “Tell us about you.” and the fields (Forms)

The four figures (“500+ Individuals Supported”, …) are written once, in stats in home.ts, and show on Home and on the Service page. They are plain text: nothing counts up.

src/content/pages/shared.ts holds the parts that several pages show from one copy:

  • founder: the founder’s name, role, round portrait (avatar), long photo and bio. The photo and the bio make the founder card of Home’s “About us” (its “+” shows the bio); the name, role and portrait sit under her quote.
  • founderQuote: the dark band with the founder’s quote over a photo: Home, About and Service.
  • ctaBand: “Ready to take the first step toward a more fulfilling life?”, its text, “Book a consultation” and the trust line (“Trusted by 500+ clients…”). Shown at the end of Home’s “Why choose us”, About’s team, Testimonial and Blog; the trust line also sits beside the booking form.
  • clientRatings: the four client photos, the “65+” bubble, “4.9/5 Average Rating” and the stars’ name for screen readers: in the call to action band and beside the booking form.
  • questionLine: “Have a question before you begin? Reach out anytime through send us an email, …”, in two parts around the e-mail link: in the same two places.
  • bioLabel: the name screen readers hear for a “+” button (“Bio of Olivia Bennett”).

src/content/pages/pricing.ts holds the pricing section of Home and Service: the intro, the switch (billing: “Monthly”, “Yearly”, “(32% off)”, its name for screen readers and the “/month”, “/year” after the prices), “Includes:”, “* Perfect for:”, the three plans and the line under them with its “Contact us” link (more).

{
name: "Growth",
description: "A balanced plan offering consistent support …",
monthly: "$249", // shown with "/month" while the switch is on Monthly
yearly: "$2,029", // shown with "/year" on Yearly; any text
includes: ["4 × 60-Minute Private Coaching Sessions", …], // the dotted list under "Includes:"
perfectFor: "Building confidence, achieving goals, …", // after "* Perfect for:"
featured: true, // the dark Green card; leave it out on the others
cta, // "Get started", to /contact
}

The discount next to “Yearly” is text: change it when your prices change. The layout is made for three plans (three columns on desktops; on tablets the second plan spans two rows beside the others).

src/content/collections/ holds the lists the site builds pages and sections from:

File What it feeds
posts.ts Blog (every post, six at a time), one page per post, Home’s “Our journal” (the first three) and “More insights for you.” under a post (up to three other posts of the same category)
services.ts The rows of “How we can help” on Home (the first four: service.count in home.ts), the cards of the Service page (every service, numbered) and the “Preferred session type” checkboxes of the booking form (every service’s name)
testimonials.ts The client stories: the card on Home (the first four: stories.count) and the Testimonial page (every story)
team.ts The team cards on About
legal.ts One page per legal text, at /legal/<slug>

The order of the items in the file is the order on the site. Nothing is sorted by date: the demo lists the posts newest first, so put a new post first to show it first on Blog and Home. Blog shows six posts at first and six more each time the visitor scrolls near the end of the list; every post is in the page’s HTML from the start, so search engines find them all.

Copy an existing entry, paste it where it should appear, and change the values:

{
"slug": "finding-calm-in-busy-weeks", // the URL: /blog/finding-calm-in-busy-weeks
"title": "Finding calm in busy weeks", // the card, the page's title and its browser title
"excerpt": "Small daily habits that keep stress from taking over.", // under the title on the page, in search results
"image": "/images/post-finding-calm-in-busy-weeks.jpg", // the card's photo and the page's cover
"imageAlt": "…", // the cover's description for screen readers
"category": "Mindset", // the card and the page's label; related posts share it
"date": "2026-06-02", // shown on the cards as "Jun 2, 2026"
"body": [ // the article: rich text, below
{ "type": "paragraph", "text": "First paragraph." },
{ "type": "heading", "level": 3, "text": "A heading" },
{ "type": "paragraph", "text": "Another paragraph." }
]
}

The quotes around the field names come from the way the files are generated; they are optional in TypeScript, so keep them or leave them out.

A post page shows “// category”, the title and the excerpt, the cover photo, then the article. “More insights for you.” follows with up to three other posts of the same category, in the file’s order; the block is left out when the category has no other post. The questions close the page.

category is plain text: “Growth”, “Mindset” and “Coaching” in the demo. Write it the same way on every post of a category, since related posts match it exactly. An excerpt shorter than 80 characters is followed in search results by the start of the article, so the description is long enough (describe in src/lib/format.ts).

{
"slug": "family-counselling", // an identifier (services have no page of their own)
"name": "Family counselling", // the row's and card's title, the booking form's checkbox
"summary": "Support for families …", // under the title when the row is open, on the card
"image": "/images/service-family-counselling.jpg", // the big photo
"images": ["/images/service-family-counselling-1.jpg", "/images/service-family-counselling-2.jpg"], // the two small ones
"imageAlts": ["…", "…", "…"], // descriptions of the three photos: big, first small, second small
"values": ["…", "…", "…", "…"] // the bulleted list of the open row and the card (four in the demo)
}

On Home a service is a row that opens one at a time, showing its summary, its values and its photos (beside the rows on desktops, inside the row on tablets and phones). On the Service page every service is an open card with its number.

{
"slug": "anna-lee",
"name": "Anna Lee",
"role": "Teacher",
"photo": "/images/client-anna-lee.png", // the small portrait beside the name
"headline": "Learning to slow down", // the story's title
"quote": "\"…\"", // the client's words, with their quotation marks
"image": "/images/story-anna-lee.jpg", // the big photo beside the story
"imageAlt": "…",
"outcomes": ["…", "…", "…"] // "Key Outcomes:" on the Testimonial page (three in the demo)
}

Home’s card turns through the first four stories as the page scrolls past it (without the outcomes); the Testimonial page shows every story as a full-screen card, with its outcomes.

{
"slug": "maya-brooks",
"name": "Maya Brooks",
"role": "Wellness Coach",
"photo": "/images/team-maya-brooks.jpg", // a portrait, shown at 2 : 3
"bio": "…" // shown over the photo when the "+" is pressed
}

The cards sit three to a row on desktops, two on tablets, one on phones. The founder on Home is not a team member: she is founder in shared.ts.

legal.ts holds Terms of Service and Privacy Policy: a slug (the URL, /legal/terms-of-service), a title, the date of the last update (updated, shown as “Last Updated: Dec 18, 2023”) and the text (body, rich text). The texts are samples with [Your Company Name] and [URL] where your details go: have them checked for your practice and country.

The footer’s legal links are written in footer.legalLinks in site.ts, not built from the collection: add a link there when you add a legal page.

Delete the entry. A post’s or legal page’s own page and its sitemap entry disappear on the next build. Before you remove a legal page, remove its link from footer.legalLinks.

src/content/types.ts is the reference: it lists every field, which are optional (?), and a comment for the ones that are not obvious. Your editor shows the same information while you type.

A post’s body and a legal page’s body are a list of blocks:

body: [
{ "type": "heading", "level": 3, "text": "Why Self-Awareness Matters" },
{ "type": "paragraph", "text": "**Journaling**\nWriting down your thoughts and feelings can help you …" },
{ "type": "list", "ordered": false, "items": [
[{ "type": "paragraph", "text": "What triggers my stress?" }],
[{ "type": "paragraph", "text": "Which habits support my goals?" }]
] }
]
  • Headings are drawn in the Heading 3 style, in Green (level is kept from the CMS; every heading looks the same).
  • Paragraphs are plain text with three marks: words between double asterisks are bold (**…**), words between single ones are italic (*…*) and \n starts a new line inside a paragraph.
  • Lists are bulleted ("ordered": false) or numbered ("ordered": true); each item is its own list of blocks, usually one paragraph.

There are no links or images inside the text.

  1. Put the file in public/images/.
  2. Refer to it in the content as /images/<file> (the path starts at public).

Sizes and formats are handled for you: pages use next/image, which serves a scaled, modern format per device. The download’s placeholders show the size of each demo photo; use photos at least as large (larger is fine where the demo’s are small):

Photos Demo size Frame
The Home hero (hero.image) 2400 × 1600 Fills the window (80 % of its height on tablets), cropped
The photo titles of About, Service, Testimonial and Blog (pageTitle.image) 2400 × 1600 Full width, about 80 % of the window’s height, cropped
The founder quote’s background (founderQuote.image) 2400 × 1600 Full width behind the dark band
The footer’s background (footer.image in site.ts) 2400 × 3600 Full width behind the footer card
Home “About us”: the small photo and the founder card (about.image, founder.photo) 1080 × 1620, 1000 × 1501 2 : 3 (150 × 225 on desktops); about 520 : 737
“Why choose us” and “Our core values” (four and five photos) 1040 × 693 (one 2400 × 1600) Square, up to 520 px; a moving strip on phones
“Our process” and “Vision & Mission”: the tall photo and the one over it 1090 × 1636, 1310 × 873 Tall (about 0.69 : 1); 3 : 2
A service’s image and images 800 × 533 and 400 × 267 (some smaller) The big one 400 × 500 on Home’s desktop rows, 320 px wide on a card; the small ones 3 : 2
A client story’s image 1140 × 760 Up to 570 px wide on Home’s card, 520 px on the Testimonial page
A client story’s photo 200 × 300 Small portrait, up to 100 px
A post’s image 2280 × 1520 367 : 244 on cards; full width (up to 1140 px) and about 80 % of the window’s height on its page
A team member’s photo 750 × 1125 2 : 3
The client photos of the rating (clientRatings.avatars) 100 × 100 Round, 42 px
The founder’s portrait and the support person of the questions 120 × 120 Round, 54 px

Photos in a fixed frame are cropped to fill it, so a photo of other proportions works, but you lose the edges the frame cuts. Frames that follow the screen change shape between phone, tablet and desktop, so keep the subject away from the edges.

Every photo comes with a short description for screen readers and search engines: alt in { src, alt }, or the imageAlt / imageAlts fields of the collections. Write one for each photo you change (an empty alt: "" marks a photo as decoration, like the footer’s). The photos of post cards and the client portraits are decorative on purpose: the title or the name next to them already says what they are.

The social icons are SVG files (public/images/icon-facebook.svg, …), named in socials in site.ts: replace a file, or point icon at another one. public/images/logo.png (Green) and logo-white.svg are copies of the logo for use elsewhere; the site draws its logo from the design system (Making it look like your brand).

Three things sit outside the content because browsers and social networks ask for them by name:

File What it is
public/icon-light.svg, public/icon-dark.svg The icon in the browser tab: the Green leaf for a light browser theme, a light one for a dark theme (the file names are set in src/app/layout.tsx)
src/app/apple-icon.png The icon on a phone’s home screen (180 × 180)
public/opengraph-image.png The picture shown when someone shares a link (2400 × 1260; 1200 × 630 or larger)

The share image’s description for screen readers is shareImage.alt in src/lib/meta.ts, next to its size: change width and height there if your image has another size, and write a description of your own (the demo’s calls the site a template). Every page uses this image when shared, except a post, which shares its own cover photo.

Two videos play on the site, muted and in a loop, without controls:

Video Where it plays Field
Home video Home, between the plans and the client stories; it grows into place as you scroll video.src in src/content/pages/home.ts
About video About, between the values and the team video.src in src/content/pages/about.ts

The demo plays two stock clips from the Pexels website (Pexels License); they are not part of the download and stop working if Pexels moves them, so replace them. Put an MP4 in public/videos/ and set src: "/videos/home.mp4", or use a web address of your own. The frame is 16 : 9 (a video of other proportions is cropped); export at about 1280 px wide and keep each file small (a few MB). A video loads only when it first comes into view and plays only while it is on screen.

Almost every word is content, including the form’s messages (book.ts). The few interface words that never change per site live in the code:

  • “Main” (the menu’s name for screen readers) and “Menu” (the phone menu button’s label) in src/components/site/Header.tsx;
  • the date format of the post cards (“May 28, 2026”) in src/lib/format.ts;
  • the page’s language, lang="en", in src/app/layout.tsx.

Search for the word and you will find it.

Terminal window
npm run build

A successful build means every content file has the fields it needs and every page still renders. It doesn’t check that the images exist, that a post’s category matches another post’s, or that links written as text ("/contact") lead somewhere: click through the site once with npm start after big changes. See Going live for the rest of the checklist.