A community organization website volunteers can keep up to date
Residents associations, tenants' groups, friends-of-the-park groups and neighbourhood forums share one website problem: the person who built it moves on and the site goes stale. A community organization website should be simple enough for any committee member to update, and focused on what people need: the next meeting, recent news, how to join and how to help.
The questions residents bring
- When's the next meeting, where, and can anyone come?
- What is the group doing about the issue I care about (the bus route, the planning application, the park toilets)?
- Who's on the committee, and how do I contact them?
- How do I join, and does it cost anything?
- How can I help without committing every week?
Answer the first on the home page, every time. A dated "Next meeting" panel does more for trust than a mission statement, because it shows the group is active.
News and meetings in the CMS
Anticode's CMS keeps content separate from design. Set up two collections: meetings (date, time, venue, agenda, and a link to the minutes once approved) and news (title, date, summary, body). Each entry gets its own page at an address like /news/park-toilets-reopen, and any committee member with dashboard access can add one in a few minutes without touching the layout.
There are no comments, RSS feed or scheduled posting, so publish news when it's ready and point people to your newsletter or social channels for discussion. The post news updates workflow has a routine that small groups can keep up.
Documents and minutes
Constitutions, annual reports, accounts and approved minutes belong on the site, because members have a right to see them and newcomers judge the group by them. The CMS holds text, not file uploads, so there are two options:
- Minutes as pages
- Paste approved minutes into a
minutesentry. They become searchable, readable on a phone and accessible to screen readers, which PDFs often aren't. - Documents as links
- Keep PDFs where the group already stores files and link to them from a documents page, with the date and a one-line summary of each.
Publish minutes only after they're approved, and leave out personal details about residents that were discussed in the meeting.
Membership sign-up
Many groups need a membership list to show they represent the area, or to meet the terms of their constitution. A custom form tied to a site function can ask for name, address or street (to confirm eligibility), email, phone, and whether they'd like to volunteer. State your area of benefit beside the form, and point people outside it to the neighbouring group. For subscription fees, link a buy button to a payment link from your provider; there are no member logins or member-only pages on published sites.
Send sign-ups to a Google Sheet or Airtable with a connector so the membership secretary has a list, and newsletter sign-ups to Mailchimp or Kit. See community group membership sign-ups.
Volunteer roles, small and specific
"Get involved" pages that just say "we always need volunteers" don't work. List roles with a time commitment: deliver the newsletter on your street four times a year, help at the summer fair for one afternoon, take minutes at meetings, keep the website news up to date. People say yes to small, named tasks.
Handing the site over
Plan for the next person from the start. Use the group's own email for the account, not a personal one. A Team workspace lets several committee members work on the site, and members can't delete the project or take the site down, which protects it from accidents. Anyone who can read form submissions must have two-factor sign-in turned on before a data-collecting site publishes, and a submissions access log records the last 200 reads, exports and deletes. Remove people's access when they leave the committee; see remove employee website access, which applies to volunteers too.
Mistakes on community websites
- A home page announcing an event that happened last spring.
- Committee members' personal phone numbers published without thinking it through; use a group email or the contact form.
- Long pages of history before the next meeting date.
- Pale text on photographs of the neighbourhood, hard to read for older residents.
Organic (Figtree) or Swiss (Inter Tight) with a clear action colour keeps the site readable. Related: nonprofits and food banks.
Limits
- No member logins, forums or members-only pages.
- No file hosting in the CMS; link to documents.
- No comments, RSS or scheduled posts.
- No card payments on the site; payment links for subscriptions.
Questions people ask
Can several committee members update the community group website?
Yes. A Team workspace gives each person their own access, and news and meetings are edited as CMS entries in the dashboard.
How should we publish meeting minutes?
Paste approved minutes into a CMS entry so they're readable on any device, or link to the files where you already store them.
Can members pay a subscription online?
Yes, through a payment link from your provider on the membership page. The site doesn't keep track of who has paid.