# Collections (Causes, Events, Voices & More)

## 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
<Steps>

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](/givo/customization/menus/).

</Steps>

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
| Collection | Folder | Pages | Schema | Used by |
| --- | --- | --- | --- | --- |
| `causes` | `causes/` | `/causes/`, `/causes/<id>/` | yes | Causes 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 |
| `donate` | `donate/` | `/donate/` | yes | Every amount on the site: the donation form, the quick donate teaser, the hero widget, the giving tiers, the impact receipt |
| `events` | `events/` | `/events/`, `/events/<id>/`, `/events/<id>.ics` | yes | Events sections, the community hero, structured data |
| `impact` | `impact/` | `/impact/` | yes | The impact page, and the spending split on `/donate/` |
| `gallery` | `gallery/` | `/gallery/` | yes | The gallery page and the photo strip on `/home-community/` |
| `reviews` | `reviews/` | none (shown on `/testimonials/` and in sections) | yes | Supporter voices in every layout, the case study on `/partners/` |
| `careers` | `careers/` | `/careers/`, `/careers/<id>/` | yes | Open roles section, job posting data |
| `team` | `team/` | `/team/` only | yes (strict) | Team section on `/team/` and `/about/` |
| `blog` | `blog/` | `/blog/`, `/blog/<id>/`, category and tag pages | yes | Stories list, latest stories section, RSS feed |
| `author` | `author/` | none | yes | Author box under stories |
| `homepage` | `homepage/` | `/`, `/home-appeal/`, `/home-community/` | yes (`page`) | The homepages' named blocks |
| `pages` | `pages/` | `/<id>/` (text pages) and the pages with their own route | yes (`page`) | Legal pages, volunteer, fundraise, tribute, partners, supporter voices, thank-you page, elements |
| `about-us` | `about-us/` | `/about/` | yes (`page`) | About page blocks |
| `faq` | `faq/` | `/faq/` | yes (`page`) | The full grouped FAQ list (in its `questionsSection` block) |
| `contact` | `contact/` | `/contact/` | **no schema** | Contact page blocks |
| `sections` | `sections/` | none | **no schema** | Default 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.

<Aside type="caution" title="No schema: check by eye">
  The `sections` and `contact` collections have no schema, so `npm run
  astro-check` doesn't catch a wrong option value there, such as a misspelled
  `layout`. Check each value against the comment next to it, then open the page
  in the browser.
</Aside>

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](/givo/customization/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](/givo/customization/causes-campaigns/).

| Field | Type | What it does |
| --- | --- | --- |
| `title` (required) | text | Cause name on cards, in the menu card, and the H1 |
| `description`, `image`, `imageAlt`, `imageCaption` | | Summary, photo, its alt text, and the caption line under the page photo |
| `category` | category id | Its filter group on `/causes/` (an `id` from `categories` in `-index.md`) |
| `goal`, `raised` | number | The goal and the amount raised so far, in the donate `currency` |
| `donors` | whole number | The donor count ("640 donors") |
| `deadline` | date | Last day of the appeal. Empty means ongoing |
| `location` | text | Where the work happens |
| `featured`, `order` | true/false, number | Shown on the homepage and at the top of `/causes/`; order in lists (lowest first) |
| `gallery` | list of `image`, `alt` | Photos from the field on the cause page |
| `impact` | list of `amount`, `label`, `icon` | "What a gift does" lines on the cause page |
| `updates` | list of `date`, `title`, `text` | Dated 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.

### Donate
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](/givo/customization/donation-form/) and [Giving Tiers & Receipt](/givo/customization/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](/givo/customization/events-calendar/).

| Field | Type | What it does |
| --- | --- | --- |
| `title` (required) | text | Event name |
| `category` | category id | Its filter group on `/events/` |
| `start`, `end` | date and time | Wall-clock times where the event happens, as `2026-11-15T09:00:00` |
| `timezone` | text | Time zone of those times, such as `"Europe/Paris"`. Empty uses `timezone` in `[organization]` |
| `venue`, `address` | text | Where it happens. The address is also written to the calendar file |
| `online` | true/false | An online event, with no venue |
| `capacity` | whole number | Places available |
| `price` | number | Ticket price. `0` or empty means free |
| `registerUrl` | URL | Where the Register button goes. Empty goes to `/contact/?topic=events` |
| `featured` | true/false | Marks a highlight event; an events section with `featuredOnly: true` shows only these |
| `imageAlt`, `imageCaption` | text | Photo 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](/givo/customization/impact-transparency/).

### Gallery
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](/givo/customization/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.

| Field | Type | What it does |
| --- | --- | --- |
| `name` | text | First name and last initial, such as `"Daniel R."` |
| `role` | `donor` \| `volunteer` \| `partner` \| `beneficiary` | Shown with the name, and used by the role filter of the `wall` layout |
| `text` | text, up to 700 characters | The quote |
| `cause` | cause id | Links the quote to a cause, so a section can show only the voices about it |
| `date` | date | Newest first |
| `featured` | true/false | Featured band on `/testimonials/`, first pick in other layouts |
| `image` | image path | Optional portrait. Without it, only the name shows |
| `draft` | true/false | Hides 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`.

| Field | Type | What it does |
| --- | --- | --- |
| `code` | text | Job reference shown on the page |
| `department` | department id | Team column on `/careers/` |
| `location` | text | "Riverside office", "Remote" |
| `type` | `full-time` \| `part-time` \| `contract` \| `internship` \| `seasonal` | Labels from `careers.types` in `src/i18n/<language>.json` |
| `pay` | `min`, `max`, `unit` (`hour` or `year`) | Pay range, in the donate `currency` |
| `schedule`, `start`, `interviews` | text | Facts on the role page |
| `date`, `validThrough` | date | Posting date and last day to apply |
| `applyUrl` | URL | Your applicant system or a `mailto:` link. Empty sends an email to `email` in `[organization]` |
| `weight` | number | Order 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](/givo/customization/stories/) and [Writing Content](/givo/customization/writing-content/) for the shortcodes you can use in stories.

### Do It With AI
```text
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.
```