Skip to content
Sign inJoin waitlist

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 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 | 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.

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.

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.

“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.

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.

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:

  • slug is the URL: /blog/small-rituals-for-calmer-mornings.
  • title is the card’s title (one line, cut with “…” when too long) and the post’s title.
  • excerpt is 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).
  • image is the card’s photo and the cover of the post, and the picture shown when the post is shared; imageAlt describes it (the cards show the photo as decoration: the title names the link).
  • category is shown on the card and above the post’s title, and decides “More insights for you.”: other posts with exactly the same category. The demo uses Growth, Mindset and Coaching.
  • date ("2026-06-02") is shown as “Jun 2, 2026” on the card.
  • body is the article (rich text).
{
"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"]
}
  • slug identifies the service; services have no page of their own.
  • name is the row’s and the card’s title, and the label of its checkbox in the booking form (submissions carry it).
  • summary is the text of the open row and of the card.
  • image is the big photo and images the two small ones under it; imageAlts holds the three descriptions, in that order.
  • values is 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.

{
"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"]
}
  • name and role sit beside the small portrait (photo), shown as decoration since the name is next to it.
  • headline is the story’s title, quote the story (the demo writes it with its quotation marks, \"…\").
  • image is the big photo beside the story, imageAlt its description.
  • outcomes is the list under “Key Outcomes:” on Client Stories (three in the demo); Home’s card doesn’t show it.

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.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 “ for the Metuo website and its coaching services.” from <code dir="auto">src/pages/legal/[slug].astro</code>, so add a description for any new page. Link a new legal page from <code dir="auto">footer.legalLinks</code> in <code dir="auto">site.json</code>.</p> <div class="sl-heading-wrapper level-h3"><h3 id="removing-an-item">Removing an item</h3><a class="sl-anchor-link" href="#removing-an-item"><span aria-hidden="true" class="sl-anchor-icon"><svg width="16" height="16" viewBox="0 0 24 24" fill="currentColor"><path d="m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 1 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 0 0-1.42-1.42m8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 1 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 0 0 0 1.42 1 1 0 0 0 1.42 0l3.88-3.89a4.49 4.49 0 0 0 0-6.33M8.83 15.17a1 1 0 0 0 .71.29 1 1 0 0 0 .71-.29l4.92-4.92a1 1 0 1 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42"></path></svg></span><span class="sr-only" data-pagefind-ignore>Section titled “Removing an item”</span></a></div> <p>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 <code dir="auto">footer.legalLinks</code> and the buttons of the page copy.</p> <div class="sl-heading-wrapper level-h3"><h3 id="what-each-field-means">What each field means</h3><a class="sl-anchor-link" href="#what-each-field-means"><span aria-hidden="true" class="sl-anchor-icon"><svg width="16" height="16" viewBox="0 0 24 24" fill="currentColor"><path d="m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 1 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 0 0-1.42-1.42m8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 1 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 0 0 0 1.42 1 1 0 0 0 1.42 0l3.88-3.89a4.49 4.49 0 0 0 0-6.33M8.83 15.17a1 1 0 0 0 .71.29 1 1 0 0 0 .71-.29l4.92-4.92a1 1 0 1 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42"></path></svg></span><span class="sr-only" data-pagefind-ignore>Section titled “What each field means”</span></a></div> <p><code dir="auto">src/content/schemas.ts</code> is the reference: it lists every field, which are optional (<code dir="auto">.optional()</code>), and a comment for the ones that are not obvious. <code dir="auto">npm run check</code> and <code dir="auto">npm run build</code> report a missing field (a misspelled name counts as missing) with the collection, the item and the field.</p> <div class="sl-heading-wrapper level-h2"><h2 id="rich-text">Rich text</h2><a class="sl-anchor-link" href="#rich-text"><span aria-hidden="true" class="sl-anchor-icon"><svg width="16" height="16" viewBox="0 0 24 24" fill="currentColor"><path d="m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 1 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 0 0-1.42-1.42m8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 1 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 0 0 0 1.42 1 1 0 0 0 1.42 0l3.88-3.89a4.49 4.49 0 0 0 0-6.33M8.83 15.17a1 1 0 0 0 .71.29 1 1 0 0 0 .71-.29l4.92-4.92a1 1 0 1 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42"></path></svg></span><span class="sr-only" data-pagefind-ignore>Section titled “Rich text”</span></a></div> <p>A post’s and a legal page’s <code dir="auto">body</code> is a list of blocks:</p> <div class="expressive-code"><figure class="frame not-content"><figcaption class="header"></figcaption><pre data-language="json"><code><div class="ec-line"><div class="code"><span style="--0:#9ECBFF;--1:#032F62">"body"</span><span style="--0:#E1E4E8;--1:#24292E">: [</span></div></div><div class="ec-line"><div class="code"><span class="indent"><span style="--0:#E1E4E8;--1:#24292E"> </span></span><span style="--0:#E1E4E8;--1:#24292E">{ </span><span style="--0:#79B8FF;--1:#005CC5">"type"</span><span style="--0:#E1E4E8;--1:#24292E">: </span><span style="--0:#9ECBFF;--1:#032F62">"paragraph"</span><span style="--0:#E1E4E8;--1:#24292E">, </span><span style="--0:#79B8FF;--1:#005CC5">"text"</span><span style="--0:#E1E4E8;--1:#24292E">: </span><span style="--0:#9ECBFF;--1:#032F62">"A paragraph with a **bold** phrase.</span><span style="--0:#79B8FF;--1:#005CC5">\n</span><span style="--0:#9ECBFF;--1:#032F62">A new line inside it."</span><span style="--0:#E1E4E8;--1:#24292E"> },</span></div></div><div class="ec-line"><div class="code"><span class="indent"><span style="--0:#E1E4E8;--1:#24292E"> </span></span><span style="--0:#E1E4E8;--1:#24292E">{ </span><span style="--0:#79B8FF;--1:#005CC5">"type"</span><span style="--0:#E1E4E8;--1:#24292E">: </span><span style="--0:#9ECBFF;--1:#032F62">"heading"</span><span style="--0:#E1E4E8;--1:#24292E">, </span><span style="--0:#79B8FF;--1:#005CC5">"level"</span><span style="--0:#E1E4E8;--1:#24292E">: </span><span style="--0:#79B8FF;--1:#005CC5">3</span><span style="--0:#E1E4E8;--1:#24292E">, </span><span style="--0:#79B8FF;--1:#005CC5">"text"</span><span style="--0:#E1E4E8;--1:#24292E">: </span><span style="--0:#9ECBFF;--1:#032F62">"A heading"</span><span style="--0:#E1E4E8;--1:#24292E"> },</span></div></div><div class="ec-line"><div class="code"><span class="indent"><span style="--0:#E1E4E8;--1:#24292E"> </span></span><span style="--0:#E1E4E8;--1:#24292E">{ </span><span style="--0:#79B8FF;--1:#005CC5">"type"</span><span style="--0:#E1E4E8;--1:#24292E">: </span><span style="--0:#9ECBFF;--1:#032F62">"list"</span><span style="--0:#E1E4E8;--1:#24292E">, </span><span style="--0:#79B8FF;--1:#005CC5">"ordered"</span><span style="--0:#E1E4E8;--1:#24292E">: </span><span style="--0:#79B8FF;--1:#005CC5">false</span><span style="--0:#E1E4E8;--1:#24292E">, </span><span style="--0:#79B8FF;--1:#005CC5">"items"</span><span style="--0:#E1E4E8;--1:#24292E">: [</span></div></div><div class="ec-line"><div class="code"><span class="indent"><span style="--0:#E1E4E8;--1:#24292E"> </span></span><span style="--0:#E1E4E8;--1:#24292E">[{ </span><span style="--0:#79B8FF;--1:#005CC5">"type"</span><span style="--0:#E1E4E8;--1:#24292E">: </span><span style="--0:#9ECBFF;--1:#032F62">"paragraph"</span><span style="--0:#E1E4E8;--1:#24292E">, </span><span style="--0:#79B8FF;--1:#005CC5">"text"</span><span style="--0:#E1E4E8;--1:#24292E">: </span><span style="--0:#9ECBFF;--1:#032F62">"**First point:** its text."</span><span style="--0:#E1E4E8;--1:#24292E"> }],</span></div></div><div class="ec-line"><div class="code"><span class="indent"><span style="--0:#E1E4E8;--1:#24292E"> </span></span><span style="--0:#E1E4E8;--1:#24292E">[{ </span><span style="--0:#79B8FF;--1:#005CC5">"type"</span><span style="--0:#E1E4E8;--1:#24292E">: </span><span style="--0:#9ECBFF;--1:#032F62">"paragraph"</span><span style="--0:#E1E4E8;--1:#24292E">, </span><span style="--0:#79B8FF;--1:#005CC5">"text"</span><span style="--0:#E1E4E8;--1:#24292E">: </span><span style="--0:#9ECBFF;--1:#032F62">"Second point."</span><span style="--0:#E1E4E8;--1:#24292E"> }]</span></div></div><div class="ec-line"><div class="code"><span class="indent"><span style="--0:#E1E4E8;--1:#24292E"> </span></span><span style="--0:#E1E4E8;--1:#24292E">] }</span></div></div><div class="ec-line"><div class="code"><span style="--0:#E1E4E8;--1:#24292E">]</span></div></div></code></pre><div class="copy"><div aria-live="polite"></div><button title="Copy to clipboard" data-copied="Copied!" data-code=""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." }] ] }]"><div></div></button></div></figure></div> <ul> <li><strong>Paragraphs:</strong> words between double asterisks (<code dir="auto">**…**</code>) are set in bold, words between single ones (<code dir="auto">*…*</code>) in italics, and <code dir="auto">\n</code> starts a new line. There are no links inside the text.</li> <li><strong>Headings</strong> are set in Heading 3 and are <code dir="auto"><h2></code> elements under the page’s title, whatever their <code dir="auto">level</code>.</li> <li><strong>Lists:</strong> <code dir="auto">"ordered": true</code> numbers 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.</li> </ul> <div class="sl-heading-wrapper level-h2"><h2 id="images">Images</h2><a class="sl-anchor-link" href="#images"><span aria-hidden="true" class="sl-anchor-icon"><svg width="16" height="16" viewBox="0 0 24 24" fill="currentColor"><path d="m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 1 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 0 0-1.42-1.42m8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 1 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 0 0 0 1.42 1 1 0 0 0 1.42 0l3.88-3.89a4.49 4.49 0 0 0 0-6.33M8.83 15.17a1 1 0 0 0 .71.29 1 1 0 0 0 .71-.29l4.92-4.92a1 1 0 1 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42"></path></svg></span><span class="sr-only" data-pagefind-ignore>Section titled “Images”</span></a></div> <ol> <li>Put the file in <code dir="auto">src/assets/images/</code>.</li> <li>Refer to it in the content as <code dir="auto">/images/<file></code>, with an <code dir="auto">alt</code>.</li> </ol> <p>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:</p> <table> <thead> <tr> <th>Photos</th> <th>Demo size</th> <th>How it is shown</th> </tr> </thead> <tbody> <tr> <td>The Home hero (<code dir="auto">home-hero.jpg</code>)</td> <td>2400 × 1600</td> <td>The full width, as tall as the window (80 % on tablets), grows into place on load and scrolls at half speed</td> </tr> <tr> <td>The photo titles of About, Services, Client Stories and the Journal (<code dir="auto">*-hero.jpg</code>)</td> <td>2400 × 1600</td> <td>The full width, 78 % of the window’s height (80 % on tablets, except About), at half speed</td> </tr> <tr> <td>The founder quote band (<code dir="auto">founder-background.jpg</code>)</td> <td>2400 × 1600</td> <td>Behind the quote, the full width, moving as the band scrolls</td> </tr> <tr> <td>The footer’s photo (<code dir="auto">footer.image</code>)</td> <td>2400 × 3600</td> <td>Behind the footer card, the full width</td> </tr> <tr> <td>A post’s <code dir="auto">image</code></td> <td>2280 × 1520</td> <td>The card at 367 : 244, and the post’s cover, the full content width and 78 % of the window’s height</td> </tr> <tr> <td>Home’s “About us”: the small photo and the founder card (<code dir="auto">home-about-1.jpg</code>, <code dir="auto">home-about-2.jpg</code>)</td> <td>1080 × 1620, 1000 × 1501</td> <td>2 : 3 (zooming from 150 % as it scrolls in), and 520 : 737</td> </tr> <tr> <td>The round founder portrait (<code dir="auto">founder.png</code>) and the FAQ card’s portrait (<code dir="auto">client-avatar.png</code>)</td> <td>120 × 120</td> <td>Small circles beside the name</td> </tr> <tr> <td>“Why choose us” (<code dir="auto">why-*.jpg</code>) and “Our core values” (<code dir="auto">about-value-*.jpg</code>)</td> <td>1040 × 693 (one 2400 × 1600)</td> <td>Squares, one under the other beside the points; a sliding row on phones</td> </tr> <tr> <td>The two photos of “Our process” (Home) and “Vision & Mission” (About)</td> <td>1090 × 1636 (tall) and 1310 × 873</td> <td>A tall photo under a light veil, with a 3 : 2 photo over its bottom</td> </tr> <tr> <td>A service’s <code dir="auto">image</code> and <code dir="auto">images</code></td> <td>800 × 533 and 400 × 267 (some 640 and 320 wide)</td> <td>3 : 2: the big photo over the two small ones (on Home’s rows, a 400 × 500 column at the left on desktops)</td> </tr> <tr> <td>A story’s <code dir="auto">image</code></td> <td>1140 × 760</td> <td>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</td> </tr> <tr> <td>A story’s <code dir="auto">photo</code> (<code dir="auto">client-*.png</code>)</td> <td>200 × 300</td> <td>100 × 150, portrait (80 × 120 on Home’s card on phones and tablets)</td> </tr> <tr> <td>A team member’s <code dir="auto">photo</code></td> <td>750 × 1125</td> <td>2 : 3</td> </tr> <tr> <td>The four client photos of the ratings (<code dir="auto">avatar-*.png</code>)</td> <td>100 × 100</td> <td>42 px circles</td> </tr> <tr> <td>The social icons (<code dir="auto">icon-*.svg</code>)</td> <td>24 × 24</td> <td>As they are, in the call to action band and the booking section</td> </tr> <tr> <td>The share image (<code dir="auto">public/opengraph-image.png</code>)</td> <td>2400 × 1260</td> <td>Shared links (<a href="#files-browsers-ask-for">below</a>)</td> </tr> </tbody> </table> <p>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.</p> <p>Every photo has an <code dir="auto">alt</code>: a short description for screen readers and search engines. Write one for each photo you change (an empty <code dir="auto">"alt": ""</code> marks a photo as decoration, as the footer’s and the founder quote’s).</p> <p><code dir="auto">src/assets/images/logo.png</code> and <code dir="auto">logo-white.svg</code> are copies of the logo for use elsewhere (an e-mail signature, a social profile); the site draws its logo from <code dir="auto">Logo.astro</code> (<a href="/docs/metuo/astro/design#logo">Making it look like your brand</a>).</p> <div class="sl-heading-wrapper level-h2"><h2 id="videos">Videos</h2><a class="sl-anchor-link" href="#videos"><span aria-hidden="true" class="sl-anchor-icon"><svg width="16" height="16" viewBox="0 0 24 24" fill="currentColor"><path d="m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 1 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 0 0-1.42-1.42m8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 1 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 0 0 0 1.42 1 1 0 0 0 1.42 0l3.88-3.89a4.49 4.49 0 0 0 0-6.33M8.83 15.17a1 1 0 0 0 .71.29 1 1 0 0 0 .71-.29l4.92-4.92a1 1 0 1 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42"></path></svg></span><span class="sr-only" data-pagefind-ignore>Section titled “Videos”</span></a></div> <p>Home and About each have a full-width video band: <code dir="auto">video.src</code> in <code dir="auto">src/content/pages/home.json</code> and <code dir="auto">about.json</code>. In the demo both are clips from Pexels, played from the Pexels website (<code dir="auto">https://videos.pexels.com/…</code>); they are not in the download. Replace them before you publish, with clips you have the rights to:</p> <ol> <li>Put the file in <code dir="auto">public/</code>, for example <code dir="auto">public/videos/home.mp4</code> (an MP4, H.264, 1280 × 720 is plenty; keep it a few MB).</li> <li>Set <code dir="auto">"src": "/videos/home.mp4"</code> in <code dir="auto">video.src</code>.</li> </ol> <p>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 <code dir="auto"><VideoSection … /></code> line from the page file (<a href="/docs/metuo/astro/pages#reordering-or-removing-a-section">Pages and sections</a>).</p> <div class="sl-heading-wrapper level-h3"><h3 id="files-browsers-ask-for">Files browsers ask for</h3><a class="sl-anchor-link" href="#files-browsers-ask-for"><span aria-hidden="true" class="sl-anchor-icon"><svg width="16" height="16" viewBox="0 0 24 24" fill="currentColor"><path d="m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 1 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 0 0-1.42-1.42m8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 1 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 0 0 0 1.42 1 1 0 0 0 1.42 0l3.88-3.89a4.49 4.49 0 0 0 0-6.33M8.83 15.17a1 1 0 0 0 .71.29 1 1 0 0 0 .71-.29l4.92-4.92a1 1 0 1 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42"></path></svg></span><span class="sr-only" data-pagefind-ignore>Section titled “Files browsers ask for”</span></a></div> <p>Files that browsers and social networks ask for by name live in <code dir="auto">public/</code>:</p> <table> <thead> <tr> <th>File</th> <th>What it is</th> </tr> </thead> <tbody> <tr> <td><code dir="auto">public/icon-light.svg</code>, <code dir="auto">public/icon-dark.svg</code></td> <td>The icon in the browser tab: the Green leaf for a light browser theme, a light one for a dark theme</td> </tr> <tr> <td><code dir="auto">public/apple-icon.png</code></td> <td>The icon on a phone’s home screen (180 × 180)</td> </tr> <tr> <td><code dir="auto">public/opengraph-image.png</code></td> <td>The picture shown when someone shares a link (2400 × 1260; 1200 × 630 or larger)</td> </tr> </tbody> </table> <p>The share image’s description for screen readers is <code dir="auto">shareImage.alt</code> in <code dir="auto">src/lib/meta.ts</code>, next to its size: change <code dir="auto">width</code> and <code dir="auto">height</code> 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.</p> <div class="sl-heading-wrapper level-h2"><h2 id="text-that-is-not-in-content">Text that is not in <code dir="auto">content/</code></h2><a class="sl-anchor-link" href="#text-that-is-not-in-content"><span aria-hidden="true" class="sl-anchor-icon"><svg width="16" height="16" viewBox="0 0 24 24" fill="currentColor"><path d="m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 1 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 0 0-1.42-1.42m8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 1 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 0 0 0 1.42 1 1 0 0 0 1.42 0l3.88-3.89a4.49 4.49 0 0 0 0-6.33M8.83 15.17a1 1 0 0 0 .71.29 1 1 0 0 0 .71-.29l4.92-4.92a1 1 0 1 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42"></path></svg></span><span class="sr-only" data-pagefind-ignore>Section titled “Text that is not in content/”</span></a></div> <p>Almost every word is content, including the form’s messages (<code dir="auto">book.json</code>) and the names screen readers hear. The few interface words that never change per site live in the code:</p> <ul> <li>“Main” (the menu’s name for screen readers) and “Menu” (the phone menu button’s name) in <code dir="auto">src/components/site/Header.astro</code>;</li> <li>the date format of the cards and legal pages (“May 28, 2026”) in <code dir="auto">src/lib/format.ts</code>;</li> <li>the fallback description of a legal page in <code dir="auto">src/pages/legal/[slug].astro</code>;</li> <li>the share image’s description in <code dir="auto">src/lib/meta.ts</code>;</li> <li>the page’s language, <code dir="auto">lang="en"</code>, in <code dir="auto">src/layouts/Layout.astro</code>.</li> </ul> <p>Search for the word and you will find it.</p> <div class="sl-heading-wrapper level-h2"><h2 id="after-editing">After editing</h2><a class="sl-anchor-link" href="#after-editing"><span aria-hidden="true" class="sl-anchor-icon"><svg width="16" height="16" viewBox="0 0 24 24" fill="currentColor"><path d="m12.11 15.39-3.88 3.88a2.52 2.52 0 0 1-3.5 0 2.47 2.47 0 0 1 0-3.5l3.88-3.88a1 1 0 1 0-1.42-1.42l-3.88 3.89a4.48 4.48 0 0 0 6.33 6.33l3.89-3.88a1 1 0 0 0-1.42-1.42m8.58-12.08a4.49 4.49 0 0 0-6.33 0l-3.89 3.88a1 1 0 1 0 1.42 1.42l3.88-3.88a2.52 2.52 0 0 1 3.5 0 2.47 2.47 0 0 1 0 3.5l-3.88 3.88a1 1 0 0 0 0 1.42 1 1 0 0 0 1.42 0l3.88-3.89a4.49 4.49 0 0 0 0-6.33M8.83 15.17a1 1 0 0 0 .71.29 1 1 0 0 0 .71-.29l4.92-4.92a1 1 0 1 0-1.42-1.42l-4.92 4.92a1 1 0 0 0 0 1.42"></path></svg></span><span class="sr-only" data-pagefind-ignore>Section titled “After editing”</span></a></div> <div class="expressive-code"><figure class="frame is-terminal not-content"><figcaption class="header"><span class="title"></span><span class="sr-only">Terminal window</span></figcaption><pre data-language="bash"><code><div class="ec-line"><div class="code"><span style="--0:#B392F0;--1:#6F42C1">npm</span><span style="--0:#E1E4E8;--1:#24292E"> </span><span style="--0:#9ECBFF;--1:#032F62">run</span><span style="--0:#E1E4E8;--1:#24292E"> </span><span style="--0:#9ECBFF;--1:#032F62">check</span></div></div><div class="ec-line"><div class="code"><span style="--0:#B392F0;--1:#6F42C1">npm</span><span style="--0:#E1E4E8;--1:#24292E"> </span><span style="--0:#9ECBFF;--1:#032F62">run</span><span style="--0:#E1E4E8;--1:#24292E"> </span><span style="--0:#9ECBFF;--1:#032F62">build</span></div></div></code></pre><div class="copy"><div aria-live="polite"></div><button title="Copy to clipboard" data-copied="Copied!" data-code="npm run checknpm run build"><div></div></button></div></figure></div> <p><code dir="auto">npm run check</code> 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 (<code dir="auto">"/contact"</code>) lead somewhere: click through the site once with <code dir="auto">npm run preview</code> after big changes. See <a href="/docs/metuo/astro/publish">Going live</a> for the rest of the checklist.</p> </div><footer class="sl-flex astro-ddtxxk7k"><div class="meta sl-flex astro-ddtxxk7k"></div><div class="pagination-links print:hidden astro-b5raizh3" dir="ltr"><a href="/docs/metuo/astro/install" rel="prev" class="astro-b5raizh3"><svg aria-hidden="true" class="astro-b5raizh3 astro-hkc32dio" width="16" height="16" viewBox="0 0 24 24" fill="currentColor" style="--sl-icon-size: 1.5rem;"><path d="M17 11H9.41l3.3-3.29a1.004 1.004 0 1 0-1.42-1.42l-5 5a1 1 0 0 0-.21.33 1 1 0 0 0 0 .76 1 1 0 0 0 .21.33l5 5a1.002 1.002 0 0 0 1.639-.325 1 1 0 0 0-.219-1.095L9.41 13H17a1 1 0 0 0 0-2Z"/></svg><span class="astro-b5raizh3">Previous<br class="astro-b5raizh3"><span class="link-title astro-b5raizh3">Install</span></span></a><a href="/docs/metuo/astro/design" rel="next" class="astro-b5raizh3"><svg aria-hidden="true" class="astro-b5raizh3 astro-hkc32dio" width="16" height="16" viewBox="0 0 24 24" fill="currentColor" style="--sl-icon-size: 1.5rem;"><path d="M17.92 11.62a1.001 1.001 0 0 0-.21-.33l-5-5a1.003 1.003 0 1 0-1.42 1.42l3.3 3.29H7a1 1 0 0 0 0 2h7.59l-3.3 3.29a1.002 1.002 0 0 0 .325 1.639 1 1 0 0 0 1.095-.219l5-5a1 1 0 0 0 .21-.33 1 1 0 0 0 0-.76Z"/></svg><span class="astro-b5raizh3">Next<br class="astro-b5raizh3"><span class="link-title astro-b5raizh3">Design</span></span></a></div></footer><footer class="fb-footer not-content"><p>© 2026 Framebrick by Marcframe. All rights reserved.</p><ul><li><a href="/support">Support</a></li><li><a href="/docs">Docs</a></li><li><a href="/license">License</a></li><li><a href="/legal/terms">Terms of service</a></li><li><a href="/legal/refund-policy">Refund policy</a></li><li><a href="/legal/privacy-policy">Privacy policy</a></li><li><a href="/legal/cookie-policy">Cookie policy</a></li><li><a href="https://x.com/hi_marcframe" target="_blank" rel="noopener">X (Twitter)</a></li></ul></footer></div></div></main></div></div></div></div></body></html>