Editing the content — Marai Neesu 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 person, menu, e-mail and the footer pages/home.ts the copy of the home page pages/about.ts …and of every other page collections/*.ts projects, products, posts, services, testimonials, experiences, tools, social profiles 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 | Marai Neesu”), share cards, the share image’s description |
site.title |
The browser title of any page without its own (the 404 page has its own; Home uses home.meta.title) |
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. |
person |
The header’s logo: your photo (avatar), your name and your city (location), the seal’s name for screen readers (verifiedLabel) and the two lines the desktop logo shows under the pointer (hoverLines, “Back to” / “Homepage”). The CV shows the same photo. |
navigation |
The menu in the header from tablets up: Home, Portfolio, About, Service |
phoneNavigation |
The phone menu, which lists every main page: Home, Portfolio, About, Service, Product, Course, Blog |
menuLabels |
The phone menu button’s two labels (“Menu”, “Close”) and the menu’s name for screen readers (“Main”) |
contactLink |
The “Contact” button of the header (and of the phone menu) |
contact.email |
The e-mail of the Home hero (it rolls to an orange copy under the pointer) and the “Email Me” links of the services and the two FAQs |
footer |
The footer: the call to action (ctaLabel, ctaTitle and its two buttons, cvLink and contactLink), the two link columns (columns), the third column (city, its local time from timeZone, and the reach links), the copyright line (copyright, where {year} becomes the current year, rights and the credit link), the profiles of the bottom row (profiles) and the link at its right (endLink) |
The demo’s e-mail (hello@example.com) is a placeholder, and it is written twice: contact.email and the “Email” link
of footer.reach. Replace both. The social and profile links (footer.reach, footer.profiles, the social
profiles collection, the CV’s contact links) open the networks’ home pages or example.com: point them to your own.
Links that start with https:// open in a new tab; mailto: links open the visitor’s mail app; links to pages of
the site (/contact) open in the same tab.
The person’s name appears in many places: site, person, the copy of Home, About and the CV, the quotes of the
testimonials, the page descriptions and the alt texts of the photos. Search src/content/ for “Neesu” and for “Dubai”
to find them all. The footer’s credit, “Template by Marcframe”, is yours to keep or remove (footer.credit).
Page copy
Section titled “Page copy”There is one file per page (or per pair of pages) in src/content/pages/. Most export an object with the sections of
that page and a meta entry:
export const about = { meta: { title: "About", // browser tab: "About | Marai Neesu" description: "Marai Neesu, a digital designer…", // search results and share cards (80–160 characters) }, breadcrumb: "About", title: "Hello, I am Neesu a digital designer based in Dubai. …", …};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) |
Home: the hero (title, portrait, greeting, the rolling roles, text, “More About me”, the e-mail’s label and “Social Profile:”), “My latest work” (projects.count: four), “Work with Me” (the price line, “More Details” and the custom-request row), “Trusted by Professionals”, “Products Spotlight” (six cards: four on tablets, three on phones), the course card under the products (course) and “Latest Articles & Publications” (blog.count: three). Its meta.title is the whole browser title. |
about.ts (about) |
About: the breadcrumb, the long title, the three photos and two paragraphs (intro), “My Experiences” with its two buttons and “Stack” |
projects.ts (projectsPage) |
Projects (/project): the title, the text and “My Awesome Clients” with its five logos (clients) |
project.ts (projectPage) |
The words shared by every project page: “Client”, “Service”, “Date”, “Project Overview”, “Key Highlights”, “See more projects” (more.count: two other projects) and “Go Back” |
services.ts (servicesPage) |
Services (/service): the title, the text, the price line, the custom-request row and the eight questions (faq) |
courses.ts (coursePage) |
Course (/course): the whole course — the cover, “About Course”, the four modules and their lessons, “Key Learning Outcomes”, the overview card (features, price, “Enroll Today”) and the nine questions (faq) |
cv.ts (cv) |
CV: the profile (status chip, greeting, rolling roles), About, Contact, Education, the titles and counts of Project, Work Experience and Writing (four each), and Certifications |
products.ts (products, product) |
Products (/product): the title, the text and the card buttons; and the words shared by every product page (the two buttons, “Overview”, “More Products”, “Go Back”) |
blog.ts (blog, post, newsletter) |
Blog: the title, the text, pageSize (six posts before “Load More”) and “Load More”; the words shared by every post page (the trail, “Date”, “Category”, “See more posts”, “Go Back”); the newsletter box and its form (Forms) |
contact.ts (contactPage, contactForm) |
Contact: the breadcrumb, “Let’s Connect”, the text and the inquiry form (Forms) |
not-found.ts (notFoundPage) |
The 404 page: its browser title, “/404”, the title, the line and the button |
shared.ts (shared) |
Words several pages use that screen readers hear: the stars of a testimonial (“Rated 5 out of 5”), the names of the testimonial slideshow and its arrows, the breadcrumb trail’s name and its first link (“Home”) |
Collections
Section titled “Collections”src/content/collections/ holds the lists the site builds pages and sections from:
| File | What it feeds |
|---|---|
projects.ts |
The Projects page (every project), one page per project, Home (the first four: projects.count in home.ts), “See more projects” at the end of a project page (the first two others) and the CV’s Project (the first four) |
products.ts |
The Products page (every product), one page per product, Home (the first six) and “More Products” at the end of a product page (the first three others; four on tablets) |
posts.ts |
The Blog, one page per post, Home (the first three), the CV’s Writing (the first four) and “See more posts” at the end of a post (up to three other posts of its category; two on tablets) |
services.ts |
“Work with Me” on Home and the Services page (every service), the “I’m interested in” choices of the Contact form and the badge of a project page |
testimonials.ts |
“Trusted by Professionals” on Home: every testimonial, moving in a ticker (a slideshow on phones) |
experiences.ts |
“My Experiences” on About (every experience) and the CV’s Work Experience (the first four) |
tools.ts |
“Stack” on About: every tool, three by three |
socials.ts |
The four two-letter tiles under the e-mail in the Home hero |
The order of the items in the file is the order on the site. Nothing sorts by date: the demo’s posts are newest first, so put a new post first to show it first, and the same goes for projects and experiences. The Blog shows six posts and a “Load More” button that shows the rest; every post is in the page’s HTML from the start, so search engines find them all.
Adding a project
Section titled “Adding a project”Copy an existing entry, paste it below, and change the values:
{ slug: "harbor-coffee-roasters", // the URL: /project/harbor-coffee-roasters title: "Harbor - Coffee Roasters Website", // the title of the page and of the card summary: "An online shop and story for…", // under the title, on the card and as the page's search description service: "Web Design", // one of the services' titles: the badge over the title links to it date: "2026-03-01", // the month, on its first day: shown as "March 2026" client: "Harbor Coffee", image: { src: "/images/project-harbor-cover.jpg", alt: "…" }, // the card and the photo beside the title (4 : 3) description: [{ type: "paragraph", text: "…" }], // "Project Overview" (rich text, below) highlights: [{ type: "list", items: [[{ type: "paragraph", text: "**Fast checkout:** …" }]] }], // "Key Highlights" gallery: [ // two photos beside the overview and one wide photo, or none { src: "/images/project-harbor-gallery-1.jpg", alt: "…" }, { src: "/images/project-harbor-gallery-2.jpg", alt: "…" }, { src: "/images/project-harbor-gallery-3.jpg", alt: "…" }, ],}A project page shows the badge, the title, the summary, Client / Service / Date beside the main photo, then “Project
Overview” with the first two gallery photos, “Key Highlights” with the third one, wide, and two other projects. The
gallery may be empty (the demo’s Makadam has none): the photos are then left out. The badge shows the project’s
service and links to the “More Details” address of the service with the same title, or to the Services page when
none matches.
Adding a product, post or anything else
Section titled “Adding a product, post or anything else”| Add | Fields |
|---|---|
| Product | slug, title, tagline (under the title), price ("$59": the card’s pill and the buy button, “Buy - $59”), category (kept for a CMS; not shown), buyUrl (the cart button of the card and the buy button of the page), demoUrl (“Live Demo”), image (the card and the main image), screenshots (two images under it), specification (the paragraph under the tagline, and the page’s search description) and overview (rich text) |
| Post | slug, title, image (the card’s photo, 4 : 3, and the wide cover), category (any words: posts with the same one are listed under each other as “See more posts”; the demo uses Product Design, UX/UI and Web Design), date ("2024-07-08", shown as “Jul 8, 2024”) and body (rich text). Its search description is the first paragraph of the body. |
| Service | slug, title, description, price ("$3,000": “Starting at $3,000 per project”), url (where “More Details” leads; the demo’s go to https://contra.com/) and images (four photos that roll beside the card) |
| Testimonial | name, role ("CEO of EcoShop"), photo (round, 50 px), quote and rating (1 to 5 stars) |
| Experience | slug, title (the job), company, period ("January 2023 - June 2023", written as you want it read), url (the CV links the job title to it) and description |
| Tool | slug, title, category ("Design Tool"), url (the card opens it in a new tab), logo (a square image, shown 50 px) and description (kept for a CMS; not shown) |
| Social profile | label (the network’s name for screen readers), short (the two letters of the tile), href and icon (an SVG shown on the tile under the pointer) |
A new project, product or post gets its own page, and its entry in sitemap.xml, on the next build. Services,
testimonials, experiences, tools and social profiles have no pages.
A few lists elsewhere name items as text and don’t follow the collections: a project’s service must match a
service’s title for the badge to link it, and the menu, the footer columns and the buttons hold their addresses as
text.
Counts the layouts expect
Section titled “Counts the layouts expect”Most lists take any number of items. A few blocks are laid out for a fixed number, so keep it:
| Where | How many |
|---|---|
| A service | four images (two columns of two that roll) |
| A product | two screenshots |
| A project | three gallery photos, or none |
| The About intro | three photos (intro in about.ts) |
| Home, the products | count six, tabletCount four and phoneCount three in home.ts: the grid is three by three on desktop and two by two on tablets |
Removing an item
Section titled “Removing an item”Delete the entry. Its page and its sitemap entry disappear on the next build. A project whose service names a
service you removed keeps its badge, which then links to the Services page.
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, projects and products
Section titled “Rich text: posts, projects and products”A post’s body, a project’s description and highlights and a product’s overview are lists of blocks:
body: [ { type: "heading", level: 3, text: "Transforming Concepts into Tangible Forms" }, { type: "paragraph", text: "A paragraph with a **bold** start and a `max-width` in code." }, { type: "paragraph", text: "First line\nSecond line" }, // \n: a line break { type: "list", ordered: true, items: [ // numbers; leave out ordered for bullets [{ type: "paragraph", text: "First item" }], [{ type: "paragraph", text: "Second item" }], ] },]Headings take a level from 2 to 6; the demo’s posts use level 3 (Heading 3) and the products level 5 (Heading 5).
Text has two marks: words between double asterisks are bold (weight 700), and words between backticks are marked
up as code (drawn in the text’s own font, as on the original); \n starts a new line inside a paragraph. There are no links and no italics inside the text. Each list item is itself a
list of blocks, so an item can hold a nested list. The demo’s posts use headings, paragraphs and both kinds of list; the
projects’ highlights are a bulleted list with a bold start on each item.
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 each photo was designed for; use photos at least as large:
| Photos | Demo size |
|---|---|
Your photo (person.avatar): the logo and the CV |
180 × 180 (shown round, 34 px in the logo and 90 px on the CV) |
| The Home hero portrait | 600 × 830 (shown 150 × 200) |
| The About photos: the portrait, the detail and the wide photo | 1100 × 1573, 800 × 1200 and 1100 × 1438 (cropped to their frames) |
A project’s image and the first two gallery photos |
1440 × 1080 (4 : 3) |
A project’s third gallery photo (the wide one) |
2240 × 1680 (4 : 3) |
A product’s image and screenshots |
1200 × 814 (shown 510 × 346 on desktop) |
A post’s image |
1600 px wide, portrait or landscape (the card crops it to 4 : 3, the cover to 300 / 350 / 400 px tall) |
A service’s four images |
400 px wide, 265 to 500 tall (two columns of small photos) |
A testimonial’s photo |
150 × 150 or smaller (shown round, 50 px) |
A tool’s logo |
100 × 100 (shown 50 px) |
| The Course cover | 2240 × 1260 (under a dark veil) |
| The course card on Home | 640 × 360 |
| The newsletter photo (Blog) | 1200 × 675 |
The client logos of the Projects page (client-1.svg … client-5.svg) are sample logos from Logoipsum: replace them
with your clients’ logos, shown 25 px tall; give each its width in projectsPage.clients.logos (projects.ts). The
social icons (social-*.svg, the networks’ marks on a small white square) show at 26 px over a tile under the pointer;
the tool logos (tool-*.png, one SVG) name the tools you use and remain their owners’ trademarks.
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 }: 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, as the demo does for the service
photos).
Two things sit outside the content because browsers and social networks ask for them by name:
| File | What it is |
|---|---|
src/app/icon.png, src/app/apple-icon.png |
The icon in the browser tab and 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 (contactForm and newsletter.form). The few interface
words that never change per site live in the code:
- the date formats (“Jul 8, 2024” for posts, “September 2023” for projects) 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 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.