Skip to content
New: Customize your theme with an AI assistant. Read the guide

Collections

Skill level: Beginner · Files: src/content/<collection>/<language>/, defined in src/content.config.ts

A collection is a folder of similar entries: causes, events, supporter quotes, job openings, team members, stories. Most entries are one file and one page. The list page of the collection (for example /causes/) takes its title and section blocks from the -index.md file in the same folder. Files whose name starts with _ are ignored.

Add An Entry

  1. Copy an existing entry in the folder, for example src/content/causes/english/community-kitchen.md.
  2. Rename the copy. The file name is the entry’s id and its URL (/causes/food-bank/) unless you set customSlug. Other files refer to entries by this id, for example cause: "community-kitchen" in a supporter quote or a story.
  3. Change the frontmatter values and the Markdown body. Keep the keys.
  4. Add the same file in each other language folder with the translated text, the same file name, and the same numbers.
  5. For a cause, add its link to the Causes menu too: see Menus.

To hide an entry, set draft: true. It still shows in npm run dev, but it is left out of the built site, the lists, and the sitemap. npm run astro-check reports a missing required field or a value of the wrong type in every collection that has a schema.

A new entry with only a title builds. Its card or page shows what you filled in, and images and other fields stay empty until you add them, so fill them in before you publish.

Every Collection

CollectionFolderPagesSchemaUsed by
causescauses//causes/, /causes/<id>/yesCauses sections, the cause picker of the donation form, the Causes mega menu card, the appeal hero, the donate call to action, the category labels of the impact results
donatedonate//donate/yesEvery amount on the site: the donation form, the quick donate teaser, the hero widget, the giving tiers, the impact receipt
eventsevents//events/, /events/<id>/, /events/<id>.icsyesEvents sections, the community hero, structured data
impactimpact//impact/yesThe impact page, and the spending split on /donate/
gallerygallery//gallery/yesThe gallery page and the photo strip on /home-community/
reviewsreviews/none (shown on /testimonials/ and in sections)yesSupporter voices in every layout, the case study on /partners/
careerscareers//careers/, /careers/<id>/yesOpen roles section, job posting data
teamteam//team/ onlyyes (strict)Team section on /team/ and /about/
blogblog//blog/, /blog/<id>/, category and tag pagesyesStories list, latest stories section, RSS feed
authorauthor/noneyesAuthor box under stories
homepagehomepage//, /home-appeal/, /home-community/yes (page)The homepages’ named blocks
pagespages//<id>/ (text pages) and the pages with their own routeyes (page)Legal pages, volunteer, fundraise, tribute, partners, supporter voices, thank-you page, elements
about-usabout-us//about/yes (page)About page blocks
faqfaq//faq/yes (page)The full grouped FAQ list (in its questionsSection block)
contactcontact//contact/no schemaContact page blocks
sectionssections/noneno schemaDefault content of every section

yes (page) means the collection uses the shared page schema: the fields every page accepts plus every named block. astro-check checks those blocks too.

The fields every page accepts (title, description, image, draft, customSlug, SEO fields) work on the entries of every collection except reviews and author, which have their own short schemas. They are listed in Pages. The tables below list what each collection adds. Required fields must be present; all others are optional.

Causes

One file per cause in src/content/causes/english/, plus -index.md for /causes/ with the categories list. Full guide: Causes & Campaigns.

FieldTypeWhat it does
title (required)textCause name on cards, in the menu card, and the H1
description, image, imageAlt, imageCaptionSummary, photo, its alt text, and the caption line under the page photo
categorycategory idIts filter group on /causes/ (an id from categories in -index.md)
goal, raisednumberThe goal and the amount raised so far, in the donate currency
donorswhole numberThe donor count (“640 donors”)
deadlinedateLast day of the appeal. Empty means ongoing
locationtextWhere the work happens
featured, ordertrue/false, numberShown on the homepage and at the top of /causes/; order in lists (lowest first)
gallerylist of image, altPhotos from the field on the cause page
impactlist of amount, label, icon“What a gift does” lines on the cause page
updateslist of date, title, textDated news on the cause page

Only in -index.md: categories (id, label, icon, order; the shipped ids are education, health, water, food, shelter). The progress bar, days left, and the “Ended” state are worked out from goal, raised, and deadline when the site is built. Keep every number identical in every language.

One file, src/content/donate/english/-index.md: the donate page and the giving data the whole site uses. Fields: currency (a three-letter code such as USD), amounts (oneTime, monthly), default, minimum, frequencies, coverFeesPercent, impactMap, tiers, form, jumpNav, spendSplit, otherWays, and the page blocks. Keep every number identical in the file of every language: npm run build prints a [donate] warning when they differ. Full guides: Donation Form and Giving Tiers & Receipt.

