Editing the content — Balancee 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 "Contact us" 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 call to action band, the consultation line, "How we work" and the contact form, shown on several pages collections/*.ts services, case studies (portfolio.ts), 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 the file that renders it.
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 (“About us | Balancee”), share cards, the copyright line, the logo link’s name for screen readers |
site.title |
The browser title of Home |
site.description |
Search results and share cards (the site’s default 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. |
logo, logoWhite |
The wordmark as image files, for use elsewhere (Making it look like your brand) |
navigation |
The header’s links (and the phone menu): Home, About, Services, Portfolio, Blog |
contactLink |
The header’s “Contact us” button (it opens /contact) |
bookingLink |
Where “Let’s talk” and “Book a Free Consultation” lead. The demo points to https://cal.com/, the booking tool’s home page: use your own booking page, or /contact. |
contact |
E-mail, phone, address and opening hours: the footer’s contact column and the Contact page |
socials |
The social links of the footer, About and Contact (the demo’s open the networks’ home pages) |
footer |
The footer: the newsletter box’s texts (newsletter), the labels of its columns, quickLinks, how many case studies (caseStudyCount, 5) and services (serviceCount, 4) it lists, the copyright line (note, where {year} becomes the current year) and legalLinks |
The demo’s e-mail (hello@example.com), phone number and Brooklyn address are placeholders: replace all three. The
phone’s link is built from the number (+44 20 7946 0345 calls tel:+442079460345), so write it the way people should
read it, with your country code if visitors call from abroad. Point the social links to your own profiles and remove the
ones you don’t use.
The company’s name appears in many places: site, the footer’s note, the copy of every page, the testimonials, the
client logos’ texts, the case studies and the legal pages. The wordmark draws the name too
(Making it look like your brand). Search src/content/ for “Balancee”, the six team members’ names (they are the posts’ authors too) and
“Brooklyn” to find them all.
Page copy
Section titled “Page copy”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 us", // browser tab: "About us | Balancee" description: "We help ambitious leaders make …", // search results and share cards (80–160 characters)};
export const hero = { breadcrumb: "About us", title: "Driving businesses to sustainable growth", text: "We help ambitious leaders make confident decisions, …", cta: { label: "Our services", href: "/service" },};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 ’.
| File | Page |
|---|---|
home.ts |
Home: the hero (hero: title, the rating with three avatars, text, two buttons, the video and its caption), the client logos (clients), the intro of the services (services, with count, how many services show: 6), “About Balancee” (about: three figures, the text, the photo and a clip), the photo of “How we work” (process; its steps are in shared.ts), “Case Studies” (caseStudies: two cards, a spotlight and three recent ones, all picked by slug), the testimonials (testimonials) and the intro of the blog (blog, with count, how many posts show: 3). Its meta is Home’s title and description. |
about.ts |
About: the hero with its three figures (hero), “Who We Are” (who: three values and four photos), “Our Journey” (journey: six milestones and the awards) and “Our Team” (team: six members) |
service.ts |
The Services page (hero, the intro of the contact form contactSection) and the labels of a service’s own page (detail, including otherCount, how many other services it ends with: 3) |
portfolio.ts |
The Portfolio page (hero, list: how many case studies load at a time, 4) and the labels of a case study’s page (detail, including otherCount: 2) |
blog.ts |
The Blog page (hero, list: how many posts load at a time, 4) and the labels of a post’s page (post, including otherCount: 2) |
contact.ts |
Contact: the title and lead (hero) and the labels of the details (details); the values are in contact in site.ts |
legal.ts |
Every legal page: “Last updated:” (updatedLabel) and the search description of each page (description) |
not-found.ts |
The 404 page: its browser title, “404 Error”, the title, the text and “Go to homepage” |
shared.ts |
The blocks several pages show (below) |
The figures (“$86M+”, “320+”, “+37%”) are plain text: nothing counts up.
Blocks shown on several pages
Section titled “Blocks shown on several pages”src/content/pages/shared.ts holds the parts that several pages show from one copy:
ctaBand: the dark band before the footer, “Ready to move your business forward?”, its text, “Get in Touch” (to/contact), “Book a Free Consultation” (tobookingLink) and the photo behind it. It closes every page except Contact.consultation: “Let’s talk about your goals — book a 20-minute consultation with our team.” and its button, beside the photo of Home’s testimonials.process: “How we work”: the heading and four steps (Discover, Define, Design, Deliver, each with a title, a promise and a text), and the line “Want to know what’s possible?” with its “Get in touch now” button. Home shows it with a photo, the Services page without.contactForm: the contact form’s fields, the three texts of the button and the title of each submission (Forms);formLegalis the line under it (“By submitting, you agree to our Terms of Service and Privacy Policy”).
Collections
Section titled “Collections”src/content/collections/ holds the lists the site builds pages and sections from:
| File | What it feeds |
|---|---|
services.ts |
The Services page (every service as a card), Home’s “Services built for growth” (the first six: services.count in home.ts), one page per service at /service/<slug>, “Other services” under a service (the next three) and the footer’s row of services (the first four) |
portfolio.ts |
The Portfolio page (every case study, four at a time), one page per case study at /portfolio/<slug>, “Other case studies” (the next two), Home’s “Case Studies” (six of them, picked by slug) and the footer’s “Case Study” column (the first five) |
posts.ts |
Blog (every post, four at a time), one page per post at /blog/<slug>, Home’s blog (the first three) and “Other blogs” under a post (up to two other posts of the same category) |
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 and Portfolio show four items at first and four more each time the visitor scrolls near the end of the list; every item is in the page’s HTML from the start, so search engines find them all.
Home picks six case studies by their slug (caseStudies in home.ts: cards, spotlight and recent). If you
delete or rename one of them, change the slug there too, or npm run build fails.
Adding a post
Section titled “Adding a post”Copy an existing entry, paste it where it should appear, and change the values:
{ "slug": "five-habits-of-calm-leaders", // the URL: /blog/five-habits-of-calm-leaders "title": "Five Habits of Calm Leaders", // the card, the page's title and its browser title "excerpt": "Small daily habits that keep a team steady.", // under the title and on the cards "image": { "src": "/images/post-five-habits-of-calm-leaders.jpg", "alt": "…" }, // the card's photo and the page's cover "category": "Business", // the chip on the card; related posts share it "date": "2026-11-02", // shown as "Nov 2, 2026" "author": { "name": "Emma Carter", "role": "Founder & CEO", "avatar": { "src": "/images/team-emma-carter.jpg", "alt": "…" } // the demo reuses the team photos }, "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 the breadcrumb, the title, the excerpt, the author and the date, the cover photo, then the article.
“Other blogs” follows with up to two other posts of the same category, in the file’s order; it is left out when the
category has no other post. category is plain text (“Marketing”, “Business” and “Innovation” 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 (describe in src/lib/format.ts).
Adding a service
Section titled “Adding a service”{ "slug": "supply-chain-advisory", // the URL: /service/supply-chain-advisory "name": "Supply chain advisory", // the card's title, the page's title, a choice in the contact form "summary": "Resilient, efficient supply chains.", // under the title on the card "image": { "src": "/images/service-supply-chain-advisory.jpg", "alt": "…" }, // the card and the photo beside the intro "intro": "…", // the paragraph under the title of the page "whatWeDo": { "title": "…", "text": "…", "image": { … } }, "offered": { "title": "…", "items": [ { "title": "…", "text": "…" }, … ] }, // six in the demo "process": { "title": "…", "text": "…", "image": { … }, "steps": [ { "title": "…", "text": "…" }, … ] } // four in the demo}The titles of the offered items are also the “What we offer” tags near the top of the page. The service is added to the
Services page, Home (if it is among the first six), the footer (if it is among the first four) and the sitemap
automatically. The contact form’s “I’m interested in …” choices are written out in contactForm in shared.ts:
add the new name to options there.
Adding a case study
Section titled “Adding a case study”{ "slug": "supply-shift", "name": "Supply Shift", // the chip on the card and the page's title "headline": "Rebuilding a Supply Chain for Resilience", "summary": "…", // under the headline, on Home's accordion "image": { "src": "/images/portfolio-supply-shift-cover.jpg", "alt": "…" }, // the cover and the card's photo "client": "…", "budget": "…", "duration": "…", "team": "…", // the four details under the headline "overview": { "title": "Overview", "body": [ … ], "images": [ … ] }, "challenges": { "title": "Client Challenges", "body": [ … ], "images": [ … ] }, "solutions": { "title": "Solutions", "body": [ … ], "images": [ … ] }, "results": { "title": "Results", "body": [ … ], "images": [ … ], "stats": [ { "value": "+37%", "label": "…" }, … ] } // three figures in the demo}Each section is a title, rich text and photos. In the demo the overview has four photos (the first wide, the next three in
a row), the challenges two (side by side), the solutions and the results one each; a case study with fewer photos
(Merge Mastery has two) simply shows fewer. Home’s accordion shows the case study’s summary and the first of its
results.stats, so keep at least one figure.
Legal pages
Section titled “Legal pages”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: Aug 10, 2025”) 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 company and country.
The footer’s legal links and the line under the contact form are written in footer.legalLinks (site.ts) and
formLegal (shared.ts), not built from the collection: change them when you add or rename a legal page.
The timeline, the awards and the team
Section titled “The timeline, the awards and the team”They are page copy in src/content/pages/about.ts, not collections:
journey.milestones:{ year, title }for each of the six entries of the timeline;journey.awards.items:{ award, by, year, href }for each row (the demo’s links open awwwards.com: point them to yours or to#);team.members:{ slug, name, role, photo, bio, href }for each card;hrefis the member’s LinkedIn profile (the demo’s open linkedin.com). The cards sit three to a row on desktops; the bio shows when the pointer is over a card on desktops and is not shown on tablets and phones.
Removing an item
Section titled “Removing an item”Delete the entry. An item’s own page and its sitemap entry disappear on the next build. Before you remove a service, a
case study or a legal page, check the places that name it: the contact form’s options, Home’s caseStudies, the
footer’s legalLinks and formLegal.
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, case studies and legal pages
Section titled “Rich text: posts, case studies and legal pages”A post’s body, a legal page’s body and every section of a case study 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 one heading style (
levelis 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\nstarts 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.
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 (larger is fine where the demo’s
are small):
| Photos | Demo size | Frame |
|---|---|---|
The Home hero video’s poster (hero.video.poster) |
1920 × 1080 | 1140 × 500 on desktops, behind the video |
The About clip’s poster (about.video.poster) |
1280 × 720 | 350 × 189 |
The review video’s poster (testimonials.items[0].video.poster) |
1506 × 1004 | Up to 753 px wide |
Home’s About photo (about.image), the process photo (process.image), the testimonials’ photo (testimonials.image) |
1040 × 1558, 934 × 1401, 734 × 918 | Tall frames, up to 520, 467 and 367 px wide |
The call to action band (ctaBand.image) |
2400 × 1600 | Full width behind the dark band |
About: the hero photos (hero.images), the four “Who We Are” photos (who.images) |
510 × 287 and 934 × 623; 1120 × 1493, 1120 × 747, 346 × 519, 734 × 918 | Up to 255 px (hero) and 560 px wide |
A team member’s photo |
about 714 × 893 to 714 × 1071 | A portrait at about 3 : 4 |
A service’s image |
about 1034 × 550 to 1034 × 690 | Square on cards, 4 : 5 beside the intro (up to 517 px wide) |
A service’s whatWeDo.image and process.image |
about 1090 × 727; 934 × 668 | 545 : 400, up to 545 px wide; up to 467 px wide |
A case study’s image (cover) |
2400 × 1427 to 2400 × 1800 | 560 : 475 on cards |
| A case study’s section photos | overview 1900 × 1267 then 620 × 413; challenges 940 × 627; solutions and results 1900 × 1267 | Overview: wide (12 : 5) then three at 3 : 2; challenges and the rest at 3 : 2 |
A post’s image |
2000 × 1333 (some taller) | 360 : 236 on cards; 2.4 : 1 on its page, up to 1140 px wide |
| The avatars of the hero rating, a post’s author and the testimonials | 120 × 120 | Small and round |
The client logos (clients.logos) |
SVG files drawn for the template | 144 px wide on 250 × 125 tiles |
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 }. Write one for
each photo you change (an empty alt: "" marks a photo as decoration, like the call to action band’s).
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 “B” mark, for a light and for a dark browser theme (the file names are set in src/app/layout.tsx) |
src/app/apple-icon.png |
The icon on a phone’s home screen |
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.
Videos
Section titled “Videos”Three videos play on Home, muted, without controls:
| Video | Where it plays | Field |
|---|---|---|
| Hero video | Under the hero’s text, behind the white wordmark; it plays at once and loops (1140 × 500 on desktops) | hero.video.src in src/content/pages/home.ts |
| About clip | Beside the text of “About Balancee” (350 × 189); it plays while it is on screen | about.video.src in home.ts |
| Review video | On the first testimonial’s card (753 × 400); it plays when the visitor clicks “Watch a review”, and again pauses on a click | testimonials.items[0].video.src in home.ts |
The demo plays three 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/hero.mp4", or use a web address of your own. Each video fills its frame (a video of other proportions is
cropped); keep each file small (a few MB). Each has a poster image (poster), a local photo shown until the video plays
and to visitors with “reduce motion” switched on, whose hero and About clips then stay on the poster.
Text that is not in content/
Section titled “Text that is not in content/”Almost every word is content, including the forms’ messages (shared.ts). The few interface words that never change
per site live in the code:
- “Main”, “Mobile” (the menus’ names for screen readers) and “Menu” (the phone menu button’s label) in
src/components/site/Header.tsx; - the date format of the post cards (“Feb 21, 2024”) 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 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.