Volunteers run the chapter websites. None of them has to be a web developer.

Dozens of chapters, and every one of them is run by volunteers

The National Peace Corps Association is the alumni organization for people who served in the Peace Corps. Much of its community lives in affiliate groups: chapters built around a city or a region, and groups built around the country where their members served.

Each chapter is led by volunteers. There is a president, a board, often a newsletter editor, and all of them have day jobs. The chapter website is how members find the next event and how a newly returned volunteer finds the chapter at all.

The person in charge of that website is usually whoever raised a hand. NPCA's national staff is small, and it cannot be the help desk for every chapter. A volunteer cannot be asked to learn web development either.

Every chapter wanted its own look, and nobody could maintain dozens of different sites

On the platform NPCA was leaving, chapters had little control over their own web presence. They wanted more. A chapter has its own name, its own logo, its own colors, and its own way of talking to members. A group of people who served in one country does not want to look like a city chapter three states away.

The obvious answer, a separate custom website for each chapter, would have buried everyone. Dozens of differently built sites mean dozens of things to update and secure. A fix made on one would have to be repeated on all the others, and sooner or later some would be missed.

Volunteers also move on. Whatever a chapter leader learned about the website leaves with them, and the next person starts cold. So the sites had to be safe to hand over, again and again.

NPCA's staff needed two things that pull against each other: chapters that are independent day to day, and a network that a small team can actually look after.

One foundation, and a settings screen for everything that makes a chapter itself

We put one shared foundation under every chapter site. All of them run the same theme, so when we improve something or fix something, we do it once, and every chapter has it. Nobody waits for their turn.

We moved branding to a settings screen. A chapter volunteer picks three brand colors, uploads a logo, and fills in contact details and social links. The whole site takes on the chapter's identity in one sitting, with no code and no request to anybody. When we update the shared theme, each chapter's colors carry over on their own.

We gave volunteers ready-made sections to build pages with: news, upcoming events, leadership profiles, photo galleries, and buttons for donating and joining. The newsletter editor builds a page by choosing sections and filling them in, so there is no layout to get wrong.

We gave volunteers an editor role with guardrails. They can write, publish, change the chapter's settings, and add the next volunteer as an editor. They cannot install plugins, edit theme files, or reach the administrator accounts. Handing the site to next year's board is safe, and a well-meaning click cannot take the site down.

We kept every chapter a separate site with its own content. A problem on one chapter's site stays with that chapter.

Every chapter that wants a site has one, and the volunteers run them

Today more than thirty chapter sites run on the same foundation, and no two look alike. Chapter leaders post their own news and events. When a board changes, the outgoing volunteer adds the incoming one and steps back.

NPCA's national staff are not the chapters' help desk for routine changes, because most of what a chapter needs, a volunteer can do on their own. Our part is the work underneath: hosting, updates, and security for the whole network, handled from one codebase. When something gets better, it gets better for every chapter on the same day.

This network began as a move off an all-in-one platform, which is its own story.