Editing the content — Cerette 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 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, socials, footer pages/home.json the copy of the home page pages/about.json …and of every other page pages/forms.json the two inquiry forms and the block around them pages/cta.json the closing call to action of Home and the inner pages collections/*.json the projects, the services, the testimonials, 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 (“Contact | Cerette”), 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, About, Services, Projects, Blog |
headerAction |
The “Let’s talk” button at the right of the header (and in the phone menu) |
contact |
The phone, the e-mail and the address in the footer’s Contact column |
socials |
The social links after “Follow us:” at the bottom of the footer |
footer |
The footer: its text (text), its button (action), the Quick Links column (quickLinksLabel, quickLinks), the other column titles (servicesLabel, legalLabel, contactLabel), the labels of the contact details (phoneLabel, emailLabel, addressLabel), followLabel and the copyright line (note, where {year} becomes the current year) |
The footer’s Services and Legal columns are built from the collections: a new service or legal page appears there by itself.
The Contact page shows its own copy of the details: email, phone, address and hours in
src/content/pages/contact.json. Change them in both files. The demo’s e-mail (hello@example.com), phone number and
address are placeholders: replace them all. The phone’s link is built from the number (+1 (000) 123-4567 calls
tel:+10001234567), 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 buttons open https://cal.com/ in the demo. Put your booking page (or /contact) in each of them:
| Button | Field |
|---|---|
| “Book a call” on Home’s hero | hero.actions in src/content/pages/home.json |
| “Book a call” on About | title.actions in src/content/pages/about.json |
| “Book a call” on Projects | title.actions in src/content/pages/projects.json |
| “Book a call” on Services | actions in src/content/pages/services.json |
| “Schedule Consultation” in the call to action of Home, About, Projects, a project and a post | action in src/content/pages/cta.json |
site.json also has a bookingHref; no page reads it, so changing it changes nothing on the site.
Links that start with https:// (the booking links, the social links) open in a new tab; mailto: and tel: links
open the visitor’s mail app or phone.
The demo studio, Cerette, and its founder, Adrian Varell, are 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 “Cerette” to find them all.
Page copy
Section titled “Page copy”There is one file per page in src/content/pages/. Most hold the sections of that page and a meta entry:
{ "meta": { "title": "About the Studio", "description": "Meet Cerette, a modern architecture and construction studio: …" }, "title": { "title": "Studio.", "aside": "(Modern Architecture)" }}title becomes the browser tab (“About the Studio | Cerette”), 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 label, the text, the title, the video and two buttons); “About us” (about: the label, three figures, the title, the text, three points, two buttons and the photo); “Our Projects” (projects: the heading, the button, the cards’ “View Project”); the founder’s quote (quote); “Our Services” (services: the heading and the “More details” link of the switcher); “Why Cerette” (why: the heading, the photo and six points with their icon); the achievements (achievement: four figures, the label, the table’s column names, six awards and three photos); the testimonials’ heading (testimonials, with ratingLabel, what screen readers hear before a rating); “Latest Insights” (blog: the heading, the button and count, how many posts). 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 (title: the big title, the small text beside it, the intro, two buttons and the photo); the statement under it (statement: the lead and two paragraphs); four figures; the founder’s quote (quote); “Meet The Team” (team: the heading, pageSize — how many cards show at first on tablets and phones — and what screen readers hear while more load); “Our Achievements” (awards: the heading, the photo, the column names and six rows) |
projects.json |
Projects: its meta, the top (title: the big title, the years beside it, the text, two buttons), the cards’ “View Project” and the testimonials’ heading |
project.json |
The words of every project page: “(Scroll to explore)”, the labels of the facts (Year, Location, Duration, Area, Services), “The Brief”, “Scope of Work” and “Other Work” (its title, its button, the cards’ text and count, how many projects) |
services.json |
Services: its meta, the top (the title, the small text, the intro, two buttons), the cards’ “View Details”, “Why Cerette” (why) and the founder’s quote (quote) |
service.json |
The words of every service page: the label “Service”, “About service” and “What’s included in the services?” |
blog.json |
Blog (blogPage: its meta, the top, pageSize — how many posts load at a time on phones, tablets and desktops — and what screen readers hear while more load) and the words of every post page (postPage.similar: “Similar posts”, its button and count) |
contact.json |
Contact: its meta, the title, the small text, the two paragraphs of the intro, the e-mail, phone, address and working hours |
forms.json |
The two forms (contactForm, serviceForm) and the block beside them on Services and the service pages (inquiry: the heading and the photo) (Forms) |
cta.json |
The closing call to action: the title, the text, the button and the photo |
legal.json |
The words of every legal page: “Last updated:” |
not-found.json |
The 404 page: its browser title (meta.title), “Error 404”, the subtitle, the text, the button and the photo |
The founder’s quote is written three times (quote in home.json, about.json and services.json), and “Why Cerette”
twice (why in home.json and services.json), so each page can say something different: change every copy.
Figures and awards
Section titled “Figures and awards”The figures (“275+ Projects Completed”, “320K+ Area Developed”) are plain text, not counters: a value, an optional
suffix (“+”, “%”, “y”) and a label. Home and About each have their own (about.figures and achievement.figures in
home.json, figures in about.json).
Each award (achievement.awards in home.json, awards.rows in about.json) is a row of the table: number (“01”),
title, category, year and text. The demo’s awards are invented: put your own, or remove the rows.
The home video
Section titled “The home video”Home’s hero plays a video under a half-black veil: hero.video in src/content/pages/home.json, with a src (the video
file) and a poster (the photo shown until it plays, /images/home-hero-poster.jpg). The demo’s src points to a file
hosted on another site: it is not part of the template and may stop working, so use your own. Put an MP4 file in
public/ (for example public/videos/hero.mp4) and write "src": "/videos/hero.mp4", or give the full address of a
video you host elsewhere. It plays muted and in a loop; keep it short and small (a few MB), and replace the poster with
a frame of your video.
Collections
Section titled “Collections”src/content/collections/ holds the lists the site builds pages and sections from:
| File | What it feeds |
|---|---|
projects.json |
“Our Projects” on Home (the first six), the Projects page, one page per project and “Other Work” at the end of a project page (the first three others) |
services.json |
The services switcher on Home, the Services page, one page per service, the footer’s Services column, a project’s Services, and the Project type of the service page’s form |
testimonials.json |
The testimonials on Home and Projects |
team.json |
“Meet The Team” on About |
posts.json |
The Blog page, one page per post, the newest on Home (“Latest Insights”) and “Similar posts” at the end of a post |
legal.json |
One page per legal page and the footer’s Legal column |
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.
Adding a project
Section titled “Adding a project”Copy an existing entry, paste it where it should appear (mind the comma between entries), and change the values:
{ "slug": "harbour-house", "title": "Harbour House", "summary": "A timber family home on the coast, opened to the light and the sea.", "category": "Residential", "image": { "src": "/images/project-harbour-house.jpg", "alt": "Timber house with large windows above the sea" }, "year": "2026", "location": "Portland, Maine", "duration": "10 Months", "area": "420 m²", "services": ["architecture", "interior"], "overview": "A family home designed around the view and the light of the coast.", "brief": "…", "scope": "…", "images": [ { "src": "/images/project-harbour-house-1.jpg", "alt": "…" }, { "src": "/images/project-harbour-house-2.jpg", "alt": "…" }, { "src": "/images/project-harbour-house-3.jpg", "alt": "…" }, { "src": "/images/project-harbour-house-4.jpg", "alt": "…" } ], "result": "…", "gallery": [ { "src": "/images/project-harbour-house-gallery-1.jpg", "alt": "…" }, { "src": "/images/project-harbour-house-gallery-2.jpg", "alt": "…" }, { "src": "/images/project-harbour-house-gallery-3.jpg", "alt": "…" } ], "resultImage": { "src": "/images/project-harbour-house-result.jpg", "alt": "…" }}Here’s what each field does:
slugis the URL:/project/harbour-house. Use lower-case letters, digits and hyphens: the demo’selvaré-studioworks, but a plainelvare-studiois easier to type and share.titleis the card’s title, the project page’s title and its browser title.summaryis shown under the title of the project page’s cover, and is the page’s search description (followed by the start of theoverviewwhen it is under 80 characters).categoryis plain text (“Residential”, “Commercial”): the label on the cover and the card’s “category / year” line.imageis the card’s photo and the full-screen cover of the project page.year,location,durationandareaare the facts under the cover, as plain text.serviceslists theslugs of its services, in order: the Services fact links to each service’s page. A slug that matches no service is left out.overviewis the large sentence of the story;briefandscopethe two paragraphs beside it (“The Brief”, “Scope of Work”).imagesis exactly four photos: a tall one (sticky) beside a wide one, then a wide one beside a tall one (sticky).resultis the sentence that sticks beside thegallery(every photo of it is shown, three in the demo), andresultImagethe wide photo that closes the story.
Adding a service
Section titled “Adding a service”{ "slug": "consulting", "name": "Consulting", "summary": "Clear advice on sites, budgets and permits before the first drawing.", "image": { "src": "/images/service-consulting.jpg", "alt": "…" }, "about": "…", "included": { "text": "…", "items": [ { "title": "Site Analysis", "text": "A visit and a report on what the site allows." }, { "title": "Budget Review", "text": "…" }, { "title": "Permit Guidance", "text": "" } ] }}slugis the URL:/service/consulting, and the value projects use in theirserviceslist.nameis the title of the service page, the cards and the switcher, the footer link, and the value the service page’s form starts with in Project type.summaryis the text of the switcher and the cards, the line under the service page’s title, and its search description (followed by the start ofaboutwhen it is under 80 characters).imageis the wide photo of the service page, the card’s photo on Services and the switcher’s photo on Home.aboutis the paragraph under “About service”;includedthe paragraph under “What’s included in the services?” and the deliverables, each atitlewith atext(a deliverable with an emptytextshows its title alone).
The switcher on Home numbers the services 01, 02… in the file’s order. A new service gets its page, its place in the
switcher and on Services, a link in the footer and an entry in sitemap.xml on the next build. If you want it in the
forms’ Project type list too, add it to options of type in src/content/pages/forms.json.
Testimonials
Section titled “Testimonials”Each testimonial in testimonials.json has a slug, a name, a role (“Interior Client”), a photo (src, alt), a
year (“2025”, shown after the role), a rating (a number, shown with one decimal: 4.9) and a quote (the demo writes
it with its quotation marks, “…”). Home and Projects show every testimonial, in columns.
The team
Section titled “The team”Each member in team.json has a slug, a name, a role, a photo (src, alt) and a summary (the text under the
portrait). On desktops About shows one person at a time, picked by pointing at a name; on tablets and phones the members
are cards, team.pageSize (six) at first and the rest as you scroll.
Adding a post
Section titled “Adding a post”{ "slug": "our-new-studio", "title": "Our new studio", "category": "Architecture", "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": "A section title" }, { "type": "paragraph", "text": "More text with **bold** words." } ]}slugis the URL:/blog/our-new-studio.categoryis one ofArchitecture,ConstructionandInterior: on the card, above the post’s title, and the posts “Similar posts” picks from (up to three others of the same category). To add a category, add its name to the list inpostSchemainsrc/content/schemas.ts.date("2026-06-01") orders the posts, newest first, and is shown as “Jun 1, 2026”.excerptis the card’s text, the line under the post’s title and the page’s search description (followed by the start of the first paragraph when it is under 80 characters).imageis the card’s photo and the photo of the post page.contentis the article (rich text).
Legal pages
Section titled “Legal pages”legal.json holds the Privacy Policy and the Terms of Service: a slug (/legal/privacy-policy), a title, the date
of the last update (shown as “May 26, 2026”) and the content (rich text). The demo’s text is a sample
that names Cerette: have your own policy and terms written for your business and country.
Removing an item
Section titled “Removing an item”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. Places that
link an item as text stay as they are: check the buttons and links 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 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 and lists: 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,textis a link (anhttps://link opens in a new tab), and\nstarts a new line. Plus Jakarta Sans is loaded upright only, so an italic word is the browser’s slanted version of the regular text (Making it look like your brand).
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 |
|---|---|---|
A project’s image |
2400 × 1600 | The full-screen cover of the project page; the cards on Home, Projects and Other Work (three shapes: 1.15 : 1, 1.65 : 1 and square) |
A project’s images 1 and 4 |
456 × 684, portrait | Tall (2 : 3), a fifth of the row, sticky while the photo beside them passes |
A project’s images 2 and 3 |
1724 × 1149 | Wide (1.5 : 1) |
A project’s gallery |
1090 px wide | 1.5 : 1, in a column beside the result |
A project’s resultImage |
2280 × 1520 | Wide, 1.5 : 1, the width of the page |
A service’s image |
2280 × 1520 | 1.5 : 1 on the service page, 1.65 : 1 on the Services cards, 1.77 : 1 in Home’s switcher |
A post’s image |
2280 px wide, about 3 : 2 | 1.5 : 1 on the post page, 1.9 : 1 on the cards |
| Team photos | 800 × 1200 | Portrait (0.74 : 1), on the cards and in the desktop picker |
| Testimonial photos | 152 × 152 | Round, 38 px |
The founder’s photo (quote.avatar) |
120 × 120 | Round, 42 px |
The founder’s quote photo (quote.image) |
2400 × 1600 | The full width behind the quote, under a dark veil |
The call to action’s photo (cta.json) |
2400 × 1800 | The full width behind the call to action, under a dark veil |
The video’s poster |
1920 × 1080 | Home’s hero until the video plays |
| Home’s “About us” photo | 1540 × 1027 | 1.5 : 1 (570 × 380 on desktops) |
| The “Why Cerette” photo | 1200 × 1800 | Tall, beside the value cards |
| Home’s three award photos | 840 px wide | Side by side in a row of 3.33 : 1 |
About’s photo (title.image) |
2280 × 1520 | 1.5 : 1, under the title |
About’s award photo (awards.image) |
1540 × 2310 | Portrait, 2 : 3 |
The inquiry photo (inquiry.image in forms.json) |
1090 × 1644 | Beside the form on Services and the service pages, desktops only |
| The 404 photo | 2400 × 1600 | The whole screen, under a dark veil |
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 fine grain texture lies over many photos, as in the original design (public/images/grain.png;
grain on Photo). 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).
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.svg |
The icon in the browser tab: the Cerette mark, black (white in a dark browser 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.
Text that is not in content/
Section titled “Text that is not in content/”Almost every word is content, including the forms’ messages. The few interface words that never change per site live in the code:
- “Main” (the menu’s name for screen readers), “Open menu” and “Close menu” (the phone menu button) in
src/components/site/Header.astro; - the date formats (“Jun 1, 2026” on the cards and posts, “May 26, 2026” on the legal pages) in
src/lib/format.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.