Events

One file per event, plus -index.md for /events/ with the categories list (fundraiser, volunteer, online in the sample). Full guide: Events & Calendar.

FieldTypeWhat it does
title (required)textEvent name
categorycategory idIts filter group on /events/
start, enddate and timeWall-clock times where the event happens, as 2026-11-15T09:00:00
timezonetextTime zone of those times, such as "Europe/Paris". Empty uses timezone in [organization]
venue, addresstextWhere it happens. The address is also written to the calendar file
onlinetrue/falseAn online event, with no venue
capacitywhole numberPlaces available
pricenumberTicket price. 0 or empty means free
registerUrlURLWhere the Register button goes. Empty goes to /contact/?topic=events
featuredtrue/falseMarks a highlight event; an events section with featuredOnly: true shows only these
imageAlt, imageCaptiontextPhoto alt text and caption line

Past events leave the upcoming lists on their own when the site is rebuilt.

Impact

One file, src/content/impact/english/-index.md, for /impact/. Blocks: figures (headline numbers with a source line), spend (the spending split, read by /donate/ too), results (what each cause category delivered), reports (annual reports with a file each), facts (registration and governance facts; {registration} is the number from [organization]), and policies. Every figure in the sample is a sample. Full guide: Impact & Transparency.

One file, src/content/gallery/english/-index.md, for /gallery/. Fields: categories (id, label), items (image, alt, category, place, caption, credit), credit (the photographer shown for every photo unless an item has its own), filterLabel, and allLabel. Every item’s category must be an id from categories. Full guide: Partners & Gallery.

Supporter Voices (Reviews)

One file per quote, with its own schema (not the page schema). Every field is optional, so an empty file never fails the build, but a quote only shows once name, role, and text are filled in.

FieldTypeWhat it does
nametextFirst name and last initial, such as "Daniel R."
roledonor | volunteer | partner | beneficiaryShown with the name, and used by the role filter of the wall layout
texttext, up to 700 charactersThe quote
causecause idLinks the quote to a cause, so a section can show only the voices about it
datedateNewest first
featuredtrue/falseFeatured band on /testimonials/, first pick in other layouts
imageimage pathOptional portrait. Without it, only the name shows
drafttrue/falseHides the quote

Givo never adds review stars to structured data. The sample quotes are invented: replace them with real ones, with the person’s consent.

Careers

One file per open role, plus -index.md for /careers/ with the departments list (programs, fundraising, volunteering in the sample) and the hiring notes.

FieldTypeWhat it does
codetextJob reference shown on the page
departmentdepartment idTeam column on /careers/
locationtext“Riverside office”, “Remote”
typefull-time | part-time | contract | internship | seasonalLabels from careers.types in src/i18n/<language>.json
paymin, max, unit (hour or year)Pay range, in the donate currency
schedule, start, interviewstextFacts on the role page
date, validThroughdatePosting date and last day to apply
applyUrlURLYour applicant system or a mailto: link. Empty sends an email to email in [organization]
weightnumberOrder on /careers/

Dates, pay, and type feed the JobPosting data search engines read. Keep only real, open roles: replace or delete the samples before launch.

Team

One file per person, plus -index.md for /team/. Fields: title (the name, first name and last initial), profession (role), group (staff, board, or ambassadors), since (year joined), languages, bio (a short Markdown bio behind the “Read bio” toggle), social (network: linkedin, instagram, twitter, or facebook, and url), image (optional 4:5 portrait), imageAlt, and weight (order inside the group). Members have no page of their own. The schema is strict: a misspelled field fails astro-check.

Stories And Authors

  • Stories are .mdx files in src/content/blog/english/: title, description, image, imageAlt, imageCaption, location, date, updated, author, categories, tags, cause (a cause id, linked at the end of the story), featured (the lead story on /blog/), and draft.
  • Authors live in src/content/author/english/, one file per author: title (required, the name), role, image, description, links. A story’s author: "Peter Ansah" matches peter-ansah.md.
  • Stories per page: blogPagination in [settings] of config.toml.

See Stories and Writing Content for the shortcodes you can use in stories.

Do It With AI

Add a [cause | event | supporter quote | job opening | team member | story] to
src/content/[folder]/english/ for: [DETAILS]. Copy the frontmatter keys of an existing entry in
that folder, keep its comments, and fill in my values only. Check the field types in
src/content.config.ts, and use ids that already exist for category, cause, and department. Then
create the other language versions in src/content/[folder]/ with the same file name and the same
numbers, and run npm run astro-check.
Type something to search...