joseph.soper

Write-up · Petoskey Church of Christ

The pastor writes the week once. Everything else follows.

Every week the pastor of Petoskey Church of Christ wrote the same content three times: on the website, again for the Sunday email, and again in Canva for the printed bulletin. Now he writes it once, as that week's Weekly Vine. The website, the email, the printed bulletin, the slides in the sanctuary, the lobby TV and the titles on the sermon video all take it from there.

November 2026

Three copies of one week

Typing a week three times wasn't only slow. It gave the week three chances to disagree with itself. Rebuilding the bulletin in Canva was the biggest manual job of his week, and the copy it produced drifted from the website every time.

One record, read one way

The week now lives in a single record: the sermon title, the reading, the pastor's thought, the announcement, prayer requests and the week's plans. Every surface reads that record through one function that turns it into the shape a page renders from, so a field added to the record reaches every surface without each one being changed. Text that is the same every week, like service times and the address, lives in the church's settings, so it is never typed again. No surface keeps its own copy.

One weekly record, every surface The pastor writes the week once into the Weekly Vine record. Church settings supply the text that never changes. Every surface reads the record the same way and asks the same question, whether it is live yet. The surfaces are the Worship page, the home page and feed, the Vine archive, the Sunday email, the printed bulletin, the welcome slides, the prayer slides, the lobby TV and the sermon video. The pastor writes the week once The Weekly Vine one record for the week Settings fixed text One read, one gate the same data, and "is it live yet?" SITEWorship page SITEHome page, feed SITEVine archive EMAILSunday email PRINTPrinted bulletin PROJECTORWelcome, prayer LOBBY TVSermon slide YOUTUBESermon video
Pink is the record, violet is what the site renders from it, cyan is an outside service.

One answer to "is it live yet?"

The pastor often writes the Vine days ahead, and a sermon must not be announced before it is preached. So a Vine stays out of public view until 10:30 on its Sunday, unless he chooses to publish it early.

That hold first lived inside the Worship page, because it was the only page that showed a Vine. Then other pages learned to show one, and a Vine written ahead leaked onto three of them at once, because none of them asked. A sermon title went public before the sermon. The fix was one check, and every surface calls it. A surface that doesn't is a defect, however right it looks in a browser.

Checking that fix turned up a second bug. Every Vine on the public archive was dated the Saturday before its service. The stored date is a calendar date, and two places converted it as if it were a moment in time, through UTC, which in Michigan lands on the evening before. It was first filed as cosmetic. It isn't: a sermon dated wrong is the church saying something false about itself, so it was fixed straight away.

Two surfaces show part of the Vine early on purpose. The lobby TV and the welcome slides show that day's sermon title and reading from midnight on Sunday, because people read them walking in, before the service begins. They only ever show the Vine dated today, never a later week's.

When a Vine becomes visible Before Sunday, only editors can see the Vine and print it ahead. From midnight on Sunday, the lobby TV and the welcome slides show its title and reading. At 10:30 on Sunday it goes live everywhere on the site, and a purge booked for that moment clears the page cache. On Sunday evening the email goes out with the Vine leading. After the service, the sermon video takes its title and description from the Vine. BEFORE Editors only see it, and print it ahead MIDNIGHT Lobby TV, welcome slides today's title and reading SUN 10:30 Live everywhere a purge booked for this minute clears the cached pages SUN EVENING Sunday email the Vine leads, then what's new AFTER Sermon video title card, YouTube title and description from the Vine
One week of one Vine. Everything before 10:30 on Sunday is a deliberate exception to the one check.

The cache that kept the gate shut

The 10:30 switch was built without a scheduled job: the stored answer to "which Vine is current" expired by itself at the next go-live time. That worked on staging. In production a page cache sits in front of the site, keeps a page for up to seven days, and answers without running any of the site's code. So the copy cached on Saturday, with last week's Vine on it, was what visitors got all Sunday. The check was right, and nothing ever asked it. It went on for three months.

The proof took one pair of requests in the same second, to the same server: the cached Worship page showed the previous Sunday's sermon, and the same page with a cache-busting parameter showed the right one.

Now, saving a Vine dated ahead books a purge for its go-live minute, and a weekly Sunday sweep at 10:30 backs it up. Both clear the same four pages through one function, so there is one list of what to clear.

A page that loads from a cache proves the page loaded, not that the code ran. Before trusting what a page shows, I check whether the cache answered it.

The bulletin lays itself out

The printed bulletin is the Vine on both sides of a sheet of Letter paper. Each side is sized to the largest type that fits. Only if the front would drop below about 8 point does the end of the pastor's thought carry over to the back, a paragraph at a time, never mid-paragraph.

While he writes, the real print view can sit beside what he's writing, updating a moment after he stops typing. It is built from the unsaved text, and nothing is stored until he saves. Every place the print code reads the record goes through the same lookup, so a single hook hands it the unsaved values and no reader had to change. Because it is the print view itself and not an imitation of it, the preview can't disagree with the printout.

Slides, the lobby TV and the sermon video

The projector computer runs presentation software that takes PowerPoint files, so the site builds the welcome slides as a PowerPoint deck. Each slide is drawn as a picture rather than as text boxes, because that computer doesn't have the site's font and a substitute would undo the design. The site checks the deck every fifteen minutes and rebuilds it when anything on it has changed, so the download is current and instant. The prayer and benediction slides take their verses from the Vine the same way.

The lobby TV mixes photos with slides built from what the site already holds: upcoming events, what each event still needs, the gatherings through the week, and that day's sermon title. Nobody types a slide for it.

After the service, a script reads that Sunday's Vine, renders the title card for the video's intro, and writes the YouTube title and description. The YouTube title is the Vine's sermon title, word for word.

The Sunday email

Subscribing, confirming and sending are a small amount of the site's own code instead of a newsletter plugin, with mail sent through a transactional email service. No plugin update can break the send, and the subscriber list stays in the church's own database. Each Sunday's email carries everything new since the last one went out, with the Vine leading. Counting from the last send rather than a fixed week means a late Vine doesn't turn into a silent Sunday.

How it is run

It's WordPress, so people at the church can run it without me. Every change is tested on a copy of the site first and deployed to production by script. Only code moves between them; content never does.

Where it falls short