Skip to content
Sign inJoin waitlist

Editing the content — Goeboek Astro

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

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

src/content/
site.json name, title, description, domain, logo, header, contact details, social links, footer
sections.json the call to action, the property cards' labels, the listing filter, the rating label
pages/home.json Home's hero, Featured Properties, About block and blog title
pages/*.json the copy of every other page
collections/*.json properties, agents, locations, categories, posts and testimonials
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 the file that renders it.

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

Field Shown where
site.name The browser title suffix (“Marble House | Goeboek”) and the share cards
site.title Home’s browser title, used whole, and the default of any page without its own
site.description Search results and share cards for Home. 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 (astro.config.mjs reads it as Astro’s site).
site.logo The logo: the round mark’s file, the name’s two lines (“Goeboek” / “properties”) and what screen readers read for the link (Making it look like your brand)
navigation The header’s four links (and the phone menu): Home, Property, Blog and About Us
headerActions The header’s two buttons: “Add Property” (to /add-property) and “Contact us” (to /contact; left out on tablets)
menu The phone menu button’s two labels (“Menu”, “Close”)
contact The office address, the two phone numbers, the e-mail (hello@example.com) and the three lines of opening hours, shown in the footer and on the Contact page
socials The footer’s four social links (Instagram, Facebook, Youtube, Twitter; the demo’s open the networks’ home pages)
footer The footer’s text and “Contact Us” button, its link columns (Categories, Links), the copyright line and “Follow us:”

Phone numbers are written as you want them shown ("(123) 456-7890"); their links dial the digits only. The copyright line’s {year} becomes the current year. Point the social links to your own profiles and remove the ones you don’t use.

The demo’s name appears in many places: “Goeboek” in site, the logo, the footer text, the copyright line (“Copyright © {year} - Goeboek by Marcframe. All rights reserved.”), the testimonials and most page texts. Search src/content/ for “Goeboek” to find them all.

src/content/pages/home.json holds Home’s copy, in the order it appears. Change the text between the quotes, keeping the field names: the sections read them by name. A double quote inside a text is written \"; apostrophes need nothing, and the demo uses both ’ and the typographic ’.

Field Section What it holds
hero The hero title (the page’s <h1>), text, action (“See all Property” → /property), stats (two facts: “150” Property Available, “87” Property Sold), testimonials (the label “Top Testimonial”, count: the first 5 testimonials in a slideshow, and “More Details” → /about#testimonials) and slideshow (count: the first 4 properties as large cards, and their labels: Beds, Bath, m2, “Price :”, Agent, Contact, “Request a tour”)
featured Featured Properties title, offset (4) and count (6): the six properties after the first four, and “More Property” → /property
about About label, title, text, the two images, details (the second text) and “More about Us” → /about
blog The latest posts title and count (the 4 newest posts)

The facts in stats are typed numbers, not counts of the collection: write your own. The hero, Featured and the listings take properties in the order of properties.json, so the first four of the file are the slideshow and the next six are Featured; there is no “featured” switch.

src/content/sections.json holds copy that several pages share:

Field What it holds
cta The call to action on Home and About: label, title, text, the photo and the two buttons (“Get Started” → /property, “Contact Us” → /contact)
propertyCard The cards’ type tags (“For Rent”, “For Sale”) and the size unit (“m2”)
filters The listing pages’ title row (label, title, text), the filter’s heading (“Explore:”), its lead and group labels (Type with All, Sell and Rent; Category; Location; Agents), pageSize (6 cards before “Load More” on /property), “Load More” and the phone toggle’s names for screen readers
testimonial What screen readers read for a score: “Rated {rating} out of 5”

The other page files:

File What it holds
properties.json The titles and descriptions of the listing pages (meta, with {name} for a location or category) and noindex: the three empty default listings kept out of search results
property.json The labels of a property page (type tags, “Property ID:”, Price, Size, “Contact Sales”, Description, “Property features”, the details and utility rows, Video, Location and “Show on map”, the agent’s contact labels and “View My Property”), the tour form (tour, Forms), “More in {location}” with count (2) and “Related properties” with count (3) and “More Property”
agent.json An agent page’s browser title and description ({name}), its title and text, the contact labels and “Explore: {name}”
blog.json The blog’s browser title, description and title
post.json “By {author}”, the sidebar’s about text, “Recent posts” (count 3), “Latest Property” (count 1) and the related posts’ title (count 4)
about.json The page title and photo, “Our Journey to Excellence” with its three paragraphs, the three values with two photos, and the testimonials block (id testimonials, 6 cards before “Load More”, 4 below 1200 px)
contact.json The page title, the map’s search (map.query), the labels of the contact details and the contact form
add-property.json The page title and every group and field of the Add property form (Forms)
success.json The two thank-you pages (tour, property): title, subtitle, text, illustration and button
not-found.json The 404 page: its browser title, the title, “404”, the two lines and “Return to Homepage”

Every page file but Home’s has a meta with its browser title and its description.

src/content/collections/ holds the lists the site builds pages and sections from, one JSON array each:

File Items What it feeds
properties.json 21 Home’s slideshow (the first 4) and Featured (the next 6), every listing, one page per property at /property/<slug>, the post pages’ “Latest Property” (the first one)
agents.json 4 One page per agent at /agent/<slug>, the agent on every property card and page, the filter
locations.json 6 One listing per location at /location/<slug>, the cards’ meta line, the filter
categories.json 5 One listing per category at /property-category/<slug>, the cards’ meta line, the filter
posts.json 12 Home’s latest posts, the blog, one page per post at /blog/<slug>
testimonials.json 12 Home’s hero (the first 5) and About (all, 6 at a time)

Every collection keeps the order of its file, except posts, which are sorted by date, newest first. Two posts of the same date keep the order of the file.

The last agent, location and category of each file are Framer’s defaults: “No Name” (no-name, no photo and no details), “No Location” (no-location) and “Uncategory” (uncategory). No property uses them; they have pages that list nothing, which are kept out of search results and the sitemap (noindex in properties.json) and out of the filter. They are also the fallbacks: a property whose agent, location or category names no item shows “No Name”, “No Location” or “Uncategory” instead, so keep them unless every property names an existing item.

Copy an existing entry, paste it into the list (mind the comma between entries), and change the values:

{
"slug": "garden-loft",
"title": "Garden Loft",
"propertyId": "55G101",
"for": "rent",
"category": "apartments",
"agent": "steve-parker",
"location": "queens",
"address": "12-34 Main St, Queens, NY 11354, USA",
"price": 2400,
"duration": "/month",
"image": { "src": "/images/property-garden-loft.jpg", "alt": "A bright loft with a sofa facing tall windows" },
"gallery": [
{ "src": "/images/property-garden-loft-2.jpg", "alt": "…" },
{ "src": "/images/property-garden-loft-3.jpg", "alt": "…" },
{ "src": "/images/property-garden-loft-4.jpg", "alt": "…" },
{ "src": "/images/property-garden-loft-5.jpg", "alt": "…" }
],
"excerpt": "A bright two-bedroom loft above a quiet garden in Queens.",
"description": [{ "type": "paragraph", "text": "**Garden Loft** is …" }],
"features": [{ "type": "paragraph", "text": "Welcome to **Garden Loft**, …" }],
"video": "https://www.youtube.com/watch?v=…",
"details": {
"size": 90, "bedrooms": 2, "bathrooms": 1, "floor": "Second", "additionalSpace": "Balcony",
"furnishing": "Semi furnished", "ceilingHeight": 3, "constructionYear": "2007-07-01", "renovation": "2019-03-01"
},
"utility": {
"heating": "Natural gas", "airCondition": "Yes", "fireplace": "-", "elevator": "Yes", "ventilation": "Yes",
"intercom": "Yes", "windowType": "Aluminum frame", "cableTv": "-", "wifi": "Yes"
}
}
  • slug is the URL: /property/garden-loft. title is the card’s title, the page’s <h1> and its browser title.
  • propertyId is shown on the page and filled into the tour form, so a request names the property.
  • for is "rent" or "sell": the type tag (“For Rent”, “For Sale”) and the Type listings.
  • category, agent and location are the slugs of items in categories.json, agents.json and locations.json.
  • address is shown under Location; “Show on map” opens Google Maps on it.
  • price is a number in dollars, shown as “$2,400”; duration follows it (“/month” for rent, "" for sale).
  • image is the card’s photo, the page’s main photo and the picture shown when the property is shared. gallery holds more photos: the page shows the first four in a 2 × 2 grid, and a hovered card steps through the main photo and the first two.
  • excerpt is the card’s text and the page’s search description (cut at 160 characters).
  • description and features are rich text.
  • video is a YouTube link, shown as an embedded player; leave the field out to hide the Video block. The demo’s 21 properties share one video: give each its own.
  • details: size in square metres, ceilingHeight in metres, constructionYear and renovation as ISO dates (shown as “Jul 1, 2007”); the rest is text. utility: “Yes”, “-” or a word (“Natural gas”).

The page ends its sidebar with “More in ” (the first two other properties of the same location, in the order of the file) and the page with “Related properties” (the other properties of the same category and type: three from 1200 px, four below).

{
"slug": "maya-lee",
"name": "Maya Lee",
"image": { "src": "/images/agent-maya-lee.jpg", "alt": "Maya Lee smiling in a navy blazer" },
"address": "560 3rd Ave, New York, NY 10016, USA",
"phone": "+2224445557",
"mobile": "+3336669991",
"whatsapp": "3336669991",
"email": "maya@example.com",
"bio": "Maya helps families find their first home in Queens and Brooklyn."
}

The agent page is /agent/maya-lee: the agent’s card (photo, address, office phone, mobile, WhatsApp, e-mail and bio) above the filter, and every property whose agent is maya-lee. Phones are written as they are dialled; WhatsApp without the + (its link is https://wa.me/<number>). “Contact Sales” on a property page calls the agent’s mobile. An agent with a photo shares it, as a large card, when the page is shared.

{ "slug": "jersey-city", "name": "Jersey City" }

Each gets a listing page (/location/jersey-city, /property-category/<slug>), a link in the filter and its name on the cards of its properties. The Add property form’s Location and Property Category choices are typed in add-property.json, not read from the collections: add the name there too.

{
"slug": "choosing-your-first-home",
"title": "Choosing Your First Home",
"category": "Improvement",
"date": "2026-11-02",
"author": "Javier Marc",
"image": { "src": "/images/post-choosing-your-first-home.jpg", "alt": "Keys on a kitchen table beside a floor plan" },
"excerpt": "Five questions to ask before you sign for your first home.",
"body": [
{ "type": "paragraph", "text": "First paragraph, with a **bold** phrase." },
{ "type": "paragraph", "text": "Another paragraph." }
]
}
  • slug is the URL: /blog/choosing-your-first-home; title the card’s title, the page’s <h1> and its browser title.
  • category is plain text, not a reference (the demo’s are Improvement, Development and Design). The post’s related posts are up to four other posts with exactly the same category, newest first (three on laptops and phones). There are no category pages for posts.
  • date ("2026-11-02") is shown as “Nov 2, 2026”, and sorts the lists. author shows as “By Javier Marc”.
  • image is the card’s photo, the cover of the post and the picture shown when it is shared.
  • excerpt is the card’s text and the post’s search description (cut at 160 characters); body is the article.

A post page’s sidebar shows the about text, “Recent posts” (the three newest, the open one included) and “Latest Property” (the first property of properties.json).

{
"slug": "jane-d",
"name": "Jane D.",
"photo": { "src": "/images/testimonial-jane-d.jpg", "alt": "Portrait of Jane D." },
"rating": 4.7,
"quote": "\"They found us a home in two weeks.\""
}

rating is a score out of 5, shown with a star, or null to show none. The first five testimonials of the file are Home’s slideshow; About shows them all, six at a time (four below 1200 px). The demo’s quotes keep Framer’s straight quotation marks inside the text.

Delete the entry (and the comma before it, if it was the last). Its own page and its sitemap entry disappear on the next build. Before deleting an agent, a location or a category, move its properties to another one: their cards would otherwise show the default (“No Name”, “No Location”, “Uncategory”).

src/content/schemas.ts is the reference: it lists every field, which are required, and what kind of value each takes. npm run check and npm run build check every entry against it and name the collection, the item and the field that is wrong.

A property’s description and features and a post’s body are lists of blocks. The demo uses paragraphs only, with bold words:

[
{ "type": "paragraph", "text": "**South Sunlight Apartment** is a radiant urban residence …" },
{ "type": "paragraph", "text": "Another paragraph." }
]
  • Paragraphs are plain text; words between double asterisks are bold (**…**), words between backticks are code.
  • Headings ({ "type": "heading", "level": 3, "text": "…" }, levels 2 to 6) and lists ({ "type": "list", "ordered": false, "items": ["…", "…"] }, numbered with "ordered": true) are drawn too, though the demo has none. A list item is a line of text; or an object with its text and a nested list (ordered and items); or an object with its text followed by more blocks (blocks).

There are no italics, links or images inside the text.

  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 when the site builds, so each device gets a size that fits. A content path that points to a missing file stops the build with its name. The download’s placeholders show the size of each demo photo; use photos at least as large as the frames:

Photos Demo size Frame
A property’s image 300 to 1400 wide (most 1024 × 644 or 1400 × 785) 1.536 : 1 on the cards; about 16 : 9 on its page (up to 940 px wide); 500 to 680 px tall in Home’s slideshow
A property’s gallery 300 to 1200 wide 16 : 9 tiles in the page’s 2 × 2 grid; the card’s frame when hovered
An agent’s image 400 × 504 round, 82 px on the agent card, 50 px on the cards
A post’s image 1400 wide (933 to 2100 tall) 0.84 : 1 (taller than wide) on the cards; 1.46 : 1 on its page
A testimonial’s photo 70 to 200 px 24 px round
About’s photos (about-hero, about-1, about-2) 1920 × 1280, 1200 × 800, 1200 × 1800 2.2 : 1 (1.4 : 1 on phones); 1.53 : 1; the height of the column
The call to action’s photo (cta) 1920 × 1282 the full block, under a dark veil

Photos in a fixed frame are cropped to fill it, so a photo of other proportions works, but you lose the edges the frame cuts. The logo’s mark (logo-mark.svg) and the two illustrations of the thank-you pages (success-tour.svg, success-property.svg) are drawings, not photos, and ship as they are.

Every photo comes with a short description for screen readers and search engines: alt in { "src", "alt" }. Write one for each photo you change.

Almost every word is content, including the forms’ messages and the screen-reader names of the filter toggle and the scores. The few interface words that never change per site live in the code:

  • “Previous”, “Next” and “Go to slide {n}” (the slideshow buttons, for screen readers) in src/design-system/components/media/Slideshow.astro;
  • the date and price formats (“May 16, 2024”, “$1,200”) in src/lib/format.ts;
  • the page’s language, lang="en", and og:locale in src/layouts/Layout.astro.

Search for the word and you will find it.

Terminal window
npm run check
npm run build

check reads every content file against its schema; a successful build means every page still renders and every image exists. Neither checks that a property’s agent, location or category names an existing item (it falls back to the default), or that links written as text ("/about#testimonials") lead somewhere: click through the site once with npm run preview after big changes. See Going live for the rest of the checklist.