Repository navigation
docs(specs): events, RSVPs, and calendar (#194) - #197
Merged
Merged
Conversation
Formatter-only; no content changes. Keeps the events spec diff readable. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Staff-created events with one-click member RSVPs, calendar files, and reminder emails, so the site becomes the system of record for the monthly hack night instead of Meetup.com. New: behaviors/events.md (time, status lifecycle, RSVP rules, iCalendar semantics, reminders, duplicate-not-recur, Meetup transition, local principles), api/events.md, screens/events-index.md, event-detail.md, event-edit.md. Threaded through: Event + EventRsvp in data-model.md and the storage sheet layout; event slug rules and new reserved words; legacy /events/*past and /calendar rewrites; Events in the header, footer, and breadcrumbs; an upcoming-events strip on the home page; the text/calendar carve-out in conventions; event-rsvps in the person purge cascade. Deferred with promotion notes: programs with sessions (laddr's Event + EventSegment, four records ever), recurrence, capacity, cover images, Slack announcements, month grid. The old "event check-ins" entry is rewritten now that RSVPs are on-site. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Three plans for the events spec: core (model, API, screens, emails, home strip) unblocks the reminder sweep and the backfill of the four historical laddr events, which can run in parallel. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Design review outcomes. Three changes to the events spec:
- The post-RSVP question is a three-way choice — "I'm new to Code for
Philly", "I don't have a project yet", "I'm coming to work on X" — so
newcomers have an answer that isn't a project picker. EventRsvp gains
`plan`; the attendee list groups by project, then newcomers, then
undecided.
- Flat events stay flat, but an optional EventSeries ("Monthly Hack
Nights", "Launchpad") with its own page replaces the deferred
parent/child programs design, and an embedded `agenda` of timed items
renders laddr's day-grouped Schedule sidebar. Sessions get identity
only when they need RSVPs — then they become events in the series.
- Private RSVPs are written up in deferred.md as a supplemental record in
the private store, never a flag on the public one.
Also records why the reminder sweep is in-process (the write mutex) and
that the API and direct data-repo commits are equally valid ways to
create next month's event.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
events-core keeps the RSVP follow-up; series and agendas get their own plan after core; the laddr backfill now depends on it so the four historical events carry their segments as agenda items under a "Launchpad" series instead of flattened markdown. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This was referenced Oct 14, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Spec and plans for replacing Meetup.com with site-native events, per #194. Specs only — no runtime code.
behaviors/events.md(time, status lifecycle, RSVP rules, series, agenda, iCalendar semantics, reminders, duplicate-not-recur, Meetup transition, principles),api/events.md,screens/events-index.md,event-detail.md,event-edit.md,event-series.md.Event(flat, one record per occurrence),EventRsvp(binary, public, with a three-way follow-up: new / no project / working on X),EventSeries(a label with a page, never a generator), embeddedagendaitems that render laddr's day-grouped Schedule sidebar./events/*pastand/calendarrewrites, header/footer/breadcrumbs, an upcoming-events strip on the home page, thetext/calendarcarve-out in conventions, person-purge cascade.events-core→events-reminders,events-series-agenda→events-legacy-backfill.Design review: https://99b533a5.ht-ml.app/ (all seven decisions went with the recommended option; the notes are folded in).
The first commit is formatter-only (markdownlint table separators) so the content diff stays readable.
🤖 Generated with Claude Code