Skip to content
Sign inJoin waitlist

Editing the content — Catchup Next.js

All the words and images 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 Contact button, social links, booking link,
e-mail and phone, the footer
pages/home.ts the copy of the home page
pages/about.ts …and of every other page
collections/*.ts work, services, testimonials, posts and legal pages
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. (The first line of each collection file says it was extracted from the live site and is synced from another folder: that note is about how the demo content was made. In your copy, these files are the content: edit them.)

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

Export Shown where
site.name The browser title suffix (“About | Catchup”), share cards, the name of the logo links for screen readers
site.title The browser title of a page that sets none of its own (every page of the demo sets one; Home’s is meta.title in home.ts)
site.description Search results and share cards of any page without its own description (the 404 page). 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, Studio, Works, Services, Insights
headerAction The mint “Contact” button at the right of the header
socials The social links: the footer’s Connect column and “Follow Us” on Contact
contact The e-mail (Contact page and the footer’s “Email Us”) and the phone (Contact page)
bookingHref The “Book a 15-min call” button of the footer
footer The footer: its line (text), the button’s label (action.label; it opens bookingHref), the four column titles (sitemapLabel, servicesLabel, worksLabel, connectLabel), the Sitemap links (sitemap), the label of the e-mail link (emailLabel) and the copyright line (note, where {year} becomes the current year)

The footer’s Services and Recent Works columns list every service and every project, and its bottom row lists the legal pages: they come from the collections, so they follow when you add or remove an item.

The demo’s e-mail (hello@example.com) and phone number are placeholders: replace both. The phone’s link is built from the number (+1 (347) 555-0123 calls tel:+13475550123), so write it the way people should read it, with your country code. The social links open the networks’ home pages: point them to your own profiles.

“Book a 15-min call” opens https://cal.com/ in the demo, in two places: bookingHref in site.ts (the footer) and serviceItemPage.pricing.action in src/content/pages/services.ts (every service page). Put your booking page (or /contact) in both.

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

The studio’s name appears in more places than site: the copy of Home, About, Work, Services, Blog and Contact, the footer’s copyright and the legal pages. The logo draws it too (Making it look like your brand). Search src/content/ for “Catchup” to find them all.

There is one file per page in src/content/pages/. Each exports an object with the blocks of that page and, for the pages that have their own address, a meta entry:

export const about = {
meta: {
title: "About", // browser tab: "About | Catchup"
description: "Catchup is a creative agency for…", // search results and share cards (80–160 characters)
},
hero: { title: "About", subtitle: "We Don’t Just Create — We Craft with Purpose", … },
…
};

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 the typographic ’. A double quote inside a double-quoted string needs a backslash before it.

File Page
home.ts Home: the hero (the tag, the title, the text and two buttons), the title over the client logos, “About Us” (the heading, the five numbers with their photos, “Core Values” with its button and photo), “What We Do” (the heading, the button and the mint call-to-action card with its two photos), “Our Work”, “Testimonials”, the call to action with its photo, and “News & Insights”. Its meta.title is the whole browser title, without the suffix.
about.ts About: the title with the subtitle, the text, the clients’ count and rating and the wide photo; “Our Philosophy” (vision, mission, the button, two photos, four numbers); “Our Process” (four steps); “Awards” (the column titles, four awards and two photos); “Teams” (three people with their photos and social handles)
work.ts Work (workPage): the title, the years, the text and “Start a Project”; and the fixed words of every project page (workItemPage: “Introduction”, “Details”, “Credits”, “The Challenge”, “Our Solution”, “The Outcome”, “Other works”)
services.ts Services (servicesPage): the title, the tagline, the text, “Start a Project”, “What’s Included:” and “Learn More”; and the fixed words of every service page (serviceItemPage: “What We Offer”, the deliverables’ heading, the square image beside the offer, “Pricing Options”, the switch’s two labels, “What is included”, “Starting at :”, “Book a 15-min call”, “More Services”)
blog.ts Blog: the title, the short line, the lead, how many posts load at a time (pageSize) and what screen readers hear while more load
post.ts The fixed words of every post: the breadcrumb’s “Blog”, “Posted at”, “Posted on” and “More Blog”
contact.ts Contact (contactPage): the title, the text, the labels of the e-mail and phone, the location, the hours, “Follow Us” and the consent line under the button with its two links; and the form itself (contactForm, Forms)
legal.ts The fixed words of every legal page: “Last updated:”
not-found.ts The 404 page: its browser title, “404 Error”, the heading, the text and the button

Home and About each have their own numbers: about.brands, about.years, about.engagement, about.satisfaction and about.projects in home.ts, and philosophy.stats in about.ts. A number counts up from start to value once it is in view; decimals sets the digits after the point (4.9) and suffix the unit (“+”, “%”, “★”). Change both pages when your numbers change, and About’s clients’ count (hero.count, “65+”) too.

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

File What it feeds
work.ts Work (every project), one page per project, Home’s hero slideshow, its client logos, its intro photos and “Our Work” (every project), “Other works” at the end of a project page (the first two others in the file), the footer’s Recent Works
services.ts Services (every service), one page per service, Home’s “What We Do” (every service), “More Services” at the end of a service page (every other service), the service tags of the project cards, the footer’s Services
testimonials.ts Home’s testimonials (every one) and the clients’ faces in “About Us”, the four faces under About’s title, the client beside each plan of a service page, the quote at the end of a project page
posts.ts Blog (every post, newest first), one page per post, Home’s “News & Insights” (the three newest), “More Blog” at the end of a post (up to two more of the same category)
legal.ts One page per item (Terms of Service, Privacy Policy), the footer’s bottom row, the consent line of the Contact form

Projects, services and testimonials appear in the order of their file. Posts are sorted by date, newest first, so their place in the file doesn’t matter.

Home’s layouts are drawn for the demo’s numbers: “What We Do” puts the first three services in a row and the fourth beside the call-to-action card (any others follow it), so keep at least three services; the testimonials run in two rows on desktops, the first half of the list and the second, and tablets and phones show the first half in a carousel.

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

{
slug: "atlas-coffee-roasters", // the URL: /work/atlas-coffee-roasters
title: "Atlas — Coffee Roasters", // the card, the hero slide, the page's title and its browser title
client: "Atlas", // "Client :" on its page, the footer's Recent Works, the logo's name
summary: "A warm identity and a shop that tripled online orders.", // the card, the page's introduction, search results
image: { src: "/images/work-atlas.jpg", alt: "…" }, // the hero slide, the card, the page's wide photo
logo: { src: "/images/logo-atlas.svg", alt: "Atlas logo" }, // the logo row on Home, over the page's photo
services: ["branding", "development"], // slugs of services in services.ts: the tags and "Services :"
year: "2026",
timeline: "10 Weeks",
credits: [{ role: "Creative Director", name: "…" }, …], // "Credits": role : name, up to four in the demo
challenge: { title: "…", text: "…", gallery: [photo, photo] }, // "The Challenge": exactly two photos
solution: { title: "…", text: "…", gallery: [photo, photo, photo] },// "Our Solution": exactly three photos
outcome: { title: "…", text: "…", gallery: [] }, // "The Outcome": no photos
}

A project page shows the title, the introduction, the Details and Credits tables and the wide photo with the client’s logo; then The Challenge with its two portrait photos, Our Solution with a wide photo over two smaller ones, The Outcome with the client’s quote, and “Other works” (the first two other projects in the file). The galleries are drawn for those counts: The Challenge shows its photos only when it has two, Our Solution only when it has three; extra photos are left out.

services must hold the slugs of services, written exactly. The quote under The Outcome is the testimonial whose work is the project’s slug (below); without one, the line and the quote are left out.

{
slug: "motion", // the URL: /service/motion; also what projects list in `services`
name: "Motion", // cards, the footer, the label of its page, the browser title
summary: "Animation that gives your brand a pulse.", // the cards' text
thumbnail: { src: "/images/service-motion-thumb.jpg", alt: "…" }, // the square photo of the cards
image: { src: "/images/service-motion.jpg", alt: "…" }, // the wide photo of its page and of the Services list
overview: { title: "…", text: "…" }, // its page's big title and the paragraph under it (also search results)
offer: { title: "…", text: "…", includes: ["…", …] }, // "What We Offer" and the deliverables, eight in the demo
pricing: {
title: "Choose the Engagement Model That Fits Your Business",
project: { price: "$2,500+", includes: ["…", "…", "…", "…"], notes: ["*Clear scope", "…", "…"], testimonial: "lena-f" },
monthly: { price: "$1,200", includes: [ … ], notes: [ … ], testimonial: "clara-v" },
},
}

The Services page lists every service with its first four deliverables; its page shows them all, under “Our Motion Deliverables Include:”. Any number works; delete a line you don’t need rather than leaving it empty (an empty "" still shows its check mark).

Each plan is one side of the Per Project / Per Month switch: the price (“Starting at :”), four lines under “What is included”, three small notes (write the leading * yourself, as the demo does) and a client: testimonial is the slug of a testimonial, whose photo, name, role, stars and quote stand beside the plan. The switch changes the plan and the client together. A plan whose testimonial matches no testimonial stops the build with Unknown testimonial "<slug>".

{
slug: "clara-v", // an id: what plans name in `testimonial`
name: "Clara V.",
role: "Co-founder at Liva",
photo: { src: "/images/client-clara-v.jpg", alt: "Portrait of Clara V." },
rating: 5, // the stars, 1 to 5
quote: "“…”", // write the quotation marks yourself, as the demo does
work: "liva-beauty-skincare", // optional: the project whose page ends with this quote
}

Testimonials have no pages of their own. About shows the first four faces (hero.faces in about.ts) before the clients’ count.

{
slug: "a-brand-in-five-days", // the URL: /blog/a-brand-in-five-days
title: "A Brand in Five Days",
category: "Branding", // Branding, Design, Development or Photography
date: "2026-06-12", // shown as "Jun 12, 2026"; also the order of the list
excerpt: "What a design sprint can and can't do for a young company.", // the card, under the title, search results
image: { src: "/images/post-a-brand-in-five-days.jpg", alt: "…" }, // the card and the cover
content: [ … ], // rich text, below
}

The four categories are the type PostCategory in src/content/types.ts: add a word there to use a new one. A post ends with “More Blog”, up to two more posts of the same category, newest first; the block is left out when the category has no other post. The Blog page loads four posts at a time (pageSize in blog.ts) as the visitor scrolls; every post is in the page’s HTML from the start, so search engines find them all.

{
slug: "privacy-policy", // the URL: /legal/privacy-policy
title: "Privacy Policy",
date: "2026-06-01", // "Last updated:"
content: [ … ], // rich text, below
}

The demo’s two pages are sample text with the demo studio’s name and e-mail filled in. They are not legal advice: replace them with your own terms and policy. The consent line under the Contact form links the pages whose slugs are terms-of-service and privacy-policy (consent in src/content/pages/contact.ts): change those slugs there if you rename the pages.

Delete the entry. Its page and its sitemap entry disappear on the next build, and it leaves the lists and the footer. Before you remove a service, take its slug out of the projects’ services; before you remove a testimonial, check that no plan names it.

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 and a legal page’s content is a list of blocks:

content: [
{ type: "paragraph", text: "A paragraph with **bold** words, an *italic* phrase and [a link](/contact)." },
{ type: "heading", level: 3, text: "1. Photography Sets the First Impression" },
{ type: "list", ordered: false, items: [
[{ type: "paragraph", text: "First point" }],
[{ type: "paragraph", text: "Second point" }],
] },
{ type: "quote", text: "A quotation set apart from the text." },
]
  • Paragraphs take three marks: words between double asterisks are bold (**…**), words between single asterisks italic (*…*), label is a link (an https:// link opens in a new tab), and \n starts a new line. Manrope has no italic cut, so an italic phrase is the browser’s slanted version of the regular text.
  • Headings all look the same (Heading 3) whatever their level, as in the original design.
  • Lists are bulleted, or numbered with ordered: true; each item is a short list of blocks, usually one paragraph.
  • Quotes are supported by the component; the demo’s texts don’t use them.

The demo’s posts use headings, paragraphs (with italics and line breaks) and bulleted lists; the legal pages add bold words and links.

  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:

Photos Demo size Frame
A project’s image 2400 × 1600 The Home hero (the whole window), its card (240 px tall on phones, 365 : 244 on tablets, 560 : 374 on desktops), its page’s wide photo (1140 : 750) and a 268 × 200 window of the Home intro
A project’s challenge.gallery 1200 px wide, portrait (1200 × 1593 to 1200 × 2100) Two side by side, 560 : 750
A project’s solution.gallery 2400 × 1600, then two at 1200 × 800 One at 1140 : 750, two at 560 : 368 under it
A client logo SVG, about 500 × 200 130 × 25 in Home’s logo row, 260 × 78 on the project’s photo (72 × 22 on phones)
A service’s thumbnail 800 × 800 Square cards
A service’s image 2400 px wide (2400 × 1518 and up) Its page: 1140 : 721; the Services list: 492 px tall on desktops, as tall as the text on tablets, 228 px on phones
The square image beside “What We Offer” (serviceItemPage.offer.image) 500 × 501 Square, 250 px on desktops; the same on every service page
A post’s image 2400 × 1600 (1350 to 1920 tall) The card at 367 : 240, the post’s cover at 1.9 : 1
A testimonial’s photo 200 × 200 Round, 42 to 45 px
About’s title photo, Home’s call-to-action photo 2400 × 1600, 2400 × 1345 1140 : 618, 1140 : 639
About’s side and wide photos 1200 × 821, 2400 × 843 Half the width beside the vision card; 1140 : 400
About’s awards photos 600 × 400 274 : 364 (portrait), cropped
A team member’s photo 800 × 1200 367 : 494
Home’s number cards and its services call-to-action 800 × 681 to 1600 × 897; 1600 × 800 and 600 × 900 Fill their cards, which change shape per screen

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

Every photo is written as { src, alt }, and the alt is a short description for screen readers and search engines. Write one for each photo you change (an empty alt: "" marks a photo as decoration). The team’s social chips use /images/icon-instagram.png (80 × 80): swap it for the icon of the network you link.

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

File What it is
public/icon-light.png, public/icon-dark.png The icon in the browser tab: the dark mark for a light browser theme, the light one for a dark theme (180 × 180 each; set in src/app/layout.tsx)
src/app/apple-icon.png The icon on a phone’s home screen (200 × 200)
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.

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

  • “Main” (the menu’s name for screen readers), “Menu” and “Close” (the phone menu button) in src/components/site/Header.tsx;
  • “Testimonials”, “Previous” and “Next” (the testimonial carousel on tablets and phones, for screen readers) in src/components/sections/HomeTestimonials.tsx;
  • “… out of 5 stars” (the ratings, for screen readers) in src/design-system/components/cards/TestimonialCard.tsx and src/components/sections/AboutTitle.tsx;
  • the date format (“May 30, 2025”) 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 project’s services match services, 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.