HOURThe HourHOUR-004
The Calendar That Ran the Week
Coffee house, fundraisers, holy week, workdays: the events archive as a log of how one church spent its year.
Entry checked on · about 3 min
Record v1 · 13 years of captures · reviewed 2026-09-21
Read as a log rather than a list, the events archive is the best instrument on this bench for the parish's real year. The calendar existed in every era: a .cfm schedule in 2002, a full events system in the WordPress years, weekly pages before both.
The stated protocol
The calendar sorted life into categories, children, youth, worship, classes, and published entries per event with dates and recurrences. The fixed points are legible: a coffee house each spring, a Valentine's dinner fundraiser, an Easter egg hunt, holy week services, a dads and kids campout, adoption workshops, the VBS week in July, workdays on the building. A river town lot by lot marks the same kind of recurring ground; what repeats each year is what the community actually runs on.
What the record measures
A river town lot by lot marks the same kind of recurring ground: what repeats each year is what the community actually runs on.
The calendar shows cadence better than any narrative page could. Youth events cluster on Sunday afternoons; the coffee house and the dinner fundraiser mark winter; holy week and Easter mark spring; VBS and the campout own the summer; the adoption workshops recur as ministry, not event. The weekly.htm and whatsnew.htm pages from the static era show the same rhythm before software formalized it: the year ran on a published loop.
The deviation
A published calendar lists intentions, and some entries are announcements rather than occurrences; the archive cannot confirm turnout at a single coffee house. Recurring categories, though, are harder to fake than single events: a calendar that keeps renumbering a prayer meeting and re-dating a fundraiser is measuring something real. The deviation is per-event, not structural.
The .cfm ancestor
The earliest calendar survives as a ColdFusion page with dated schedule queries in 2002, crude by later standards but already doing the same job: the week published for anyone who looked. Between that and the categorized events system of the 2010s, the parish ran at least three calendar technologies. The protocol outlived each tool. On the bench that is the significant finding, that a congregation this size kept its week in public continuously, whatever the software underneath.
Held against the whole file
The calendar is the bench's integrity check on every other card. If the children's track, the youth series, the prayer meeting and the VBS week all appear in the same dated system, then those ministries were not brochure claims but scheduled realities. A calendar is harder to keep falsely than a page, because it must be updated to stay plausible. This one was updated for years, which is why it functions here as the parish's master instrument.
The fundraiser as marker
The Valentine's dinner fundraiser earns a line because of what it implies: a community willing to buy tickets to its own dinner, year after year, to keep something funded. Fundraisers are the calendar's honesty check; they only recur if they work. Paired with the coffee house, the egg hunt and the workdays, the pattern is a parish that paid its way with its own evenings. The record does not publish the take, only the recurrence, and the recurrence is the more durable measurement.
Verdict
Documented: a categorized, continuously maintained events system spanning fifteen years, with legible annual rhythm. Not shown: attendance per event, cancellation rate. The calendar is the parish's truest public instrument, and the archive kept it almost whole.
