How the CMS Works

Philosophy

The finished site will be fully editable by your team for day-to-day needs. The goal isn't to limit control — it's to make editing safer, clearer, and easier.

What staff can do

Edit content

Headlines, body text, links, images, and media on any page

Manage sections

Add, remove, and reorder predefined sections within a page

Update CTAs

Change calls to action, button text, and button destinations

Create pages

Build new pages using existing layouts without developer help

This covers the vast majority of real-world content changes.

How sections work

Pages are built from a set of reusable section types (block components):

Text blocks
Image + text combinations
Call-to-action sections
Statistics / impact metrics
Embeds (donation forms, maps)
Card grids (services, team, FAQs)
Testimonials

What this means in practice

Add sections to pages
Choose which sections appear and in what order
Adjust the content inside each section freely
Create new pages from existing section types

Keeps layouts consistent and clean across pages
Maintains accessibility standards automatically
New pages match the rest of the site automatically

When to involve a developer

For larger changes like:

New section types
New page templates
Structural changes to navigation

This matches how things already work: your team handles content updates, and bigger changes happen collaboratively.

Content update expectations

Aspect	Expectation
Update frequency	Occasional, not frequent
Blog publishing	Current cadence is fine
Landing pages	Staff can create as needed
Section reordering	Supported within pages
Content additions	Supported without developer help

The site should work well even if content changes infrequently. It's designed for stability, not constant publishing.