Webflow CMS for Nonprofits:
Programs, Impact, and Team

Nonprofit websites have a specific content problem. The organization does meaningful work — programs that change lives, impact data that proves it, team members who drive it, events that fund it, and partners who support it. But the website rarely reflects that complexity. Instead, it gets a static "About" page with a paragraph from 2019 and a "Programs" page that is actually just a list of bullet points.

The issue is not design talent or budget. It is CMS architecture. When the CMS does not have the right collections and fields, content editors cannot maintain the site without a developer. Programs get added as rich text blocks instead of structured CMS items. Impact stats get hardcoded into page sections. Team member photos get embedded in rich text instead of a proper collection.

This guide walks through the CMS collections nonprofits actually need, how to structure them for editorial independence, and how Trellis generates the right structure automatically. For a detailed reference on nonprofit collection architecture, see the nonprofit CMS architecture wiki.

Why Nonprofits Need Structured CMS

Most nonprofit websites start as brochureware — a few static pages built by a volunteer or a donated agency project. The site launches looking great. Six months later, the executive director needs to add a new program, update the board list, and post three upcoming events. None of these changes can be made without touching the Designer or asking the original developer for help.

Structured CMS solves this. When programs, team members, events, and impact metrics each have their own CMS collection with the right fields, anyone on the team can add, edit, and remove content without touching the design. The site stays current because updating it is as simple as filling in a form.

The challenge is getting the structure right from the start. Too few collections and you are back to hardcoding content. Too many and the CMS becomes confusing for non-technical editors. The sweet spot for most nonprofits is six to ten collections — enough to cover every content type, lean enough to stay manageable.

The Typical Nonprofit Collection Set

After building CMS architectures for dozens of nonprofit sites, the following collection set covers the vast majority of use cases. Not every nonprofit needs every collection, but this is the menu to choose from.

Programs

The core of what the organization does. Each program gets its own CMS item with fields for: Name, Description (Rich Text), Hero Image, Program Category (Option), Status (Active/Completed/Upcoming), Impact Summary, Target Audience, Location, and a Reference to the Program Lead (from the Team collection).

Structuring programs as CMS items — rather than sections on a static page — means each program can have its own URL, its own SEO metadata, and its own landing page template. When a funder asks "send me a link to your youth mentorship program," you have one. See the programs collection guide for field recommendations.

Impact Stats

Numbers tell the story that paragraphs cannot. A dedicated Impact Stats collection holds: Metric Label ("Families Served"), Value ("2,400+"), Year or Time Period, Category (Option: Education, Health, Housing), Sort Order, and a Switch for "Featured on Homepage."

With impact stats as CMS items, you can display them dynamically — a homepage counter section that pulls the top four stats, a program page that shows program-specific metrics, an annual report page that lists everything. When numbers update annually, the change is one field edit per stat, not a design session.

Team Members

Every nonprofit has a team page. Most build it as a static grid that becomes outdated the moment someone joins or leaves. A Team Members collection with: Name, Role/Title, Photo, Bio (Rich Text), Department (Option), Email, LinkedIn URL, Sort Order, and a Switch for "Show on Team Page" makes the team page self-maintaining.

The "Show on Team Page" switch is critical. It lets you keep former team members in the CMS (for historical records or annual reports) without displaying them on the active team page. Toggle off when someone departs, toggle on when someone joins.

Board of Directors

Board members have different content needs than staff. They typically need: Name, Title/Affiliation, Photo, Bio (shorter than staff), Term Start Date, Term End Date, Board Role (Chair, Treasurer, Secretary, Member), and a Switch for "Current Board Member."

You can structure board members as a separate collection or as part of the Team Members collection with a "Type" option field (Staff vs Board). A separate collection is cleaner if board members have significantly different fields. A shared collection saves a collection slot and is fine if the fields overlap substantially.

Events

Galas, fundraisers, volunteer days, community workshops — nonprofits run events constantly. An Events collection with: Name, Date, End Date, Location, Event Type (Option: Fundraiser, Volunteer, Workshop, Gala), Description (Rich Text), Featured Image, Registration Link, Ticket Price (or "Free"), and a Switch for "Featured Event."

Filtering by date lets you show upcoming events on the homepage and archive past events on a separate page. Filtering by type lets you create dedicated pages for volunteer opportunities, fundraising events, or community programs.

Donors and Partners

The logo bar at the bottom of every nonprofit homepage. A Partners collection with: Organization Name, Logo, Website URL, Partner Type (Option: Funder, Corporate Partner, Government, Community Partner), Tier (Option: Platinum, Gold, Silver), and Sort Order.

Structuring this as a CMS collection rather than a static image grid means adding a new partner is a 30-second CMS entry, not a design request. Filter by tier to show top-level partners more prominently. Filter by type to create separate sections for funders, corporate partners, and government agencies.

Testimonials and Stories

Impact stories and constituent testimonials are powerful fundraising tools. A Stories collection with: Person Name, Quote or Story (Rich Text), Photo, Program (Reference to Programs collection), Year, and a Switch for "Featured on Homepage." Connecting stories to programs lets you display relevant testimonials on each program page automatically.

Resources and Downloads

Annual reports, policy briefs, toolkits, educational materials. A Resources collection with: Title, Description, File (for PDFs), Resource Type (Option: Annual Report, Policy Brief, Toolkit, Fact Sheet), Year, and a Thumbnail Image. This turns a cluttered "Downloads" page into a filterable, searchable resource library.

