Skip to content
Sign inJoin waitlist

Editing the content — Semono 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, contact details and the footer
pages/home.json the copy of the home page
pages/about.json …and of every other page
collections/*.json services, testimonials, posts, careers, legal pages, the team, client logos
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 logo’s name for screen readers, the browser title suffix (“Contact Us | Semono”), share cards
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): Home, About, Services, Blog
contactLink The “Contact us” button of the header (and the phone menu)
contact E-mail, phone and address, with the labels the footer shows: the footer’s Contact column and the Contact page (which has its own labels for them, contactPage.info in contact.json)
footer The footer: the line about the firm (about), the note (note, where {year} becomes the current year), the titles of its four columns (quickLinksLabel, servicesLabel, socialLabel, contactLabel), the Quick Links (quickLinks), the social links (socials), the three taglines (taglines) and the legal links (legalLinks)

The footer’s Services column lists every service of the collection, so it follows services.json. The Team, Careers and Testimonial pages are not in the menu: Pages and sections says where each one is linked.

The demo’s e-mail (hello@example.com), phone number, address and business hours are placeholders: replace all of them (the hours are contactPage.info.hours in src/content/pages/contact.json). The phone’s link is built from the number (+1 (800) 458 9214 calls tel:+18004589214), so write it the way people should read it. The social links in footer.socials open the networks’ home pages, and so do the LinkedIn links of the team: point them to your own profiles.

Links that start with https:// (the booking link, the LinkedIn links) open in a new tab, except the footer’s social links, which open in the same one; mailto: and tel: links open the visitor’s mail app or phone.

The firm’s name appears in many places: site.name, the footer, the copy of every page, the quotes of the testimonials, the posts, the careers and the legal texts. The logo draws it too (Making it look like your brand). Search src/content/ for “Semono” to find them all.

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

{
"meta": {
"title": "About Semono: Our Story, Mission and Team",
"description": "Semono helps businesses improve…"
},
"label": "About Semono",
"title": "Building smarter businesses through strategic consulting"
}

title becomes the browser tab (“About Semono: Our Story, Mission and Team | Semono”), 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: the hero, the title of the client logos, “About Semono” (its text, three photos, four cards and the four figures), “Our Services” (the heading, services.limit, the closing line and its two buttons, the video), “Why Choose Semono” (its six reasons), the photo band, the process (four steps, three tabs and the booking link), the headings of the testimonials, the closing call to action and “Latest Insights”. Its meta is empty: its title and description are site.title and site.description.
about.json About: the title, the photo, “Our Story” and its four figures, “Our Mission & Values” (its four cards, the video and the closing line) and “Our Team”
team.json Team: the title, the start of the LinkedIn links’ names for screen readers, the group photo and the “Join the Semono team” card
careers.json Careers (/career): the title, the three photos, the four cards (perks) and the heading of “Open Positions”
career.json The words shared by every career page (careerPage: “Location :”, “Type :”, the headings, “Apply for this position”) and the application form (careerForm)
services.json Services (/service): the title, the text screen readers hear while more rows load, “What’s Included:” and “Learn more” on the rows, “How We Work” (four steps, the black card and the title of the client logos) and the heading of the client cards
service.json The words shared by every service page (servicePage: “Overview”, the consultation card, “Other services”) and the consultation form (consultationForm)
testimonials.json Testimonial: the title, the text screen readers hear while more stories load, the closing call to action and the heading of “Latest Insights”
blog.json Blog: label, title, text and the text screen readers hear while more posts load
post.json The heading “Related articles” under every post
contact.json Contact: the page (contactPage: its meta, the title, the labels of the contact details, the business hours and the FAQ) and the inquiry form (contactForm) (Forms)
legal.json “Last updated on” on the legal pages
not-found.json The 404 page: its browser title (meta.title), the title, the text, the button and the photo

A few blocks appear on more than one page, and each page’s file holds its own copy of them: the four figures, the four icon cards, the process steps, the closing call to action, “Latest Insights” and the headings over the client logos and the client cards. Change them in every file that has them (Pages and sections lists where).

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

File What it feeds
services.json The Services page (every service, numbered 01, 02, … in the file’s order), one page per service, Home (the first four: services.limit in home.json), “Other services” at the end of a service page (the first four others) and the footer’s Services column
testimonials.json The Testimonial page (every story), the cards of Home and Services (the first eight), the client story in “Why Choose” on Home (the first), the quote beside the closing line of “Our Services” on Home (the fourth) and the one in “Our Mission & Values” on About (the third)
posts.json The Blog, one page per post, “Latest Insights” on Home and on the Testimonial page (the first three) and “Related articles” at the end of a post (up to three other posts of its category)
careers.json Careers (every position) and one page per position
legal.json One page per legal text: /legal/privacy-policy and /legal/terms-of-service
team.json The Team page (every member) and About (the first three: team.limit in about.json)
clients.json The logo ticker on Home and at the end of “How We Work” on the Services page (every logo)

The order of the items in the file is the order on the site. The Blog doesn’t sort posts by date either: the demo lists them newest first, so put a new post first to show it first. The Services and Testimonial pages show four items at first and the Blog four (six on desktop), then more each time the visitor scrolls close to the spinner under the list; every item is in the page’s HTML from the start, so search engines find them all.

The testimonials are not only a page. The same list is read in four places, and their position in testimonials.json decides which story goes where:

  • 1st: the client story in “Why Choose” on Home (two results, the company logo, the line about the project and its services);
  • 3rd: the quote beside the closing line of “Our Mission & Values” on About;
  • 4th: the quote beside the closing line of “Our Services” on Home;
  • every one, up to eight: a card in the grid of Home and of the Services page. The look of a card follows its position: 1 the client with the company logo over the quote; 2 the client, the quote and two results; 3 and 4 the quote over the client; 5 like 2; 6 two results over the quote and the client; 7 like 1; an eighth starts again at 1.

Move a testimonial in the file and it moves to the other place. These positions are quote in home.json (services.details) and about.json (mission.details) and story.item in home.json (why), counted from 0. Keep at least one testimonial: with none, Home and About can’t be built; with fewer than four, the place that asks for a later one takes the last.

Copy an existing entry, paste it after the last one (mind the comma between entries), and change the values:

{
"slug": "risk-advisory",
"name": "Risk Advisory",
"summary": "Identify, measure and manage…",
"image": "/images/service-risk-advisory.jpg",
"highlight": "Managing risk before it manages you",
"overview": ["First paragraph.", "Second paragraph."],
"included": ["Risk Assessment", "Scenario Planning"],
"gallery": ["/images/service-risk-advisory-1.jpg", "/images/service-risk-advisory-2.jpg", "/images/service-risk-advisory-3.jpg"],
"deliver": [{ "title": "Risk Mapping", "description": "…" }],
"impact": [{ "value": "42%", "label": "Growth Increase" }]
}

Here’s what each field does:

  • slug is the URL: /service/risk-advisory.
  • name is the title, the numbered row and the footer’s link.
  • summary is shown under the title and on the rows, and is the page’s search description.
  • image is the wide photo under the title, the row’s photo and the page’s share image.
  • highlight is the headline of the overview, overview its paragraphs (one string per paragraph, plain text).
  • included is “What’s Included”, on the rows and beside the overview.
  • gallery holds three photos, deliver the four “What We Deliver” cards and impact four numbers (a label may be empty).

A service page shows its name and summary over a wide photo, the overview beside “What’s Included”, the gallery beside the four cards, the four numbers, the consultation form and four other services. The numbers are plain text: they don’t count up. Three demo services have no label under their fourth number, as in the original design.

Two lists elsewhere name the services and don’t follow the collection: the “Service Required” choices of the Contact form (contactForm.fields.service.options in contact.json, which also holds two choices that are not services, “Process Optimization” and “Organizational Growth”) and the services tags of each testimonial. Update them when you add, remove or rename a service.

Adding a post, career, testimonial, team member, client or legal page

Section titled “Adding a post, career, testimonial, team member, client or legal page”
Add Fields
Post slug, title, excerpt (under the title, the card text and the search description), image (the card’s photo and the wide cover, both cropped), category (any words: posts with the same one are listed under each other as “Related articles”; the demo uses Operational, Leadership and Business), date ("2026-05-20", shown as “May 20, 2026”), body (rich text, below)
Career slug, title, summary (the row on Careers and the search description), location and type (two chips: "New York, United States", "Full Time"), overview (a paragraph), responsibilities, qualifications and offers (three bulleted lists; six items each in the demo)
Testimonial slug (an id), company, logo (an SVG: usually the client’s logo file), quote, name, role ("CEO"; shown as “CEO — Noventra Labs” where there is no logo), photo (round, 42 px), summary (the line about the project), services (names shown as tags) and results (four: a value such as "+38%" and a label)
Team member slug (an id), name, role, photo (a 2:3 portrait), linkedin (the profile address)
Client name (also the logo’s text for screen readers) and logo: an SVG file in src/assets/images/ with a width and height or a viewBox, shown 24 px tall at its own proportions
Legal page slug, title, updated ("2026-05-20", shown as “Last updated on May 20, 2026”) and body (rich text). The footer links the two demo pages from footer.legalLinks in site.json: add a link there for a new page.

Dates are shown with a short month: "2026-04-28" reads “Apr 28, 2026”. A new service, post, career or legal page gets its own page, and its entry in sitemap.xml, on the next build. Testimonials, team members and clients have no pages.

Most lists take any number of items. A few blocks are laid out for a fixed number, so keep it:

Where How many
Home, “About Semono” three photos, four cards and the four figures (facts; About has the same four in about.json)
Home, the process four steps
Careers three photos and four cards (perks)
A service three photos in gallery, four cards in deliver and four numbers in impact
A testimonial four results
Home, “Why Choose” two photos for each reason

Delete the entry (and the comma before it, if it was the last one). Its page and its sitemap entry disappear on the next build. Places that name the item as text stay as they are: the footer’s legal links, the Contact form’s service choices, a testimonial’s tags.

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. One comment there is out of date: the figures (Fact) are plain text and never count up.

A post body and a legal text are a list of blocks:

"body": [
{ "type": "heading", "text": "Identifying Workflow Inefficiencies" },
{ "type": "paragraph", "text": "A plain paragraph with an *italic* word." },
{ "type": "paragraph", "text": "The mistake:\nOvercomplicated menus leave users frustrated." },
{ "type": "list", "items": [
[{ "type": "paragraph", "text": "First item" }],
[{ "type": "paragraph", "text": "Second item" }]
] }
]

Headings have one size (larger on a post than on a legal page). Text is plain apart from two marks: words between asterisks are set in italics, and \n starts a new line inside a paragraph. There is no bold and there are no links inside the text. Each list item is itself a list of blocks, so an item can hold a nested list; add "ordered": true to a list for numbers instead of bullets. The demo’s posts use headings, paragraphs and bulleted lists; the legal pages use headings and paragraphs, and one list. Inter is loaded upright only, so an italic word is the browser’s slanted version of the regular text (Making it look like your brand).

Two videos play on the site: on Home, under the closing line of “Our Services”, and on About, in “Our Mission & Values”. Each is a card that shows a poster picture under a light veil with a play button. One press plays the clip in place, muted and in a loop, and the next press pauses it. The clip is only fetched at the first press, so the page stays light.

Video Where it plays Field
Home Under the closing line of “Our Services” services.video in src/content/pages/home.json
About In “Our Mission & Values” mission.video in src/content/pages/about.json
"video": {
"src": "/videos/intro.mp4",
"poster": { "src": "/images/home-video-poster.jpg", "alt": "…" },
"label": "Play video",
"caption": "Watch our activity"
}

src is a file in public/videos/ or a web address; poster is the picture shown before it plays (16:9); label is the play button’s name for screen readers; caption is shown beside the button while the pointer is over the card.

The demo’s src addresses point at stock clips on Pexels’ servers (videos.pexels.com), by Pavel Danilyuk: 8716590 on Home and 7691549 on About. The Pexels License lets you use them for free, including on a commercial site, and credit is optional; what it doesn’t allow is reselling or redistributing the clips themselves. So the template doesn’t ship them: the demo plays them from Pexels. Replace both before you launch: the clips show strangers, not your firm, and they stay on someone else’s server, which may move or remove them.

To use your own:

  1. Export a 16:9 clip of about 1280 × 720 and keep it to a few MB, because it loops. Put the MP4 in public/videos/ (create the folder) and set "src": "/videos/intro.mp4". A larger file belongs on a video host or a CDN: put its address in src.
  2. Replace the poster: home-video-poster.jpg and about-video-poster.jpg in src/assets/images/ are 1280 × 720 images (the placeholders show the size).
  3. Write the alt of the poster and, if you like, the label and the caption.

To remove a video, delete the <Reveal> that holds its <VideoCard {...video} />: in src/components/sections/HomeServicesSection.astro (Home) or src/components/sections/AboutMissionSection.astro (About).

  1. Put the file in src/assets/images/.
  2. Refer to it in the content as /images/<file>.

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

Photos Demo size
The Home hero photo, the photo band (Home) 2400 px wide, landscape (full screen width, cropped)
The 404 photo 2400 × 3600, portrait (it fills the window, cropped)
The wide photo of About, the photo of the process (Home) 1800 × 1200
A service’s image (the wide photo, the row’s photo, the share image) 1800 × 1013 (shown 1140 × 600 on desktop; the row’s photo is cropped to 274 × 238)
A service’s gallery (three photos) 600 px wide: 600 × 900 for the tall one, shorter for the others
A post’s image (the card’s photo and the wide cover) 1800 px wide, landscape (the card is 3 : 2; the cover is cropped to about 1.9 : 1, 300 to 600 px tall)
“About Semono” photos (Home) 700 px wide: one tall (700 × 1050) and two shorter
The three tabs of the process (Home) 700 × 1050
Photos of “Why Choose” (two per reason) 320 × 213 (shown square, 130 to 150 px)
The closing call to action photo (Home, Services, Testimonial) 1000 × 667
The photo of the consultation card (service pages) 1000 × 1500
The three photos of Careers 700 px wide: 700 × 1050 for the tall one, shorter for the others
The group photo of the Team page 1200 × 800
Team portraits 800 × 1200 (2 : 3, cropped from the top)
Portraits of the testimonials 160 × 160 (shown round, 42 px)
The posters of the two videos 1280 × 720

Client logos are SVG files shown 24 px tall (20 on phones) in the ticker and about 15 px tall on the cards: draw them with a width and height or a viewBox. src/lib/image-size.ts reads each logo’s size when the site builds, so the ticker and the cards keep its proportions. The same files serve as the clients’ logos and as the testimonials’ company logos: replace a file and both change.

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

Photos in the page copy written as { "src": …, "alt": … } have 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). Photos that come from the collections (services, posts, the team, the testimonials) are decorative in this template: the name or title next to them says what they show. Client and company logos take their company’s name as their description.

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

File What it is
public/icon.svg, public/apple-icon.png The icon in the browser tab (a black square with the monogram, white in a dark browser theme) and 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, except the service and post pages, which share their own photo.

Almost every word is content, including the forms’ messages (contactForm, consultationForm and careerForm). 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 label) in src/components/site/Header.astro;
  • the “ — “ between a client’s role and company (“CEO — Noventra Labs”) in src/lib/to-ui.ts;
  • the date format of posts and legal pages (“May 20, 2026”) in src/lib/format.ts;
  • the page’s language, lang="en", in src/layouts/Layout.astro.

Search for the word and you will find it.

Terminal window
npm run check
npm run build

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