Skip to content
Sign inJoin waitlist

Editing the content — Catchup Astro

All the words of this Astro template live in src/content/, and its photos and client logos in src/assets/images/: plain JSON files you edit while npm run dev shows the result.

No CMS is needed: text goes between quotes and entries are separated by commas. If you would rather manage content in Sanity, Payload, Strapi or Directus, see Using a headless CMS.

src/content/
site.json name, title, description, domain, menu, header button, contact details, booking link, socials, footer
pages/home.json the copy of the home page
pages/about.json …and of every other page
collections/*.json the work, the services, the testimonials, the posts and the legal pages
routes.ts the URL of every page
schemas.ts the fields each kind of item has, and which are required

Not sure which file holds a piece of text? The page maps label every section of every page with its file.

src/content/site.json holds what appears on every page:

Field Shown where
site.name The browser title suffix (“About | Catchup”), share cards and the logo’s name for screen readers. Put your own (your studio’s name).
site.title The browser title of the home page
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 menu in the header (and the phone menu): Home, Studio, Works, Services, Insights
headerAction The mint “Contact” button at the right of the header (and in the phone menu)
contact The e-mail and the phone number: on Contact, and the e-mail behind the footer’s “Email Us”
bookingHref The link of the “Book a 15-min call” button in the footer
socials The social links: the footer’s Connect column and “Follow Us” on Contact
footer The footer: its text (text), the label of its button (action.label; the link is bookingHref), the column titles (sitemapLabel, servicesLabel, worksLabel, connectLabel), the Sitemap links (sitemap), the name of the e-mail link (emailLabel) and the copyright line (note, where {year} becomes the current year)

The footer’s Services and Recent Works columns and its legal links (Terms of Service, Privacy Policy) are built from the collections: a new service, project or legal page appears there by itself.

The demo’s e-mail (hello@example.com) and phone number are placeholders: replace both. The phone’s link is built from the number (+1 (347) 555-0123 calls tel:+13475550123), so write it the way people should read it. The social links open the networks’ home pages: point them to your own profiles.

The booking link appears twice, as https://cal.com/ in the demo: bookingHref in site.json (the footer’s button) and serviceItemPage.pricing.action.href in src/content/pages/services.json (the button under the price of every service page). Put your booking page in both, or /contact.

Links that start with https:// (the booking links, the social links, the awards, the team’s social handles) open in a new tab; mailto: and tel: links open the visitor’s mail app or phone.

The demo studio, Catchup, is named in the copy of several pages, the legal pages, the footer’s copyright line and the logo (Making it look like your brand). Search src/content/ for “Catchup” to find them all.

There is one file per page in src/content/pages/. Most hold the sections of that page and a meta entry:

{
"meta": {
"title": "About",
"description": "Catchup is a creative agency for branding, design, development and photography — strategy-led and…"
},
"hero": {
"title": "About",
"subtitle": "We Don’t Just Create — We Craft with Purpose"
}
}

title becomes the browser tab (“About | Catchup”), and description the text in search results and share cards (80–160 characters). Change the text between the quotes, keeping the field names: the sections read them by name. Apostrophes are safe inside the double quotes, and the demo uses the typographic ’. A double quote inside the text needs a backslash before it (\"). JSON has no comments and no comma after the last entry of a list; if the site stops building after an edit, that is usually why.

File Page
home.json Home: its meta, the hero (hero: the small tag, the title, the text and two buttons; the slides are your projects), the logo row’s title (logos), “About Us” (about: the heading, five numbers — brands, years, engagement, satisfaction, projects — with the photos of three of them, and the Core Values card with its button and photo), “What We Do” (services: the heading, the button and the mint call-to-action card with its two photos), “Our Work” (works), the heading of the testimonials (testimonials), the call to action (cta: the heading, two buttons, the photo) and “News & Insights” (blog). When meta.title is the same as site.title, the page’s browser title is site.title alone.
about.json About: its meta, the top (hero: the title, the subtitle, the text, faces — how many clients’ faces to show —, the count in the black disc, the stars and the line under them, the wide photo), “Our Philosophy” (philosophy: the heading, Our Vision, Our Mission, the button, two photos and four numbers), “Our Process” (process: the heading and four steps), “Awards” (awards: the heading, the column names, the awards and two photos) and “Teams” (team: the heading and the members)
work.json Work (workPage: its meta, the title, the years beside it, the text and the button) and the words of every project page (workItemPage: “Introduction”, the labels of the Details table, “Credits”, “The Challenge”, “Our Solution”, “The Outcome”, “Other works” and its button)
services.json Services (servicesPage: its meta, the title, the tagline, the text, the button, “What’s Included:” and “Learn More”) and the words of every service page (serviceItemPage: “What We Offer” with its decorative image, “Pricing Options” with the switch’s two names, “What is included”, “Starting at :”, the button under the price, “More Services”)
blog.json Blog: its meta, the title, the short line beside the text, the text, pageSize (how many posts load at a time) and what screen readers hear while more load
post.json The words of every post page: the breadcrumb (“Blog”), “Posted at”, “Posted on”, “More Blog”
contact.json Contact: the page (contactPage: its meta, the title, the text, the labels of the details, the location, the hours, “Follow Us” and the consent note under the button, which links the two legal pages by their slug) and the form (contactForm) (Forms)
legal.json The words of every legal page: “Last updated:”
not-found.json The 404 page: its browser title (meta.title), “404 Error”, the heading, the text and the button

The numbers of Home and About count up when they come into view. Each is a start, a value (where it stops), an optional decimals (1 for 4.9), a suffix (“+”, “%”, “★”) and a label; Home’s engagement and projects also have a text. Search engines and visitors without JavaScript see the final number.

Each award in awards.items (about.json) is a row link: title, event (the nomination), year and href (the page it opens, in a new tab). The demo’s links point at awwwards.com: link the real page of each award, or a page about it on your site.

Each member in team.members has a name, a role, a photo (src, alt) and a social chip: the handle, its href and a small icon (/images/icon-instagram.png in the demo).

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

File What it feeds
work.json The Home intro and the Home hero’s slides, the logo row on Home, “Our Work” on Home, the Work page, one page per project, “Other works” at the end of a project page (the first two others) and the footer’s Recent Works (the client names)
services.json The cards of “What We Do” on Home, the Services page, one page per service, “More Services” at the end of a service page (the three others), the footer’s Services column and the service tags of the projects
testimonials.json The testimonial rows on Home (the first half moving left, the rest right; the carousel of tablets and phones shows the first half), the clients’ faces on Home and About, the client beside each pricing plan, and the quote under “The Outcome” of a project
posts.json The Blog page, one page per post, the three newest on Home and “More Blog” at the end of a post
legal.json One page per legal page, the footer’s legal links and the consent note of the contact form

The order of the items in the file is the order on the site, except for posts, which are always newest first by their date. Every post is in the Blog page’s HTML from the start, so search engines find them all.

Copy an existing entry, paste it where it should appear (mind the comma between entries), and change the values:

{
"slug": "harbour-coffee",
"title": "Harbour — Coffee Roasters",
"client": "Harbour",
"summary": "A warm, hand-drawn identity and packaging system for a coastal roastery.",
"image": { "src": "/images/work-harbour.jpg", "alt": "Coffee bags on a wooden counter by a window" },
"logo": { "src": "/images/logo-harbour.svg", "alt": "Harbour logo" },
"services": ["branding", "photography"],
"year": "2026",
"timeline": "6 Weeks",
"credits": [
{ "role": "Creative Director", "name": "Ana Lopez" },
{ "role": "Photographer", "name": "Sam Ortiz" }
],
"challenge": {
"title": "…",
"text": "…",
"gallery": [
{ "src": "/images/work-harbour-challenge-1.jpg", "alt": "…" },
{ "src": "/images/work-harbour-challenge-2.jpg", "alt": "…" }
]
},
"solution": {
"title": "…",
"text": "…",
"gallery": [
{ "src": "/images/work-harbour-solution-1.jpg", "alt": "…" },
{ "src": "/images/work-harbour-solution-2.jpg", "alt": "…" },
{ "src": "/images/work-harbour-solution-3.jpg", "alt": "…" }
]
},
"outcome": { "title": "…", "text": "…", "gallery": [] }
}

Here’s what each field does:

  • slug is the URL: /work/harbour-coffee.
  • title is the card’s title, the hero slide’s title and the page’s title.
  • client is the name in the footer’s Recent Works and the Details table, and the logo’s name in the logo row on Home.
  • summary is shown on the card, the hero slide and beside “Introduction” on the page, and is the page’s search description (followed by the start of the challenge’s text when it is under 80 characters).
  • image is the full-screen photo of the Home hero, the card’s photo and the wide photo of the project page.
  • logo is the client’s logo: on the project page’s photo and in the moving row of logos on Home. The demo’s are SVG files 200 px tall, drawn in black.
  • services lists the slugs of its services, in order: the tags on the card and the hero slide, and the links of the Details table. Each tag links to that service’s page, so a slug that matches no service shows the slug and leads to a missing page.
  • year, timeline and credits (a role and a name each) fill the Details and Credits tables.
  • challenge, solution and outcome are the three stories of the page, each a title and a text. The Challenge shows the first two photos of its gallery side by side, Our Solution the first three (one wide, two under it); The Outcome shows no photo, but the quote of the project’s client. Give the first two stories at least that many photos.

The client’s quote is the testimonial whose work is the project’s slug (see Testimonials); without one, The Outcome ends with its text.

{
"slug": "consulting",
"name": "Consulting",
"summary": "Workshops and audits that give your team a clear creative direction.",
"thumbnail": { "src": "/images/service-consulting-thumb.jpg", "alt": "…" },
"image": { "src": "/images/service-consulting.jpg", "alt": "…" },
"overview": { "title": "We Help Teams Make Better Creative Decisions", "text": "…" },
"offer": {
"title": "A Practical, Hands-On Consulting Service",
"text": "…",
"includes": ["Brand audit", "Creative workshop", "Roadmap", "…"]
},
"pricing": {
"title": "Choose the Engagement Model That Fits Your Business",
"project": {
"price": "$1,500+",
"includes": ["Audit", "Workshop", "Roadmap", "2-Week Delivery"],
"notes": ["*Clear scope", "*One-time delivery", "*Ideal for new teams"],
"testimonial": "lena-f"
},
"monthly": {
"price": "$900",
"includes": ["Monthly session", "Reviews", "Priority answers", "Quarterly roadmap"],
"notes": ["*Flexible", "*Cancel anytime", "*Great for growing teams"],
"testimonial": "amir-d"
}
}
}
  • slug is the URL: /service/consulting, and the value projects use in their services list.
  • name is the label above the service page’s title, the title of the cards and the footer link, and the tag on the projects; the page’s “Our Consulting Deliverables Include:” is built from it.
  • summary is the text of the cards on Home, Services and “More Services”.
  • thumbnail is the square photo of the cards on Home and “More Services”; image the wide photo under the service page’s title and the photo beside its card on Services.
  • overview is the service page’s title and the paragraph under it, and the page’s search description.
  • offer is “What We Offer”: its title, its text and the deliverables, shown with a check each (eight in the demo). The Services page shows the first four under “What’s Included:”.
  • pricing is “Pricing Options”: its title and the two plans of the Per Project / Per Month switch. Each plan has a price (plain text, “$2,500+”), four includes, three notes (written with their leading “*”) and a testimonial: the slug of the client shown beside the plan, with their own quote. A slug that matches no testimonial stops the build with Unknown testimonial "…".

A new service gets its page, a card on Home and Services, a link in the footer and an entry in sitemap.xml on the next build. Home’s “What We Do” is laid out for four services: three cards in a row, then the fourth beside the call-to-action card; a fifth and more join the fourth. Keep at least three services: the first row expects three.

Each testimonial in testimonials.json has a slug, a name, a role (“CEO at Northbyte”), a photo (src, alt), a rating (1 to 5 stars) and a quote (the demo writes it with its quotation marks, “…”). Give one a work — a project’s slug — and its quote closes that project’s page. Services name testimonials by slug for their pricing plans.

Add or remove entries freely: Home’s rows split the list in half, and About shows the faces of the first hero.faces entries (four in the demo).

{
"slug": "our-new-studio",
"title": "Our New Studio",
"category": "Design",
"date": "2026-06-01",
"excerpt": "We moved: a look at the new space and what it changes for our clients.",
"image": { "src": "/images/post-our-new-studio.jpg", "alt": "…" },
"content": [
{ "type": "paragraph", "text": "First paragraph." },
{ "type": "heading", "level": 3, "text": "1. A section title" },
{ "type": "paragraph", "text": "More text with **bold** words." }
]
}
  • slug is the URL: /blog/our-new-studio.
  • category is one of Branding, Design, Development and Photography: the pill on the card and the “Posted on” of the page. “More Blog” lists up to two other posts of the same category. To add a category, add its name to the list in postSchema in src/content/schemas.ts.
  • date ("2026-06-01") orders the posts, newest first, and is shown as “Jun 1, 2026”.
  • excerpt is the card’s text, the line under the page’s title and the page’s search description (followed by the start of the first paragraph when it is under 80 characters).
  • image is the card’s photo and the cover of the page.
  • content is the article (rich text).

legal.json holds the Terms of Service and the Privacy Policy: a slug (/legal/terms-of-service), a title, the date of the last update and the content (rich text). The demo’s text is a sample that names Catchup: have your own terms and policy written for your business and country. The contact form’s consent note links both by their slug (consent in contact.json): change it there too if you rename one.

Delete the entry (and the comma before it, if it was the last one). Its page, its footer link and its sitemap entry disappear on the next build. Before you delete a service, take its slug out of the projects’ services; before you delete a testimonial, check that no plan names it. Places that link an item as text stay as they are: check the buttons and links of the page copy.

src/content/schemas.ts is the reference: it lists every field, which are optional (.optional()), and a comment for the ones that are not obvious. npm run check and npm run build report a missing field (a misspelled name counts as missing) with the collection, the item and the field.

A post’s content and a legal page’s content are lists of blocks:

"content": [
{ "type": "paragraph", "text": "A paragraph with **bold**, *italic* and a [link](/contact).\nA second line." },
{ "type": "heading", "level": 3, "text": "A heading" },
{ "type": "quote", "text": "A quotation." },
{ "type": "list", "ordered": false, "items": [
[{ "type": "paragraph", "text": "**First:** an item" }],
[{ "type": "paragraph", "text": "**Second:** another" }]
] }
]
  • Paragraphs and headings. Every heading is drawn the same way, in the Heading 3 style; level (2 to 6) is kept for a CMS but doesn’t change the look.
  • Quotes get a line at their left.
  • Lists are bulleted ("ordered": false) or numbered (true); each item is a list of blocks, usually one paragraph.
  • Inside the text: words between double asterisks (**…**) are bold, between single asterisks italic, text is a link (underlined, orange on hover; an https:// link opens in a new tab), and \n starts a new line. Manrope is loaded upright only, so an italic word is the browser’s slanted version of the regular text (Making it look like your brand).
  1. Put the file in src/assets/images/.
  2. Refer to it in the content as /images/<file>, with an alt.

Astro resizes, compresses and converts the photos (to WebP) when the site builds, so each device gets a size that fits. The download’s placeholders show the size each photo was designed for; use photos at least as large:

Photos Demo size How it is shown
A project’s image 2400 × 1600 The Home hero, the whole window; the project page’s wide photo (1140 × 750 on desktop); the cards (a photo over the text on desktop, beside it on tablets, 240 px tall on phones); the Home intro’s 268 × 200 window
A project’s Challenge photos 1200 px wide, portrait (1200 × 1593 to 1200 × 2100 in the demo) Two side by side at 560 : 750
A project’s Solution photos 2400 × 1600, then two of 1200 × 800 One wide at 1140 : 750, two side by side at 560 : 368
A project’s logo SVG, 200 px tall 260 × 78 on the project’s photo (72 × 22 on phones), 130 × 25 in the logo row on Home
A service’s thumbnail 800 × 800 Square, on the service cards
A service’s image 2400 × 1500 to 2400 × 1700 Under the service page’s title (1140 × 721 on desktop); beside the card on Services, 492 px tall on desktop and 228 on phones
The “What We Offer” image (serviceItemPage.offer.image) 500 × 500 A decorative square beside the offer of every service page, 250 px on desktop
A post’s image 2400 × 1600 The page’s cover at 1.9 : 1, the cards at 367 : 240
The About photo (hero.image) 2400 × 1600 Wide under the title, 1140 × 618 on desktop
About’s philosophy photos (side, wide) 1200 × 821 and 2400 × 843 Beside the vision card; wide (1140 × 400) with the logo in its corner
About’s award photos 600 × 400 Two portrait frames, 274 × 364 on desktop, cropped
Team photos 800 × 1200 367 × 494 on desktop
Home’s number photos (about.brands.image, engagement.image, projects.image) 800 × 681 to 1600 × 897 Behind three of the number cards, under a dark veil
The Core Values photo (about.values.image, a post’s cover in the demo) 2400 × 1600 Under the Core Values card: 365 px wide on desktop, a 100 px strip on tablets and phones
Home’s “What We Do” photos (services.cta.image, side) 1600 × 800 and 600 × 900 Above and beside the mint call-to-action card
Home’s call-to-action photo (cta.image) 2400 × 1345 16 : 9, with the logo in its middle
Testimonial photos 200 × 200 Round: 42 px on About, 54 px on Home’s numbers, small on the cards
The team’s social icon 80 × 80 20 px
The share image (public/opengraph-image.png) 2400 × 1260 Shared links (below)

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 that follow the screen change shape between phone, tablet and desktop, so keep the subject away from the edges. A content path that points to a missing file stops the build with its name.

Every photo has an alt: a short description for screen readers and search engines. Write one for each photo you change (an empty "alt": "" marks a picture as decoration, as the “What We Offer” image).

Files that browsers and social networks ask for by name live in public/:

File What it is
public/icon-light.png, public/icon-dark.png The icon in the browser tab (180 × 180): the first (black) for a light browser theme, the second (white) for a dark one
public/apple-icon.png The icon on a phone’s home screen (200 × 200)
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” and “Main, fixed” (the menu’s names for screen readers) in src/components/site/Header.astro, and “Menu” and “Close” (the phone menu button) in src/components/site/Bar.astro;
  • “Our … Deliverables Include:” on a service page, in src/pages/service/[slug].astro;
  • the names screen readers hear for the testimonial carousel (“Testimonials”, “Previous”, “Next”, “Page 1 of 3”) in src/components/sections/HomeTestimonials.astro and src/design-system/scripts/testimonial-carousel.ts, and for the stars (“5 out of 5 stars”) in src/design-system/components/cards/TestimonialCard.astro and src/components/sections/AboutTitle.astro;
  • the date format (“Jun 1, 2026”) in src/lib/format.ts;
  • the page’s language, lang="en", in src/layouts/Layout.astro.

Search for the word and you will find it.

Terminal window
npm run check
npm run build

npm run check compares the collections with their schemas and the page copy with the sections that read it, and names the file and the field that is missing. A successful build means every page still renders and every image it shows exists. Neither checks that links written as text ("/contact") lead somewhere: click through the site once with npm run preview after big changes. See Going live for the rest of the checklist.