Emerald Curtain Collective

The Problem

Emerald Curtain Collective protects Oregon Coast ecosystems through art, education, and community action. It was founded in January 2025, it is run by volunteers, and like most young nonprofits it was assembling its operations out of whatever the plugin directory happened to offer.

That works until it does not. Their events are ticketed and they sell out. Their artist roster appears in a dozen places across the site. Their education program is built on specific coastal species with structured information behind each one. Off-the-shelf plugins covered about eighty percent of each of those, and the missing twenty percent was where the volunteer hours were going.

What We Built

Four plugins, each solving one thing the organization actually does, all running on their WordPress site today.

Artist Profiles

An artist roster with a photo, a biography, and up to four links each, embeddable anywhere on the site through the block editor. The cards render on the server rather than being copied into pages, so updating a profile once updates it everywhere it appears. Nobody has to remember which pages an artist is on.

Wildkin Profiles

Structured profiles for the keystone coastal species in ECC's education program. Volunteers fill in specific fields rather than a blank page, which is the difference between a set of profiles that stay consistent and a set that drift apart as different people write them.

Event Check-In

A check-in tool that lives at a plain address on the site and works on any phone, with no WordPress login and no admin access. Volunteers get a list of the day's events, one-tap check-in, QR ticket scanning through the device camera, walk-in registration, and cash donation logging.

Two decisions in there matter more than the feature list. The QR scanner is bundled with the plugin instead of loaded from a public CDN, so the tool does not depend on a third party being up on event day. And check-ins are optimistic and queued locally, so a volunteer standing in a hall with one bar of signal can keep working and the queue drains when the connection returns.

Event Waitlist

Built because a September gathering sold out and people kept asking to be added to a list that did not exist. When tickets are gone, a signup form appears on the event page. When a spot frees up, an invitation goes out by hand and drops the held ticket straight into the visitor's basket, so the normal checkout runs and the donation step is not skipped.

Inviting by hand is deliberate. Automatic release sounds better until two people claim the same returned ticket, and a volunteer organization would rather send a personal email than manage a race condition.

Where It Landed

All four plugins are in production on the organization's site. The check-in tool runs their events from volunteers' own phones, the artist and species profiles are maintained by the people who know the content rather than by whoever knows WordPress, and the waitlist exists because a real event sold out and real people asked to be told when a seat opened.

The quieter outcome is the one worth naming. None of this needed a developer standing by on event day, which for a volunteer organization is the difference between a tool they use and a tool they are afraid of.