Editing the content — Compose Digi Next.js
All the words and images of this Next.js template live in src/content/ and public/images/, 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, "Contact Us", "Book a call", contact details, socials, the footer and the cursor's labels pages/home.ts the copy of the home page pages/about.ts …and of every other page (About also holds the team, the figures and the client logos) pages/service.ts the fixed words of every service page (the plan card, "Other Services") pages/project.ts the fixed words of every project page ("Overview", "Process", "Outcome", "More Projects") pages/post.ts the fixed words of every post page ("Posted on", Prev / Next, "More Blog") pages/careers.ts the Careers page and the headings of every job page pages/contact.ts the Contact page and its form collections/*.ts services, projects, posts and job openings (careers.ts) 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.
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 | Compose”), 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 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, Services, Projects, About, Blog |
contactLink |
“Contact Us” and the round lime arrow beside it in the header, and the footer’s round button: all open /contact |
menuLabels |
The phone menu button’s two words, “Menu” and “Close” |
bookCallLink |
“Book a call” in the Home hero. It opens https://cal.com/: point it at your own booking page. |
contact |
The phone number, the e-mail and the address at the bottom of the footer |
socials |
The footer’s Social Media column (Instagram, Twitter, Facebook, Behance) |
footer |
The footer: the call to action (title, “Tell Us Your New Ideas”), the line under the logo (lead), the three link columns (columns: Links, Support, Social Media), the words after the copyright year (note) and the name of the moving service strip for screen readers (tickerLabel) |
pageSocials |
The round social buttons at the top of About, Services, a service, Projects and Blog |
cursorLabels, serviceCursorLabel |
The words of the custom cursor over a project card (“View Project”), a post card (“Read”) and a service card (“More Details”) |
The demo’s e-mail (hello@example.com), phone number and address (“23 Artist Avenue, … Wonderland”) are placeholders:
replace all three. The phone’s link is built from the number (001 265 847 483 calls tel:001265847483), 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. The “Book a Call” link of the footer’s
Support column is written in footer.columns itself: change it together with bookCallLink.
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 agency’s name appears in many places: site, the copy of most pages, the founder’s quote on Home (“— Davide
Gotlieb, Founder of Compose”), the job openings and the share image’s description. The logo draws the name too
(Making it look like your brand). Search src/content/ for “Compose” to find them all. Every job opening asks applicants
to write to careers@example.com: put your own address there.
Page copy
Section titled “Page copy”There is one file per page in src/content/pages/. Each exports one object with the blocks of that page and, for most
pages, a meta entry:
export const about = { meta: { title: "About", // browser tab: "About | Compose" description: "Compose blends creativity, data …", // search results and share cards (80–160 characters) }, hero: { eyebrow: "About Us", title: "Crafting Digital Connections That Drive Growth", lead: "At Compose, we blend creativity, data, and strategy …", … }, …};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.
| File | Page |
|---|---|
home.ts |
Home: the hero (hero: the title, the rating — score, caption and four round avatars —, the lead, “Book a call” and “Our Services”, and the name of the project strip for screen readers), “Who are we?” (about: the title, the lead, two photos, two paragraphs, “More about us” and “Our Projects”), the founder’s quote over a photo (quote), “Our services” (services: the intro, two lines, count, how many services the list shows, and “More Services”), “Our Projects” (projects: the title, which projects the strip and the list show — tickerCount, listOffset, listCount — and the dark invitation box under the list, more) and “Latest Blog” (blog, with count). Home’s browser title is site.title; its description is meta.description. |
about.ts |
About: the top block (hero), “WHO WE ARE?” (intro: two photos, the statement, two paragraphs, “Contact us” and “Our Projects”), the video (video, below), the figures and the client logos (facts), “Our Team” (team: the intro and the six members) and “Open Positions” (positions: count, how many openings show, and “See all positions”) |
services.ts |
Services: the top block, the list’s intro (list), “How we work?” with its chart (process, below), the call to action over a photo (cta) and “Hear From Customers” (testimonials: count, how many projects’ testimonials, and interval, the seconds before the next one shows) |
service.ts |
Every service page: the social buttons and “Scroll to Explore” of the top block, “What We Offer” and “Key Benefits”, the plan card’s words (plans: “ Package” after the name, “Weekly” / “per week”, “Monthly” / “per month”, “What’s Included:”, “Book an intro call”) and “Other Services” (others, with count). The name, the summary, the photo, the texts and the prices are the service’s own entry. |
projects.ts |
Projects: the top block and the list (list: its name for screen readers, pageSizes, how many cards show at a time on phones, tablets and desktops, and “Load More”) |
project.ts |
Every project page: the headings “Overview”, “Process” and “Outcome”, and “More Projects” (more: count and the dark invitation box) |
careers.ts |
Careers (careers: the title, the lead, “More Details”, pageSizes and “Load More”) and every job page (job: the headings “Key Responsibilities”, “Requirements”, “Perks and Benefits”, “How to Apply” and “Back to Career page”) |
blog.ts |
Blog: the top block and the list (list: as on Projects) |
post.ts |
Every post page: “Posted on” and “Posted in” (meta), Prev / Next (nav) and “More Blog” (more, with count) |
contact.ts |
Contact: the title (two lines), the lead and the form (Forms) |
not-found.ts |
The 404 page: its browser title, the big “404”, the title, the two lines under it and the two buttons |
The figures on About (“260+ Campaigns Launched”, …) are plain text, split into the number (value) and the small sign
after it (suffix): nothing counts up. The Home hero’s rating (“4.9 / 5.0”, “Trusted by 500+ Brands Globally”) is text
too: write your own.
The team
Section titled “The team”The team is page copy, not a collection: team.members in src/content/pages/about.ts.
{ name: "Jane Mills", role: "Developer", photo: { src: "/images/about-team-jane-mills.jpg", alt: "A young woman with long hair in a beige sweatshirt" }, socials: teamSocials, // the round buttons under the photo (defined at the top of about.ts)}The cards sit three to a row on desktops, two on tablets, one on phones. Every member shares the same teamSocials
(links to the networks’ home pages): give a member a list of their own, with network set to "behance",
"dribbble", "instagram", "twitter" or "x" to pick the logo.
The process chart
Section titled “The process chart”“How we work?” on Services draws the phases of a project as bars over a scale from 0 to 100 %:
phases: [ { name: "Discovery", from: 0, to: 20, row: 0 }, // from 0 % to 20 %, on the first row { name: "Planning", from: 20, to: 45, row: 1 }, // the second row …],axis: [0, 25, 50, 75, 100], // the scale under the bars (phones show 0, 50 and 100)The bars fill in once the whole chart is on screen. Screen readers hear the phases as a list, named by label.
Collections
Section titled “Collections”src/content/collections/ holds the lists the site builds pages and sections from:
| File | What it feeds |
|---|---|
services.ts |
One page per service; the list of Home (the first six: services.count in home.ts); the cards of Services (every service); “Other Services” under a service; the tags of the projects that used it; the footer’s two moving rows of names (the first eight); the “Services” checkboxes of the contact form (every service) |
projects.ts |
One case study per project; Home’s moving strip (the first four: tickerCount) and list (five from the fourth on: listOffset 3, listCount 5); Projects (every project); “More Projects” under a project (the first three others); the testimonials of Services (the client quotes of the first three) |
posts.ts |
One page per post; Home’s “Latest Blog” (the first three); Blog (every post); Prev / Next and “More Blog” under a post |
careers.ts |
One page per job opening; About’s “Open Positions” (the first three); Careers (every opening) |
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. Projects, Blog and Careers show a few items at first and the next ones each time the visitor presses “Load More”; every item is in the page’s HTML from the start, so search engines find them all.
Adding a service
Section titled “Adding a service”{ "slug": "influencer-marketing", // the URL: /services/influencer-marketing; projects refer to it "name": "Influencer Marketing", // the title everywhere, the form's checkbox, the footer strip "summary": "We connect your brand with …", // under the title on cards, rows and the service's page "image": { "src": "/images/service-influencer-marketing.jpg", "alt": "…" }, "offer": [ … ], // "What We Offer": rich text, below "benefits": [ … ], // "Key Benefits": rich text "weekly": { // the plan card with the switch on "Weekly" "price": "$800", // any text; shown with "per week" "features": ["…", "…", "…", "…"] // "What’s Included:" (four lines in the demo) }, "monthly": { "price": "$2,600", "features": ["…", "…", "…", "…"] }}The plan card has a Weekly / Monthly switch; it starts on Weekly. Both plans are required. The footer’s moving strip shows the first eight services in two rows of four, and its look is made for names of about the demo’s length.
Adding a project
Section titled “Adding a project”{ "slug": "launching-a-coffee-brand", // the URL: /projects/launching-a-coffee-brand "title": "Launching a Coffee Brand Online", // the card and the page's title "company": "Bean & Co", // the client: the card, the Home strip, "2024, Bean & Co" on the page "year": "2024", "summary": "…", // under the title on the page; its search description "thumbnail": { "src": "/images/project-…-cover.jpg", "alt": "…" }, // the cards and the page's cover "services": ["branding-and-strategy", "content-marketing"], // slugs from services.ts: the tags above the title "testimonial": { // the client's words: on the card, the page and (first three) Services "name": "…", "role": "CEO, Bean & Co", "photo": { "src": "/images/testimonial-….png", "alt": "" }, "quote": "…" }, "overview": [ … ], // rich text under "Overview" "mainImage": { "src": "/images/project-…-main.jpg", "alt": "…" }, // the photo after Overview "process": [ … ], // rich text under "Process" "images": [ // exactly two: the photo sliding in from the right, then the one growing on the left { "src": "/images/project-…-image-1.jpg", "alt": "…" }, { "src": "/images/project-…-image-2.jpg", "alt": "…" } ], "outcome": [ … ], // rich text under "Outcome" "finalImage": { "src": "/images/project-…-image-3.jpg", "alt": "…" } // the last photo}A project’s services are slugs: a slug that matches no service is skipped. The Home strip shows a project’s company
and its first service. The quote is written without quotation marks; the page adds them.
Adding a post
Section titled “Adding a post”{ "slug": "finding-your-brand-voice", // the URL: /blog/finding-your-brand-voice "title": "Finding Your Brand Voice", // the card, the page's title and its browser title "excerpt": "…", // the card's text (its start) "image": { "src": "/images/post-finding-your-brand-voice.jpg", "alt": "…" }, // the card's photo and the page's cover "category": "Web Design", // "Posted in" on the page "date": "2026-06-02", // shown as "Jun 2, 2026" "body": [ // the article: rich text, below { "type": "paragraph", "text": "First paragraph." }, { "type": "heading", "level": 3, "text": "A heading" } ]}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 title, “Posted on” with the date and “Posted in” with the category, the cover photo and the article, then Prev (the next item of the list, older in the demo’s order) and Next (the one before it, newer). “More Blog” follows with the first three other posts of the list. The search description is the article’s first paragraph, cut at 160 characters.
Adding a job opening
Section titled “Adding a job opening”{ "slug": "content-strategist", // the URL: /careers/content-strategist "title": "Content Strategist", "type": "Full Time", // any text: "Remote", "Full Time", "Part Time", "Freelance" in the demo "summary": "…", // the list row's text; the page's search description "responsibilities": [ … ], // rich text under "Key Responsibilities" "requirements": [ … ], // "Requirements" "benefits": [ … ], // "Perks and Benefits" "apply": [ … ] // "How to Apply" (the demo's has an e-mail link)}Removing an item
Section titled “Removing an item”Delete the entry. Its page and its sitemap entry disappear on the next build. Before you remove a service, remove its
slug from the services of the projects that name it (a missing one is simply skipped).
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
Section titled “Rich text”A service’s offer and benefits, a project’s overview, process and outcome, a post’s body and an opening’s four
texts are lists of blocks:
[ { "type": "heading", "level": 3, "text": "Why Prototyping Matters" }, { "type": "paragraph", "text": "**Brand Strategy**: Developing a comprehensive brand strategy …" }, { "type": "list", "ordered": false, "items": [ [{ "type": "paragraph", "text": "Competitive salary with performance-based bonuses." }], [{ "type": "paragraph", "text": "Flexible working hours and remote work options." }] ] }]- Headings keep their
level, which picks the text style: the posts use level 3. - Paragraphs are plain text with four marks: words between double asterisks are bold (
**…**), words between single ones are italic (*…*),[label](https://…)is a link (mailto:works too) and\nstarts a new line inside a paragraph. A bracket without a link after it ([Your Name]) stays plain text. - Lists are bulleted (
"ordered": false) or numbered ("ordered": true); each item is its own list of blocks, usually one paragraph.
There are no 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:
| Photos | Demo size | Frame |
|---|---|---|
A project’s thumbnail |
2000 × 1333 (some 2000 × 1121 to 2400 × 1600) | The cards (about 1.43 : 1), the Home strip (450 × 370, 260 × 375 on phones) and the page’s cover (1120 × 635, settling from 120 %) |
A project’s mainImage and finalImage |
2000 × 1121 to 2240 × 1494 | 3 : 2, full width, moving slower than the page |
A project’s two images |
1200 × 673 to 1200 × 800 | 2 : 1, 75 % and 60 % of the width on desktops |
A testimonial’s photo |
150 × 150 | Round, 72 px on a project page, smaller on the Services chips |
A service’s image |
2200 × 1460 (some 2000 × 2500) | 353 : 420 on cards; 1200 : 680, full width, on its page |
A post’s image |
2000 × 1333 (some 2000 × 3000) | 353 : 420 on cards; 3 : 2 on its page |
A team member’s photo |
720 × 785 | 7 : 9 |
Home and About “Who are we?” (about.images, intro.images) |
1100 × 619, 1100 × 1375 | 545 : 450 and a tall photo on Home; 353 : 292 and 500 px tall on About |
The quote’s background (quote.image in home.ts) |
2400 × 1594 | Full width under a dark veil |
The About video’s cover (video.image) |
2240 × 1654 | 16 : 9 |
The Services call to action (cta.image) |
2400 × 3600 | Full width under a dark veil, moving slower than the page |
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: the alt in { src, alt }. Write
one for each photo you change (an empty alt: "" marks a photo as decoration, like the testimonial portraits, whose name
is written beside them).
Some images are SVG files and stay as they are in the download:
| Files | What they are |
|---|---|
client-logo-*.svg |
The six client logos running under the figures on About (facts.logos in about.ts, each with its width in pixels at 30 px tall). They are samples from the original template: replace them with your clients’ logos, or delete the entries. |
home-hero-avatar-1.svg … -4.svg |
The four round faces of the Home hero’s rating (42 × 42, an SVG holding a small portrait). Put four portraits of your own clients in their place (SVG, PNG or JPG, at least 84 × 84 — change the paths in hero.rating.avatars). |
logo.svg |
The logo as a file, 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.svg |
The icon in the browser tab: the round Compose mark, the same for light and dark browser themes (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 demo’s shows an older Compose design: make your own. |
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).
The About video
Section titled “The About video”The About page shows a photo with a Play button. Pressing it opens a YouTube player over the page (muted, without videos from other channels at the end); Escape, a click beside the video or the close button closes it.
Field (video in src/content/pages/about.ts) |
What it is |
|---|---|
youtubeId |
The video: the part after youtu.be/ or watch?v= in its YouTube address |
image |
The photo shown before the video plays |
caption |
The line over the photo |
playLabel, playerTitle, closeLabel |
What screen readers hear for the Play button, the player and the close button |
cursor |
The custom cursor’s word over the photo (“Play”) |
The demo plays 8AHPXm9Y6mI, the original Framer template’s promo video. It isn’t yours to keep: upload your own video
to YouTube and put its ID here. The player is built in src/app/about/page.tsx (youtubeEmbed): to use another video
service, change the address it builds.
Text that is not in content/
Section titled “Text that is not in content/”Almost every word is content, including the form’s messages (contact.ts). The few interface words that never change
per site live in the code:
- “Main” (the menu’s name for screen readers) in
src/components/site/Header.tsx; - the date format of the posts (“Jun 25, 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 project’s services exist, 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.