Somewhere on most church websites is a link that reads "This Week's Bulletin" and points to a PDF. It is usually four pages, laid out in Publisher, exported without accessibility tags, and last updated three Sundays ago. On a phone — where nearly every visitor actually finds it — it opens as a zoomable image nobody zooms.
The bulletin is not a bad idea. The PDF is.
What the page should be instead
A single, plain URL — /this-week is our favorite — that lists what is happening between now and the next Sunday, in the order a real person would ask about it. No download. No login. Nothing to unzip.
Roughly:
- One sentence about Sunday's service theme or sermon text.
- Three to five announcements, each two lines, with a link if there is one.
- A short list of what is on the calendar the rest of the week.
- The next give / serve / connect step at the bottom.
That is it. The whole page reads in under a minute on the treadmill, in the pickup line, or in the pew ten minutes before the service starts.
Why this quietly matters
Search engines can read it. Screen readers can read it. Older members can pinch-zoom the browser without fighting a locked PDF viewport. Newcomers can share the URL in a group chat without asking someone to "download that thing." And Friday's late edit takes thirty seconds instead of "wait, I need to re-export the PDF and re-upload it."
The bulletin as an artifact of Sunday morning is not going anywhere — printed copies still matter to the people who love them. But the online version does not have to be the print version pretending to be a webpage. It can be its own thing, and be better at what the web is actually good at.
If you would like help designing yours — or migrating five years of PDF bulletins into something searchable — we would be glad to help.