Skip to content
Sign inJoin waitlist

Editing the content — Lookis 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, the photographer, menu, social links, contact details, footer
pages/home.ts the copy of the home page
pages/about.ts …and of every other page
pages/shared.ts the testimonials and the "See what I do" gallery, shown on several pages
collections/*.ts projects (portfolio.ts) and services (services.ts)
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 | Lookis”), share cards, the logo link’s name 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.
owner The photographer: name, place (the town before the header’s clock, “Asheville, (NC)”) and timeZone (the clock’s time zone, an IANA name such as "Europe/London")
navigation The header’s links (and the phone menu): Portfolio, About, Services, Contact
socials The social links: in the Home hero, on About and Contact, and in the footer’s Social column
bookingHref The “Schedule a call” button of every service page
contact E-mail and phone, with their labels (“Email :”, “Phone :”): the footer’s Contact column
footer The footer: the photo behind it (image), “Let’s Connect” (title), its line (text), the button (action), the titles of its three columns (quickLinksLabel, contactLabel, socialLabel), the Quick Links (quickLinks), the “Contact me” link under the contact details (contactAction) and the copyright line (note, where {year} becomes the current year)

The demo’s e-mail (hello@example.com) and phone number are placeholders: replace both. 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.

The booking link is written in three places, all https://cal.com/ in the demo: bookingHref and footer.action in site.ts, and hero.primary (“Book a session”) in src/content/pages/home.ts. Put your booking page (or /contact) in all three.

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 photographer’s name and town appear in many places: owner, the footer’s line and copyright, the copy of every page, the testimonials, the projects and the services. The logo draws the name too (Making it look like your brand). Search src/content/ for “Daniel”, “Mercer” and “Asheville” 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 a meta entry:

export const about = {
meta: {
title: "About", // browser tab: "About | Lookis"
description: "Daniel Mercer is a photographer…", // search results and share cards (80–160 characters)
},
image: { src: "/images/about-1.jpg", alt: "…" },
intro: { label: "About me", portrait: { … }, title: "Hello, I’m Daniel Mercer, …" },
…
};

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 (the testimonials’ quotes are written that way).

File Page
home.ts Home: the hero (the name that runs across the top, the photo, the introduction, “Book a session” and “See my portfolio”), “About me” (the title, three paragraphs, the closing line, two buttons and four photos), “Selected Projects” (the heading, the button and count, how many projects show), “My numbers” (the heading, four numbers with a line each, the photo) and the heading of “My Services”. Its meta.title is the whole browser title, without the suffix.
about.ts About: the page photo, the label with the small portrait and the title, “My little story” (two photos, three paragraphs, “See my service”), the four numbers (without lines) and “Awards & Recognitions” (the awards, the photo and imageAfter, the award it follows)
portfolio.ts Portfolio (portfolioPage): the heading, the “All” tab, the filter’s name for screen readers and the text they hear while more projects load; and the fixed words of every project page (projectPage: “Date”, “Service”, “Overview”, “Project Gallery”, “Related Projects”)
services.ts Services (servicesPage): the photo, the heading and two paragraphs, and “Questions” (the heading and six questions with their answers); and the fixed words of every service page (servicePage: “Price :”, “Schedule a call”, “Perfect for”, “What’s Included”, “Other Services”)
contact.ts Contact: the page photo, the label with the small portrait and the title, three paragraphs, the title of the form card and the form itself (contactForm, Forms)
shared.ts The testimonials block and the “See what I do” gallery (below)
not-found.ts The 404 page: its browser title, the photo, “404”, the title and the two buttons

Home and About each have their own four numbers: facts.items in home.ts (with a line under each) and facts in about.ts (without). Change both when your numbers change.

src/content/pages/shared.ts holds two blocks that several pages show from one copy:

  • testimonials: the label and title, the photo behind the block, the names of the slideshow’s two arrows for screen readers, and the clients’ words (items: quote, name, role, photo). Shown on Home, Services and every service page. The slideshow moves to the next quote every four seconds, in the order of the list, and starts again after the last; any number of quotes works.
  • showcase: “See what I do”, the block above the footer: the heading with its line, “Contact me”, the five photos and the Instagram button over them (instagram: its label and address; the photos link there too). Shown on Home, About, Portfolio, Services, every service page and, without the heading, on Contact. Project pages and the 404 page don’t have it.

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

File What it feeds
portfolio.ts Portfolio (every project, with a filter tab per service), one page per project, Home’s “Selected Projects” (the first six: projects.count in home.ts) and “Related Projects” at the end of a project page (up to three other projects of the same service)
services.ts The rows of “My Services” on Home and the cards on Services (every service), one page per service, the tabs of the Portfolio filter (after “All”, in the file’s order), the “Service” of a project page and “Other Services” at the end of a service page (the first three others)

The order of the items in the file is the order on the site. Nothing is sorted by date: the demo lists the projects newest first, so put a new project first to show it first on Home and Portfolio. Portfolio shows four projects at first and four more each time the visitor scrolls close to the spinner under the list; every project 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: "harbour-at-dawn", // the URL: /portfolio/harbour-at-dawn
title: "Harbour at Dawn", // the card, the page's title and its browser title
summary: "A slow morning with the fishing boats of a small harbour.", // under the title, on the card, in search results
date: "2026-05-20", // shown as "May 20, 2026"; also the date of the page in sitemap.xml
service: "travel-documentary", // the slug of a service in services.ts
details: [ // "Overview": rich text, below
{ type: "paragraph", text: "First paragraph." },
{ type: "paragraph", text: "Second paragraph." },
],
image: { src: "/images/portfolio-harbour-at-dawn.jpg", alt: "…" }, // the card's photo and the page's photo
gallery: [ // "Project Gallery": the photos under the overview, in this order
{ src: "/images/portfolio-harbour-at-dawn-1.jpg", alt: "…" },
…
],
}

A project page shows the main photo on the left (it stays in view as you scroll on tablets and desktops), and on the right the title, the summary, the date and the service’s name, “Overview” and the gallery, one photo under the other. Then “Related Projects”: up to three other projects of the same service, in the file’s order (two on tablets); the block is left out when the service has no other project.

service must be the slug of a service, written exactly: it decides the project’s Portfolio tab, the service’s name on the project page and its related projects. A project whose service matches no service shows under “All” only, without a service name.

The demo’s projects have five gallery photos each; any number works. A summary shorter than 80 characters is followed in search results by the start of the overview, so the description is long enough (describe in src/lib/format.ts).

{
slug: "family-sessions", // the URL: /services/family-sessions; also what projects name in `service`
name: "Family Sessions", // the row's and card's title, the Portfolio tab, the label of its page, the browser title
summary: "Relaxed portraits of the people you live with.", // the page's big title, the row's and card's text, search results
price: "$400 – $700", // the pill on rows and cards, and "Price :" on its page (any text)
image: { src: "/images/service-family-sessions.jpg", alt: "…" }, // the page's photo and the row's thumbnail
content: [ // rich text under the price; the demo starts with an italic line
{ type: "paragraph", text: "*Still moments. Honest presence.*" },
{ type: "paragraph", text: "…" },
],
perfectFor: ["…", "…", "…", "…"], // "Perfect for": up to four lines, numbered 01–04
included: ["…", "…", "…", "…", "…"], // "What’s Included": up to five lines, numbered 01–05
}

A service page shows its photo on the left and, on the right, its name, its summary as the page title, the price, the content, “Schedule a call” (bookingHref in site.ts), “Perfect for”, “What’s Included” and three other services. An empty line in perfectFor or included ("") leaves its row out; the other rows keep their numbers.

A new service also gets its own tab in the Portfolio filter, a row on Home and a card on Services. To fill its tab, set the service of its projects to its slug. If you rename a service’s slug, change the projects that name it too.

Delete the entry. Its page and its sitemap entry disappear on the next build. Before you remove a service, move its projects to another service (their service), or they fall out of every tab but “All”.

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: project details and service content

Section titled “Rich text: project details and service content”

A project’s details and a service’s content are a list of paragraphs:

details: [
{ type: "paragraph", text: "**Harbour at Dawn** is a plain paragraph with an *italic* phrase." },
{ type: "paragraph", text: "Shot in digital + 35mm film.\nEdited with warmth and restraint." }, // \n: a line break
]

Text is plain apart from three marks: words between double asterisks are bold (**…**, weight 700), words between single asterisks are set in italics (*…*), and \n starts a new line inside a paragraph. There are no links inside the text. Inter is loaded upright only, so an italic phrase is the browser’s slanted version of the regular text (Making it look like your brand).

The component that draws rich text (RichText in the design system) can also show headings and lists, but the content type allows paragraphs only (RichTextBlock in src/content/types.ts). To use them, widen that type to the one in src/design-system/components/patterns/RichText.tsx.

  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
The Home hero (hero.image), also the footer’s background (footer.image in site.ts) 2400 × 1600 The hero fills the window under the name, the footer runs the full width: both cropped
The 404 photo 1920 × 1280 Fills the window
The photo behind the testimonials (shared.ts) 2400 × 1600 Full width, 750 px tall on desktop, 600 on tablets, 650 on phones
The page photo of About, Contact, Services, a service and a project (the left column) 1200 × 1500, 1200 × 800, 1200 × 2133, 1200 × 800, 1440 × 1440 Portrait: about 4 : 5 on phones and tablets, half the width and 85 % of the window’s height on desktop, cropped. A portrait photo at least 1200 px wide fits best.
A project’s image on its card (Home, Portfolio, “Related Projects”) 1440 × 1440 565 : 600
A project’s gallery 1440 px wide, any height 0.74 : 1 (a tall frame), cropped
A service’s image as the row’s thumbnail on Home 1200 × 800 200 × 145 on desktop, a wide strip on tablets, square on phones
Home “About me”: the portrait, the tall photo, the wide photo and the narrow one 1200 × 1500, 1200 × 1500, 1440 × 952, 1000 × 667 4 : 5; as tall as the column; 1.51 : 1; as tall as the wide one
About “My little story”: two photos (the same files as Home’s last two) 1440 × 952, 1000 × 667 1.51 : 1, the second as tall as the first
The awards photo (About) 1200 × 1600 3 : 4
The small portrait beside “About me” and “Contact Me” 400 × 400 (About), the hero photo (Contact) 200 × 200
“My numbers” (Home), also the Services page photo 1200 × 2133 502 px wide and as tall as the numbers on desktop; full width, 400 / 350 px tall on tablets and phones
The five photos of “See what I do” 600 px wide Square, 5 in a row on desktop, 4 on tablets, 2 on phones
Client portraits of the testimonials 200 × 200 80 × 80 (40 × 40 on phones)

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 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, like the footer’s).

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 light one for a light browser theme, the dark one for a dark theme (180 × 180 each; 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.

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) and “Menu” (the phone menu button’s label) in src/components/site/Header.tsx;
  • the date format of projects (“Apr 14, 2024”) in src/lib/format.ts, and the clock’s format (“7:32 AM”) in src/components/site/Clock.tsx;
  • 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 service matches a service, 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.