More than 30 people showed up to the Berlin Peace Corps Association kickoff in 2025—not for a keynote, but because a returned volunteer had spent months wondering where everyone else was. Germany had no local Peace Corps association. In the United States, those groups are commonplace: alumni, staff, counterparts, and family members keeping the community alive after service. In Berlin, the need was the same; the infrastructure was not.
MWWE founder Judson Moore served as a Peace Corps volunteer in the Kyrgyz Republic from 2010 to 2013. After nearly a decade in Berlin, he wanted what many returned volunteers want—a place where people who share that experience can find each other. The Berlin Peace Corps Association is the public face; membership and events run elsewhere. The portfolio case study covers the web build—this post is how the community actually operates.
No local association in Germany
Peace Corps creates durable bonds—host-country friendships, staff relationships, families who lived the arc of service alongside volunteers. Stateside, local associations give that network a name, a rhythm, and a place to gather. Germany did not have an equivalent. For returned volunteers in Berlin, “community” often meant individual friendships or the occasional reunion, not an org you could join on a Tuesday.
That gap is not a failure of the Peace Corps mission. It is a local organizing problem: someone has to map who is here, create channels people actually use, and keep the invitation open as new people arrive.
Finding each other first
The first work was discovery. LinkedIn searches surfaced a surprising map: on the order of a hundred people in Berlin with some tie to Peace Corps—returned volunteers, staff, counterparts, and family members. Names led to messages; messages led to channels where introductions could travel faster than one-to-one outreach.
Not every “join us” link should dump strangers into a group chat. A returned-volunteer community needs a way to verify that applicants actually share the experience—or a close enough tie to it—before the room opens up. That verification problem shaped everything that came next.
From chat to kickoff
The association formalized in 2025. The kickoff drew more than thirty people—proof that the latent network was real, not a mailing list fantasy. Since then the calendar has filled with the essense of community: Thanksgiving dinners, nights out, nature walks, and other social gatherings that give returned volunteers an excuse to leave their apartments and recognize each other in person.
Those events are planned in the WhatsApp community—the place members use day to day once they are in. LinkedIn and the public site sit upstream; WhatsApp is where the group coordinates.
LinkedIn as the membership gate
berlinpeacecorps.org does one job well: it points people to LinkedIn. The association runs a private LinkedIn group as a quality gate for membership applicants.
When someone wants to join, their Peace Corps connection has to be legible—typically Peace Corps experience on a LinkedIn profile that organizers can review. If the tie checks out, they are admitted to the group and encouraged to join the WhatsApp community, where events and informal planning happen as a group.
That flow is deliberate:
- Public site — discoverability for “Peace Corps Berlin” and a clear next step.
- Private LinkedIn group — vetting before access; keeps the inner circle aligned with the association’s purpose.
- WhatsApp — ongoing coordination; members propose and schedule gatherings without maintaining a website calendar.
Time is scarce. Asking the same people to publish event posts to a CMS every week would have been the wrong default. Membership verification belongs where résumés already live; social planning belongs in chat.
A static site on purpose
The website is static—built with Eleventy (11ty) and hosted on Cloudflare Pages. It is not meant to be logged into, updated weekly, or treated as the system of record for announcements. No volunteer should be on the hook for “who knows how to publish.”
Static here means stable and low-maintenance: a few pages that explain what the association is and hand off to LinkedIn. When the community’s rhythm lives in a private group and a WhatsApp thread, the site stays a signpost, not a second job.
MWWE built that site for the Berlin Peace Corps Association with the same static-first posture used elsewhere: predictable hosting, few moving parts, and a clear split between public discovery and private community tools.
Berlin had returned Peace Corps volunteers looking for each other. The association mapped the network, opened a vetting gate on LinkedIn, and moved real life—Thanksgiving, walks, nights out—into WhatsApp once trust was established. The website supports discovery; it does not pretend to be the community.
If you are growing a volunteer community and want a partner who will match technology to how people actually join and coordinate—not every org needs a CMS—contact MWWE.