Editing the content — Metuo Astro
All the words of this Astro template live in src/content/ and its photos in src/assets/images/: plain JSON files you edit while npm run dev shows them.
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, "Book a session", contact details, socials, footer pages/home.json the copy of the home page pages/about.json …and of every other page pages/shared.json the founder, her quote, the call to action band, the ratings, the e-mail line, the social icons pages/pricing.json the plans (Home, Services) pages/faq.json the questions (Home, Services, Contact, every post) pages/book.json the booking section and its form (Home, Services, Contact) collections/*.json the services, the client stories, the team, 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 requiredNot 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.json holds what appears on every page:
| Field | Shown where |
|---|---|
site.name |
The browser title suffix (“About | Metuo”), share cards and the logo’s name for screen readers. It is the template’s name in the demo: put your own (your name, or your practice’s). |
site.title |
The browser title of the home page |
site.description |
Search results and share cards of the home page and 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) and the footer’s Quick links: Home, About, Services, Stories, Journal |
bookLink |
The “Book a session” button in the header, the phone menu and the footer (/contact in the demo) |
contact |
E-mail, phone and address with their labels (“Email:”, “Phone:”, “Location:”): the footer’s Contact column |
socials |
The footer’s Social media column (text links) |
footer |
The footer: its background photo (image), the line under the logo (about), the column titles (contactLabel, quickLinksLabel, socialLabel), the legal links (legalLinks) and the copyright line (note, where {year} becomes the current year) |
The demo’s e-mail (hello@example.com), phone number and London address are placeholders: replace them. The phone’s
link is built from the number ((555) 123-4567 calls tel:5551234567), so write it the way people should read it. The
social links open the networks’ home pages: point them to your own profiles.
Some details are written in more than one file, so change each copy:
| Detail | Where |
|---|---|
| Your e-mail | contact.email in site.json; the “send us an email” link (questionLine.link.href in shared.json, a mailto:); “Contact support” (support.cta.href in faq.json, a mailto:) |
| Your social links | socials in site.json (the footer’s text links) and socialLinks in shared.json (the icons of the call to action band and the booking section) |
| The founder (Dr. Amelia Hart) | founder (Home’s card with her bio) and founderQuote (the quote band) in shared.json, and one client story’s quote in collections/testimonials.json |
| The numbers (“500+”, “4.9/5”…) | stats in home.json, facts in service.json, clientRatings and ctaBand.trust in shared.json |
| Your place | hero.place in home.json (“London, United Kingdom (GMT+1)”, plain text at the foot of the hero) and contact.address in site.json |
Links that start with https:// open in a new tab, except the social icons, which open in the same tab as in the
original design; mailto: and tel: links open the visitor’s mail app or phone. Search src/content/ for “Amelia”,
“example.com” and “London” to find them all.
Page copy
Section titled “Page copy”There is one file per page in src/content/pages/, and one per block that several pages share. Most page files hold
the sections of that page and a meta entry:
{ "meta": { "title": "About", "description": "Meet Metuo: our vision and mission, the values behind every coaching session and the team of coaches who support your personal growth." }, "pageTitle": { "title": "About Metuo", "lead": "Helping you build clarity, confidence, and emotional resilience through personalized coaching and compassionate support.", "image": { "src": "/images/about-hero.jpg", "alt": "A counsellor reaching for a client's hand, a tablet on her knee" } }}title becomes the browser tab (“About | Metuo”), 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 ’ in places. A double quote inside the
text needs a backslash before it (\"), as in the quotes of the stories and the founder. 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 or block |
|---|---|
home.json |
Home: the hero (hero: the pill “Available for treatment”, the title, the text, two buttons, the foot line note, the place and the photo), “About us” (about: the title, two paragraphs, the button, the small photo, “What we believe” and its four points), “How we can help” (service: the heading, count, the number of services shown, and “View all services”), “Why choose us” (why: the heading, four points and four photos), “Our process” (step: the heading, four steps and two photos), the video (video.src), “Client stories” (stories: the heading, count, the number of stories, and “Read full stories”), the four numbers under them (stats) and the heading of “Our journal” (blogIntro). Home has no meta: its browser title and description are site.title and site.description. |
about.json |
About: its meta, the photo title (pageTitle), “Vision & Mission” (vision: the heading, the two cards, the line “We’ve Got Something For Everyone.” with its button, two photos), “Our core values” (values: the heading, five values, five photos), the video (video.src) and the heading of “Meet the team” (teamIntro) |
service.json |
Services: its meta, the photo title and the four numbers under the service cards (facts) |
testimonial.json |
Client Stories: its meta, the photo title, “Key Outcomes:” (outcomesLabel) and the name screen readers hear for the list of stories (storiesLabel) |
blog.json |
The Journal: its meta, the photo title and the list (list: pageSize, the posts shown at first and loaded each time, and the text screen readers hear while more load) |
post.json |
The block under every post: “More insights for you.” with its label and text, and count, the number of related posts (3) |
contact.json |
Contact: its browser title and description (the page’s words are the booking section and the questions) |
legal.json |
The legal pages: “Last Updated:” (updatedLabel) and a search description per page, by its slug (descriptions) |
not-found.json |
The 404 page: its browser title (meta.title), the title, the text and the button |
shared.json |
Blocks of several pages: founder (Home’s founder card), founderQuote (the dark quote band on Home, About and Services), ctaBand (the call to action band “Ready to take the first step…” on Home, About, Client Stories and the Journal, and its trust line, also in the booking section), clientRatings (the four client photos, “65+” and the rating), questionLine (the “send us an email” sentence), socialLinks (the social icons) and bioLabel (“Bio of”, the name screen readers hear for the “+” of a team card, followed by the person’s name) |
pricing.json |
The plans on Home and Services: the heading, the switch’s words (billing), “Includes:”, “* Perfect for:”, the three plans and the closing row (more, with the “Contact us” link) |
faq.json |
The questions on Home, Services, Contact and every post: the heading, the “Still have questions?” card (support, with Olivia’s photo and “Contact support”) and the six items |
book.json |
The booking section on Home, Services and Contact: the heading (intro; on Contact its title is the page’s <h1>), “Tell us about you.” (formTitle) and the form (form, see Forms) |
Each plan in pricing.json has a name, a description, two prices written as they should read (monthly: “$129”,
yearly: “$1,049”), the lines under “Includes:” (includes, as many as you like), the line after “* Perfect for:”
(perfectFor), its button (cta) and, for one of them, "featured": true, which makes it the Green card. The switch
shows the monthly prices first and rolls every price to the yearly one; “/month” and “/year” (billing.perMonth,
billing.perYear) follow the price, and billing.discount (“(32% off)”) sits beside “Yearly”. The template doesn’t
compute the discount: write the prices and the discount yourself.
Questions
Section titled “Questions”The questions are items in faq.json, each a question and an answer (plain text). The first starts open; each
opens and closes on its own. The same six appear on Home, Services, Contact and every post.
Steps and points
Section titled “Steps and points”“Our process” (step.items in home.json) is a list of title and text, numbered 01, 02, … in their order; one step
is open at a time, the first at the start. “Why choose us” (why.points, with why.images) and “Our core values”
(values.points, with values.images in about.json) pair each point with the photo at the same place in the list:
keep both lists the same length.
Collections
Section titled “Collections”src/content/collections/ holds the lists the site builds pages and sections from:
| File | What it feeds |
|---|---|
services.json |
Home’s “How we can help” (the first four: service.count in home.json), the six cards of Services, and the session types of the booking form (one checkbox per service, by name) |
testimonials.json |
Home’s pinned story card (the first four: stories.count in home.json) and every story card of Client Stories |
team.json |
“Meet the team” on About |
posts.json |
The Journal (every post, six at a time as the visitor scrolls), one page per post, Home’s “Our journal” (the first three) and “More insights for you.” under a post (up to three other posts of its category) |
legal.json |
One page per legal page (/legal/<slug>), linked from the footer (footer.legalLinks in site.json) |
The order of the items in the file is the order on the site. The Journal doesn’t sort posts by date: the demo lists them newest first, so put a new post first to show it first, on Home too. Every post is in the Journal’s HTML from the start, so search engines find them all.
Adding a post
Section titled “Adding a post”Copy an existing entry, paste it where it should appear (mind the comma between entries), and change the values:
{ "slug": "small-rituals-for-calmer-mornings", "title": "Small rituals for calmer mornings", "excerpt": "How a few quiet minutes before the day begins can lower stress, sharpen focus and set the tone for everything that follows.", "image": "/images/post-small-rituals-for-calmer-mornings.jpg", "imageAlt": "A cup of tea and an open notebook on a windowsill at sunrise", "category": "Mindset", "date": "2026-06-02", "body": [ { "type": "paragraph", "text": "First paragraph.\nA second line in the same paragraph." }, { "type": "heading", "level": 3, "text": "Start before your phone does" }, { "type": "paragraph", "text": "A paragraph with a **bold** phrase." } ]}Here’s what each field does:
slugis the URL:/blog/small-rituals-for-calmer-mornings.titleis the card’s title (one line, cut with “…” when too long) and the post’s title.excerptis shown under the title on the post page, and is its search description (followed by the start of the first paragraph when it is under 80 characters).imageis the card’s photo and the cover of the post, and the picture shown when the post is shared;imageAltdescribes it (the cards show the photo as decoration: the title names the link).categoryis shown on the card and above the post’s title, and decides “More insights for you.”: other posts with exactly the samecategory. The demo uses Growth, Mindset and Coaching.date("2026-06-02") is shown as “Jun 2, 2026” on the card.bodyis the article (rich text).
Adding a service
Section titled “Adding a service”{ "slug": "grief-support", "name": "Grief support", "summary": "A gentle space to understand loss, honour your feelings and find a way forward at your own pace.", "image": "/images/service-grief-support.jpg", "images": ["/images/service-grief-support-1.jpg", "/images/service-grief-support-2.jpg"], "imageAlts": ["…the big photo…", "…the first small photo…", "…the second small photo…"], "values": ["Coping with loss", "Processing emotions", "Rebuilding routines", "Finding meaning"]}slugidentifies the service; services have no page of their own.nameis the row’s and the card’s title, and the label of its checkbox in the booking form (submissions carry it).summaryis the text of the open row and of the card.imageis the big photo andimagesthe two small ones under it;imageAltsholds the three descriptions, in that order.valuesis the dotted list (four in the demo).
The rows on Home show the first service.count services (4); Services shows all of them, numbered in their order. A new
service is a new checkbox of the booking form at once.
Adding a client story
Section titled “Adding a client story”{ "slug": "maya-lopez", "name": "Maya Lopez", "role": "Product Designer", "photo": "/images/client-maya-lopez.png", "headline": "Learning to slow down without falling behind", "quote": "\"Coaching gave me the space to ask what I really wanted from my work.\"", "image": "/images/story-maya-lopez.jpg", "imageAlt": "A woman reading by a window in soft morning light", "outcomes": ["Clearer priorities", "Less weekend work", "More energy for family"]}nameandrolesit beside the small portrait (photo), shown as decoration since the name is next to it.headlineis the story’s title,quotethe story (the demo writes it with its quotation marks,\"…\").imageis the big photo beside the story,imageAltits description.outcomesis the list under “Key Outcomes:” on Client Stories (three in the demo); Home’s card doesn’t show it.
Adding a team member
Section titled “Adding a team member”Each member in team.json has a slug, a name, a role, a photo (2 : 3) and a bio, shown when the “+” on the
photo is pressed. The cards follow the order of the file, three per row on desktops. Members have no page of their own.
Legal pages
Section titled “Legal pages”legal.json holds Terms of Service and Privacy Policy: a slug (the URL, /legal/terms-of-service), a title, the date
of the last update (updated, an ISO date shown as “Dec 18, 2023”) and a body (rich text). The demo’s
texts are samples with placeholders such as [Your Company Name] and [URL]: have your own texts written for your
practice and the law where you work. Each page’s search description is in descriptions in pages/legal.json, by slug;
a page without one gets “
src/pages/legal/[slug].astro,
so add a description for any new page. Link a new legal page from footer.legalLinks in site.json.
Removing an item
Section titled “Removing an item”Delete the entry (and the comma before it, if it was the last one). A post’s or legal page’s page and its sitemap entry
disappear on the next build; a removed service also leaves the booking form. Places that link an item as text stay as
they are: check footer.legalLinks and the buttons of the page copy.
What each field means
Section titled “What each field means”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.
Rich text
Section titled “Rich text”A post’s and a legal page’s body is a list of blocks:
"body": [ { "type": "paragraph", "text": "A paragraph with a **bold** phrase.\nA new line inside it." }, { "type": "heading", "level": 3, "text": "A heading" }, { "type": "list", "ordered": false, "items": [ [{ "type": "paragraph", "text": "**First point:** its text." }], [{ "type": "paragraph", "text": "Second point." }] ] }]- Paragraphs: words between double asterisks (
**…**) are set in bold, words between single ones (*…*) in italics, and\nstarts a new line. There are no links inside the text. - Headings are set in Heading 3 and are
<h2>elements under the page’s title, whatever theirlevel. - Lists:
"ordered": truenumbers the items (1., 2., …), otherwise each gets a bullet. Each item is itself a list of blocks, so an item can hold several paragraphs or a list of its own.
Images
Section titled “Images”- Put the file in
src/assets/images/. - Refer to it in the content as
/images/<file>, with analt.
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 |
|---|---|---|
The Home hero (home-hero.jpg) |
2400 × 1600 | The full width, as tall as the window (80 % on tablets), grows into place on load and scrolls at half speed |
The photo titles of About, Services, Client Stories and the Journal (*-hero.jpg) |
2400 × 1600 | The full width, 78 % of the window’s height (80 % on tablets, except About), at half speed |
The founder quote band (founder-background.jpg) |
2400 × 1600 | Behind the quote, the full width, moving as the band scrolls |
The footer’s photo (footer.image) |
2400 × 3600 | Behind the footer card, the full width |
A post’s image |
2280 × 1520 | The card at 367 : 244, and the post’s cover, the full content width and 78 % of the window’s height |
Home’s “About us”: the small photo and the founder card (home-about-1.jpg, home-about-2.jpg) |
1080 × 1620, 1000 × 1501 | 2 : 3 (zooming from 150 % as it scrolls in), and 520 : 737 |
The round founder portrait (founder.png) and the FAQ card’s portrait (client-avatar.png) |
120 × 120 | Small circles beside the name |
“Why choose us” (why-*.jpg) and “Our core values” (about-value-*.jpg) |
1040 × 693 (one 2400 × 1600) | Squares, one under the other beside the points; a sliding row on phones |
| The two photos of “Our process” (Home) and “Vision & Mission” (About) | 1090 × 1636 (tall) and 1310 × 873 | A tall photo under a light veil, with a 3 : 2 photo over its bottom |
A service’s image and images |
800 × 533 and 400 × 267 (some 640 and 320 wide) | 3 : 2: the big photo over the two small ones (on Home’s rows, a 400 × 500 column at the left on desktops) |
A story’s image |
1140 × 760 | The big photo beside the story: on Home’s card the right half on desktops, a 270 px column on tablets, a strip on phones; on Client Stories from tablets up |
A story’s photo (client-*.png) |
200 × 300 | 100 × 150, portrait (80 × 120 on Home’s card on phones and tablets) |
A team member’s photo |
750 × 1125 | 2 : 3 |
The four client photos of the ratings (avatar-*.png) |
100 × 100 | 42 px circles |
The social icons (icon-*.svg) |
24 × 24 | As they are, in the call to action band and the booking section |
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 photo as decoration, as the footer’s and the founder quote’s).
src/assets/images/logo.png and logo-white.svg are copies of the logo for use elsewhere (an e-mail signature, a
social profile); the site draws its logo from Logo.astro (Making it look like your brand).
Videos
Section titled “Videos”Home and About each have a full-width video band: video.src in src/content/pages/home.json and about.json. In the
demo both are clips from Pexels, played from the Pexels website (https://videos.pexels.com/…); they are not in the
download. Replace them before you publish, with clips you have the rights to:
- Put the file in
public/, for examplepublic/videos/home.mp4(an MP4, H.264, 1280 × 720 is plenty; keep it a few MB). - Set
"src": "/videos/home.mp4"invideo.src.
A full URL to a file on your own video host works too. The video is muted, loops, has no controls, loads only when it
first comes into view and plays only while it is on screen; it is shown at 16 : 9 and cropped to fill the band. To
remove a band, delete its <VideoSection … /> line from the page file (Pages and sections).
Files browsers ask for
Section titled “Files browsers ask for”Files that browsers and social networks ask for by name live in public/:
| File | What it is |
|---|---|
public/icon-light.svg, public/icon-dark.svg |
The icon in the browser tab: the Green leaf for a light browser theme, a light one for a dark theme |
public/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, apart from the posts, which share their cover.
Text that is not in content/
Section titled “Text that is not in content/”Almost every word is content, including the form’s messages (book.json) and the names screen readers hear. 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 name) in
src/components/site/Header.astro; - the date format of the cards and legal pages (“May 28, 2026”) in
src/lib/format.ts; - the fallback description of a legal page in
src/pages/legal/[slug].astro; - the share image’s description in
src/lib/meta.ts; - the page’s language,
lang="en", insrc/layouts/Layout.astro.
Search for the word and you will find it.
After editing
Section titled “After editing”npm run checknpm run buildnpm 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.