Editing the content — Cerette 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 "Let's talk" button, social links, booking link, phone, e-mail and address, the footer pages/home.ts the copy of the home page pages/about.ts …and of every other page pages/cta.ts the closing call to action of Home and the inner pages pages/forms.ts the inquiry forms collections/*.ts projects, services, testimonials, team, posts and legal pages routes.ts the URL of every page types.ts the fields each kind of item hasNot 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 generated from another folder: that note is about how the demo content was made. In your copy, these files are the content: edit them.)
Your details first
Section titled “Your details first”src/content/site.ts holds what appears on every page:
| Export | Shown where |
|---|---|
site.name |
The browser title suffix (“Projects | Cerette”), 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, About, Services, Projects, Blog |
headerAction |
The brown “Let’s talk” button at the right of the header |
socials |
The social links of the footer’s “Follow us:” row |
contact |
The phone, the e-mail and the address of the footer’s Contact column; the e-mail and the phone of the Contact page too |
bookingHref |
Every “Book a call” button (Home, About, Projects, Services) and “Schedule Consultation” in the closing call to action |
footer |
The footer: its line (text), the “Contact us” link (action), the column titles (quickLinksLabel, servicesLabel, legalLabel, contactLabel), the Quick Links (quickLinks), the labels of the contact lines (phoneLabel, emailLabel, addressLabel), “Follow us:” (followLabel) and the copyright line (note, where {year} becomes the current year) |
The footer’s Services column lists every service and its Legal column every legal page: they come from the collections, so they follow when you add or remove an item.
The demo’s e-mail (hello@example.com), phone number and address are placeholders: replace them. The Contact page shows
its own copy of the address, written on three lines (address in src/content/pages/contact.ts), and the working hours
(hours): change those too. The phone’s link is built from the number (+1 (000) 123-4567 calls tel:+10001234567),
so write it the way people should read it, with your country code.
The social links (Instagram, Behance, LinkedIn, Pinterest) open the networks’ home pages: point them to your own profiles, and delete the ones you don’t use.
“Book a call” and “Schedule Consultation” open https://cal.com/ in the demo, a placeholder. Put your booking page in
bookingHref (or /contact, to send visitors to the form): every button that books a call reads it.
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 every page, the founder’s quote, the testimonials, the
forms’ titles, the footer’s copyright and the legal pages. The logo draws it too (Making it look like your brand). Search
src/content/ for “Cerette” to find them all.
Page copy
Section titled “Page copy”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 the Studio", // browser tab: "About the Studio | Cerette" description: "Meet Cerette, a modern architecture and…", // search results and share cards (80–160 characters) }, title: { title: "Studio.", aside: "(Modern Architecture)", intro: "Cerette is a modern…", … }, …};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 label, the text, the title, the video and two buttons), “About us” (three numbers, the title, the text, three points, two buttons and the photo), “Our Projects”, the founder’s quote with its photos, “Our Services”, “Why Cerette” (the tall photo and six reasons, each with an icon), “Our Achievements” (four numbers, the awards table and three photos), the testimonials’ title, and “Latest Insights” with how many posts it shows (blog.count). Its meta.title is the whole browser title, without the suffix. |
about.ts |
About: the title with the line beside it, the text, two buttons and the photo; the statement under the photo; “Meet The Team” (the title, and how many cards tablets and phones show at first); “Our Achievements” (the title, the text and the photo) |
projects.ts |
Projects (projectsPage): the title, the years beside it, the text, two buttons, the cards’ “View Project”, and the testimonials’ title |
project.ts |
The fixed words of every project page (projectPage): “(Scroll to explore)”, the labels of the information row (Year, Location, Duration, Area, Services), “The Brief”, “Scope of Work” and “Other Work” with its button and how many projects it shows |
services.ts |
Services: the title, the line beside it, the text, two buttons and the cards’ “View Details” |
service.ts |
The fixed words of every service page: “Service”, “About service” and “What’s included in the services?” |
blog.ts |
Blog (blogPage): the title, the line beside it, the text, how many posts load at a time (pageSize, per screen size) and what screen readers hear while more load; and the fixed words of every post (postPage: “Similar posts”, “All Articles” and how many posts it shows) |
contact.ts |
Contact: the title, the line beside it, the two paragraphs, the labels of the e-mail and phone, the address and the working hours |
cta.ts |
The closing call to action of Home, About, Projects, a project and a post: the title, the text, the button and the photo |
forms.ts |
The inquiry forms and the block that holds them on Services and a service page (its title and photo) (Forms) |
legal.ts |
The fixed words of every legal page: “Last updated:” |
not-found.ts |
The 404 page: its browser title, “Error 404”, the subtitle, the text, the button and the photo |
Some blocks are written once and shown on several pages:
- the founder’s quote (
home.quote) is on Home, About and Services; - “Why Cerette” (
home.why) is on Home and Services; - the numbers and the awards of “Our Achievements” (
home.achievement) are on Home, and on About (the four numbers under the statement and the awards table).
Edit them in home.ts and every page follows. The numbers are plain text (value: "275", suffix: "+"), shown as
written: they don’t count up. Replace the demo’s numbers, awards and quote with your own.
The Home video
Section titled “The Home video”The Home hero plays a muted, looping video behind its title:
video: { src: "https://…/….mp4", // the video poster: "/images/home-hero-poster.jpg", // the frame shown until the video plays},The demo’s video is streamed from another server; it is not part of your licence and may stop working at any time. Use
your own: put the file in public/ (for example public/videos/hero.mp4) and write src: "/videos/hero.mp4". A
short clip (10 to 20 seconds, 1920 × 1080, H.264 MP4, a few MB) loads quickly. Replace the poster with a frame of your
video, at the same size.
Collections
Section titled “Collections”src/content/collections/ holds the lists the site builds pages and sections from:
| File | What it feeds |
|---|---|
projects.ts |
Projects (every project), one page per project, Home’s “Our Projects” (the first six), “Other Work” at the end of a project page (the first three others in the file) |
services.ts |
Services (every service), one page per service, Home’s “Our Services” (every service, numbered in the file’s order), the services of a project page, the footer’s Services |
testimonials.ts |
The testimonials of Home and Projects (every one) |
team.ts |
“Meet The Team” on About (every person) |
posts.ts |
Blog (every post, newest first), one page per post, Home’s “Latest Insights” (the three newest), “Similar posts” at the end of a post (up to three more of the same category) |
legal.ts |
One page per item (Privacy Policy, Terms of Service), the footer’s Legal column |
Projects, services, testimonials and the team appear in the order of their file. Posts are sorted by date, newest
first, so their place in the file doesn’t matter.
Adding a project
Section titled “Adding a project”Copy an existing entry, paste it where it should appear, and change the values:
{ slug: "lakeside-villa", // the URL: /project/lakeside-villa title: "Lakeside Villa", // the card, the page's title and its browser title summary: "A low timber house that opens onto the water.", // the card, the cover, search results category: "Residential", // any word: the card and the label over the title image: { src: "/images/project-lakeside-villa.jpg", alt: "…" }, // the card and the page's cover year: "2026", location: "Lake Como, Italy", duration: "12 Months", area: "640 m²", services: ["architecture", "interior"], // slugs of services in services.ts: "Services" on its page overview: "…", // the lead of the story brief: "…", // "The Brief" scope: "…", // "Scope of Work" images: [tall, wide, wide, tall], // exactly four photos around the story result: "…", // the paragraph beside the gallery gallery: [photo, photo, photo], // the photos beside the result (three in the demo) resultImage: { src: "/images/project-lakeside-villa-result.jpg", alt: "…" }, // the wide photo at the end}A project page shows the cover with the category, the title and the summary; the information row (year, location, duration, area and the services, each linking to its page); the story (the first tall photo beside a wide one, the overview beside The Brief and Scope of Work, a wide photo beside the second tall one, the result beside the gallery, and the wide result photo); then “Other Work” (the first three other projects in the file) and the closing call to action. The tall photos and the result stay in place while the photos beside them scroll past.
images takes exactly four photos: the first and the fourth are shown tall (2 : 3), the second and the third wide.
services must hold the slugs of services, written exactly; a slug that matches no service is left out.
Home’s “Our Projects” and the Projects page lay the cards out in rows of three of different widths (narrow, wide, narrow, then three equal); the pattern repeats past six projects.
Adding a service
Section titled “Adding a service”{ slug: "lighting", // the URL: /service/lighting; also what projects list in `services` name: "Lighting", // cards, the footer, Home's list, its page's title, the browser title summary: "Lighting design that…", // the cards' text, the line under its page's title, search results image: { src: "/images/service-lighting.jpg", alt: "…" }, // the card, Home's photo, its page's wide photo about: "…", // "About service" included: { text: "…", // the paragraph under "What’s included in the services?" items: [ { title: "Concept Lighting", text: "…" }, // a deliverable: a dot, its title and its line … ], },}Any number of deliverables works; one with an empty text shows its title alone. A service’s page ends with the
inquiry form, its project type filled in with the service’s name (Forms).
On Home, the services are shown one at a time: their names in a list (numbered 01, 02 … in the file’s order) beside the chosen one’s card and photo on desktops and tablets, an accordion on phones.
Testimonials
Section titled “Testimonials”{ slug: "olivia-bennett", // an id name: "Olivia Bennett", role: "Interior Client", // shown as "Interior Client • 2025" photo: { src: "/images/client-olivia-bennett.jpg", alt: "Portrait of Olivia Bennett" }, year: "2025", rating: 4.9, // shown with one decimal beside a star quote: "“…”", // write the quotation marks yourself, as the demo does}Testimonials have no pages of their own. Home and Projects show every one, in columns of different heights.
The team
Section titled “The team”{ slug: "ethan-carter", // an id name: "Ethan Carter", role: "Principal Architect", photo: { src: "/images/team-ethan-carter.jpg", alt: "…" }, summary: "…", // the line under the portrait}On desktops, About lists the names; pointing at one (or focusing it) shows that person’s portrait and summary in the
column beside the list. Tablets and phones show the people as cards, six at first and the rest as the visitor scrolls to
the end of the list (team.pageSize in about.ts).
Adding a post
Section titled “Adding a post”{ slug: "daylight-in-small-homes", // the URL: /blog/daylight-in-small-homes title: "Daylight in small homes", category: "Interior", // Architecture, Construction or Interior date: "2026-06-12", // shown as "Jun 12, 2026"; also the order of the list excerpt: "How windows, colour and layout bring light into a small plan.", // the card, under the title, search results image: { src: "/images/post-daylight-in-small-homes.jpg", alt: "…" }, // the card and the post's photo content: [ … ], // rich text, below}The three categories are the type PostCategory in src/content/types.ts: add a word there to use a new one. A post
ends with “Similar posts”, up to three more posts of the same category, newest first, and the closing call to action.
The Blog page shows six posts on desktops and four on tablets and phones, and loads as many again each time the visitor
nears the end of the list (pageSize in blog.ts); every post is in the page’s HTML from the start, so search engines
find them all.
Legal pages
Section titled “Legal pages”{ slug: "privacy-policy", // the URL: /legal/privacy-policy title: "Privacy Policy", date: "2026-05-26", // "Last updated: May 26, 2026" content: [ … ], // rich text, below}The demo’s two pages are sample text with the demo studio’s name filled in. They are not legal advice: replace them with your own policy and terms, and say there what the forms collect (Forms).
Removing an item
Section titled “Removing an item”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.
What each field means
Section titled “What each field means”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.
Rich text: posts and legal pages
Section titled “Rich text: posts and legal pages”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: "The Importance of Functional Space Planning" }, { 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 (*…*),labelis a link (anhttps://link opens in a new tab), and\nstarts a new line. - Headings all look the same (Heading 3) whatever their
level. - 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 and legal pages use headings, paragraphs and bulleted lists.
Images
Section titled “Images”- Put the file in
public/images/. - Refer to it in the content as
/images/<file>(the path starts atpublic).
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 px wide (2400 × 1350 to 1600) | The project page’s cover (the whole window); the cards: square, 1.15 : 1 or 1.65 : 1, depending on their place in the grid |
A project’s first and fourth images |
456 px wide, portrait (456 × 556 to 718) | 2 : 3, a fifth of the row on tablets and desktops |
A project’s second and third images |
1724 px wide (1724 × 970 to 1294) | 3 : 2 |
A project’s gallery |
1090 px wide | 3 : 2, half the row |
A project’s resultImage |
2280 px wide (2280 × 1282 to 1522) | 3 : 2, the whole row |
A service’s image |
2280 px wide (2280 × 1282 to 1710) | Its page: 3 : 2; the Services cards: 1.65 : 1; Home’s services: 1.77 : 1 |
A post’s image |
2280 px wide (2280 × 1203 to 1710) | The card: 1.9 : 1; the post: 3 : 2 |
A testimonial’s photo |
152 px wide | Round, 38 px |
A team member’s photo |
798 px wide, portrait (798 × 997 to 1200) | 0.74 : 1 |
Home: the hero’s poster, the about photo, the quote’s photo, the “Why Cerette” photo |
1920 × 1080, 1540 × 1027, 2400 × 1600, 1200 × 1800 | The whole window; 3 : 2; the width of the page; a tall cell beside the reasons |
Home: the founder’s avatar, the three award photos |
120 × 120; 840 px wide | Round, 42 px; three side by side |
| About: the title photo, the awards photo | 2280 × 1520, 1540 × 2310 | 3 : 2; 2 : 3 |
The call to action’s photo (cta.ts), the form block’s photo (forms.ts), the 404 photo |
2400 × 1800, 1090 × 1644, 2400 × 1600 | The width of the page; as tall as the form, desktops only; the whole window |
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. The photos under text (the hero, the covers, the quote, the call to action, the 404) sit under a half-black veil, so the white text stays readable.
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).
public/images/grain.png is the fine texture laid over many photos (the cards’ and the covers’). Keep it, or replace it
with a texture of your own under the same name.
Three things sit outside the content because browsers and social networks ask for them by name:
| File | What it is |
|---|---|
public/icon.svg |
The icon in the browser tab: the black mark with its brown pieces, white in a dark browser theme (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.
Text that is not in content/
Section titled “Text that is not in content/”Almost every word is content, including the forms’ messages (forms.ts) and what screen readers hear while more posts
load. The few interface words that never change per site live in the code:
- “Main” (the menu’s name for screen readers), “Open menu” and “Close menu” (the phone menu button) in
src/components/site/Header.tsx; - the date formats (“Jun 12, 2026” on posts, “May 26, 2026” on legal pages) in
src/lib/format.ts; - the page’s language,
lang="en", insrc/app/layout.tsx.
Search for the word and you will find it.
After editing
Section titled “After editing”npm run buildA 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.