Showing Impact Data Dynamically

Impact metrics are the single most underutilized content type on nonprofit websites. Most organizations have compelling numbers — families served, meals distributed, students graduated, dollars raised — but they are buried in annual reports or hardcoded into a homepage section that was last updated two years ago.

With a dedicated Impact Stats collection, you can build dynamic impact sections throughout the site:

• Homepage hero stats: A collection list filtered to "Featured on Homepage" showing 3 to 4 headline numbers with animated counters
• Program-specific metrics: Filter by program reference to show relevant stats on each program page
• Year-over-year comparison: Use the Year field to show growth trends — "2024: 1,200 families served. 2025: 2,400 families served."
• Annual report page: A complete metrics dashboard pulling all stats, grouped by category, for board presentations and grant applications

When a program director updates a number after a quarterly review, the change propagates to every page that displays that metric. No developer needed. No design changes. One field edit, everywhere updated.

Managing Team and Board Members

Staff turnover at nonprofits is a reality. The average tenure for nonprofit employees is shorter than the private sector, and board terms rotate on fixed schedules. A CMS that cannot handle these transitions without a developer is a CMS that will always be out of date.

The key architectural decisions for team management:

• One collection or two? If staff and board members share most fields (name, photo, bio, role), use one Team Members collection with a "Type" option field. If they have significantly different fields (board members need term dates, staff need department and email), separate collections are cleaner.
• Visibility toggles: Add a "Show on Website" switch to every person-type collection. This lets you keep historical records without displaying departed staff. It is also useful for new hires who have not been publicly announced yet.
• Department grouping: Use an option field for departments, then filter collection lists by department to create grouped team pages (Leadership, Programs, Operations, Development).
• Sort order: Add a numeric Sort Order field for manual ordering. The executive director should appear first, not alphabetically between D and F.

Events and Programs Architecture

Events and programs are often confused in nonprofit CMS architecture. They are related but structurally different. Programs are ongoing initiatives with long-term impact. Events are time-bound occurrences that may or may not be part of a program.

The relationship between them matters. A mentorship program (ongoing) might host a mentor training workshop (event), a quarterly meetup (recurring event), and an annual graduation celebration (annual event). Connecting events to programs via a reference field lets you show upcoming events on each program page and attribute events to the programs they support.

For organizations with recurring events (monthly volunteer days, weekly workshops), each occurrence is a separate CMS item. This seems redundant, but it allows each occurrence to have its own date, registration link, capacity, and status. A "Recurring Event" option field or a Reference to a parent event can group occurrences for display purposes.

How Trellis Generates the Right Structure for Nonprofits

Building the CMS architecture described in this guide manually takes hours. Creating each collection, adding the right fields, configuring field types, setting up references between collections, and testing the editorial workflow. It is the kind of structured, detail-oriented work that is perfect for automation and painful for humans.

Trellis generates the right CMS structure for nonprofits automatically. Tell Trellis about your organization — the programs you run, whether you need an events calendar, whether you track impact metrics — and it creates the full collection architecture: Programs, Impact Stats, Team Members, Events, Partners, and any additional collections your specific organization needs.

Every field is typed correctly. References between collections are configured. Option fields have sensible default values. The structure follows the patterns described in this guide — because these patterns were developed from real nonprofit projects and encoded into how Trellis makes architectural decisions.

If your nonprofit already manages content in Airtable — program lists, team rosters, event calendars — Trellis can connect directly and map your existing data into the Webflow CMS structure. No manual migration. No copy-pasting between tabs. Your Airtable is the source of truth, and Trellis keeps Webflow in sync.

Frequently Asked Questions

How many CMS collections does a typical nonprofit site need?

Most nonprofit sites need between six and ten collections. A minimal setup covers: Programs, Team Members, Events, and Partners (four collections). A comprehensive setup adds: Impact Stats, Board Members (or merged with Team), Stories/Testimonials, Resources/Downloads, Blog Posts, and Blog Categories. The exact number depends on what content your organization produces and how often it changes.

Should we manage board members and staff in the same collection?

If they share most fields (name, photo, bio, role), a single collection with a "Type" option field is simpler. If board members need term dates, committee assignments, and other fields that staff do not have, separate collections avoid cluttering the staff editing experience with irrelevant fields.

How do we handle programs that have ended?

Add a "Status" option field with values like Active, Completed, and Paused. Filter your public-facing collection lists to show only Active programs. Completed programs remain in the CMS for historical reference, annual reports, and impact attribution — they just do not appear on the active programs page.

Can we show different impact stats on different pages?

Yes. Use a combination of reference fields and switch fields. A "Featured on Homepage" switch controls which stats appear on the homepage. A reference to the Programs collection lets you filter stats by program on each program page. A "Category" option field lets you group stats on an annual report or impact page.

What about donation integration?

Donation processing (Stripe, PayPal, Donorbox, Give Lively) is separate from CMS architecture. Your CMS manages the content that drives donations — the impact stories, the program descriptions, the event pages with registration links. The donation flow itself is typically an embedded form or an external page linked from your CMS content. Keep them separate: CMS for content, donation platform for transactions.

Does Webflow offer nonprofit pricing?

Webflow does not publish a formal nonprofit discount, but they have historically offered discounts on a case-by-case basis. Contact Webflow sales directly with proof of 501(c)(3) status. Regardless of pricing, the CMS architecture recommendations in this guide apply to all Webflow plans.