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

Volunteer & Fundraise Pages

Files: src/content/pages/<language>/volunteer.md, src/content/pages/<language>/fundraise.md · Skill level: Beginner

Two ways for supporters to help beyond a gift: give their time on /volunteer/, or raise money for you on /fundraise/. Both pages end in a sign-up form. Both forms send to the same address as the contact form (contactFormAction in config.toml), so connect your forms first: see Forms.

The Volunteer Page

/volunteer/ is built from the blocks in src/content/pages/<language>/volunteer.md, top to bottom:

BlockWhat it showsDefaults in
pageHeaderTitle, description, buttons, and a photo with its caption
featureGridSectionWhat volunteering here is like, beside a photofeature-grid-section.md
volunteerRolesSectionThe open roles, each with where, how much time, and skillsvolunteer-roles-section.md
stepsSectionHow to start, as numbered stepssteps-section.md
volunteerSectionThe sign-up form, with short points and a volunteer’s quote beside itvolunteer-section.md
questionsSectionQuestions about volunteeringquestions-section.md
ctaSectionThe closing bandcall-to-action.md

A block only needs the fields it changes; the rest come from the section file named in the last column (in src/content/sections/<language>/). See Sections.

Volunteer Roles

Each role is one item in roles:

volunteerRolesSection:
roles:
- id: "kitchen"
title: "Community kitchen shift"
description: "Sort donations, pack food parcels, and welcome people at the door."
where: "Community kitchen, Mill Street" # sample
commitment: "3 hours"
frequency: "a week, Tuesday or Friday morning" # sample
skills: ["Teamwork", "Lifting light boxes", "Food hygiene (we train you)"]
url: "/volunteer/?role=kitchen#volunteer-form"
linkLabel: "Apply"
options:
layout: "list" # default | list
  • id is the value of the role’s checkbox in the sign-up form. Every role becomes a checkbox, so adding a role adds a choice to the form.
  • url with ?role=<id> ticks that role in the form and scrolls to it. The Apply links on /volunteer/ do this without reloading the page.
  • commitment and frequency together read as “3 hours a week, Tuesday or Friday morning”.
  • layout: "list" (used on /volunteer/) shows one row per role with its skills, place, time, and Apply link. default shows the roles side by side, led by the time they take, with a small drawing (illustration). /home-community/ uses default.

The sample roles, places, and times are examples. List the roles you really need, and keep a catch-all such as “Anywhere I am needed” if you want people to sign up without choosing.

The Volunteer Form

The form’s words are in src/content/sections/<language>/volunteer-section.md, under form::

form:
emailSubject: "New volunteer sign-up"
name: { label: "Full name", placeholder: "Your name" }
email: { label: "Email", placeholder: "[email protected]" }
phone: # remove to leave the phone field out
label: "Phone (optional)"
roles:
label: "Which roles interest you?" # the checkboxes are the roles above
days:
label: "Which days are you usually free?"
items:
- { label: "Mon", value: "monday" }
message: # remove to leave the message field out
label: "Anything we should know?"
consent:
label: "I agree that the team may contact me about volunteering. [Privacy policy](/privacy-policy/)"
submitLabel: "Send my sign-up"
success: "**Thank you, your sign-up is in.** We will be in touch within five working days."
error: "**That did not go through.** Please try again, or email us at {email}."
  • The consent box is required.
  • {email} in the error message is your email from [organization].
  • success is a promise: change “within five working days” to what you can keep.
  • The same file holds the text beside the form: title, description, points, the volunteer quote (remove it to leave it out), and a note for under-18s.

The form sends each answer to contactFormAction with your contactFormProvider, with or without JavaScript. With JavaScript, the success or error message shows in place.

The Fundraise Page

/fundraise/ invites supporters to raise money for a cause: a birthday, a run, a workplace challenge. Its blocks are in src/content/pages/<language>/fundraise.md:

BlockWhat it shows
pageHeaderTitle, description, and a photo
featureGridSectionFundraising ideas
stepsSectionHow it works
fundraisersSectionExample fundraisers, each with a goal bar
toolkitSectionFiles to download: a guide, posters, a sponsorship form
contactSectionThe “Register your fundraiser” form
questionsSection, ctaSectionQuestions and the closing band

Current Fundraisers

src/content/sections/english/fundraisers-section.md
items:
- title: "Ten kilometres for clean taps" # sample
organizer: "Daniel and his running club" # sample
idea: "Sports challenge"
cause: "clean-water-wells" # cause id: the card links to the cause page
image: "/images/photos/gallery-standpipe-tap.jpg"
imageAlt: "A brass standpipe tap in a green garden"
raised: 2140 # sample
goal: 3000 # sample
supporters: 58 # sample
deadline: "2027-03-14" # sample; "YYYY-MM-DD" in quotes; empty: ongoing

Every fundraiser in the file is a sample. Replace them with your supporters’ real fundraisers (with their permission), or set enable: false in a fundraisersSection: block to hide the section. Like causes, the figures are numbers you type and update yourself.

The Toolkit

src/content/sections/english/toolkit-section.md
items:
- title: "Fundraising guide"
description: "Twelve pages of ideas, a timeline, and how to pay in what you raise."
format: "PDF · 12 pages"
url: "#" # sample: replace with "/files/fundraising-guide.pdf"
icon: "FileText" # FileText | File

Put your files in public/files/ and link them as "/files/<name>.pdf". A url of "#" marks a sample: the row says “Sample file” and shows no download link, so nothing broken goes live.

The Fundraiser Form

The register form is a contactSection block in fundraise.md, written like the contact form (see Forms). Its Cause dropdown fills itself with your published causes:

- label: "Cause"
name: "Cause"
required: true
dropdown:
type: "select"
source: "causes" # one option per published cause, then the items below
items:
- label: "Where it is needed most"
value: "Where it is needed most"

When you add a cause, it appears in this list with no change here. The other fields (name, email, idea, target amount, date, message) are plain inputs you can edit, add, or remove.

Where The Pages Are Linked

The header’s Get involved menu links to Volunteer, Fundraise, and the other ways to help. The homepage “Get involved” section (involvedSection) and the volunteer band on /home-community/ link there too. To remove one of the pages, take its links out of src/config/menu.<language>.json and the homepage blocks, and set draft: true in its file in every language.

Do It With AI

Replace the volunteer roles on /volunteer/ with these: [ROLE: what they do, where, how much time,
how often, skills]. Edit volunteerRolesSection.roles in src/content/pages/<language>/volunteer.md,
in every language, give each role a short id and a url /volunteer/?role=<id>#volunteer-form, and
keep a catch-all role. Then check that each role shows as a checkbox in the form.
Replace the sample fundraisers in src/content/sections/<language>/fundraisers-section.md, in
every language, with these real ones: [TITLE, ORGANIZER, CAUSE ID, RAISED, GOAL, SUPPORTERS,
DEADLINE]. Use photos I name: [FILES]. If I gave none, turn the section off on /fundraise/.
Type something to search...