We build the systems that schedule, book, and coordinate.

A mission for RSVP-System I started when you laid out pages with tables and prayed they'd render the same in Netscape as they did in IE. Since then I've watched the web reinvent itself more times than I can count — portals, blogs, social, mobile, the app store, the cloud, and now machines that answer your question before you finish typing it. Twenty-five years of churn.

One of the most common patterns on a community platform home page is the "three pillars" row — a set of short, punchy columns that each highlight a key feature and invite visitors to take action. Events. Resources. Announcements. Browse. Reserve. Learn more.

When you manage a platform used by a town government, a university housing office, and a neighborhood association — sometimes all at once — access control becomes a surprisingly hard problem. Who can post an announcement? Who can approve a room reservation? Who can manage the Library's calendar but not the Town Clerk's?

How we're building a resource reservation system that actually understands how communities work — on Drupal, with open source, for the long haul. Every community organization has the same problem.

Overview Every fix or feature follows this path:

If you host Drupal on Pantheon and develop locally with DDEV, you can run a perfectly solid workflow without ever touching Multidev: Branch in GitHub Test locally in DDEV Open a pull request Deploy to Pantheon Dev Promote Dev → Test → Live That’s already a big improvement over “push straight to Pantheon and hope.”

I manage a production Drupal site on Pantheon. Real users depend on it, and for a long time my development workflow was embarrassingly simple: pull it down to DDEV, fix the thing, push directly to Pantheon Dev, and hope for the best.

The RSVP-System Cookbook is built around a simple promise: spin up a fully-featured community calendar and reservation platform by applying a set of Drupal Recipes. No manually clicking through the admin UI, no hunting for which modules need which config. You run the recipes, you get the system.

Every scheduling tool I've ever used treats a calendar the same way: as a container for events, filtered by date. You pick a month, you see what's in it. January looks like July. August looks like November. The tool is indifferent to meaning. But communities don't experience time that way.