Back to the blog

I rebuilt my church’s website in 8 hours (with Statamic and a little help from AI)

11 min read

This post is also available in: Română (Romanian)

Ever since I was a teenager I’ve been kind of semi-responsible for my church’s website, bisericasega.ro. Over the years I built it with different systems: at first, being a big WordPress fan, it was on WordPress, then I moved it to October CMS. But for a while now the site had been pretty outdated, with a lot of missing information. The service times changed, I stopped adding the archive… because everything had to be done by hand. And you know how it goes: when something has to be done by hand, in the end nobody does it.

The turning point: a bug in PHP

You probably heard or read about it, because it made it into the press, on TV, on Biziday: PHP, the programming language, recently had a pretty serious vulnerability. With a bit of effort, anyone could take control of the server. When the fix came out, you had to update.

So I looked at what sites I have on the server where this blog also lives and what needed updating. The church website was on the list. The problem was that it ran on a pretty old October CMS, on PHP 7, and it didn’t support PHP 8, which I needed to move to in order to be up to date. All the other sites were already on PHP 8, only this one was left behind.

So on Wednesday morning I sat down to rewrite the site. This time, from the start, with one single rule: it has to be a low maintenance website. I don’t want to add the archive by hand anymore, and I don’t want a lot of information that needs to be kept up to date.

The homepage of the new bisericasega.ro
The homepage of the new site. “Next service” is calculated by itself from the schedule.

Why Statamic

I chose Statamic, a CMS built on top of Laravel. What I like about it is that it has no database: everything is a file. The pages, the sermons, even the video archive are static files (YAML/Markdown) in a folder. And even though it works with files, it’s very well indexed, so it’s fast.

I went with the Pro version, because I needed more than the free one offers. For example, the site is in Romanian and English, and for multiple languages you need Pro.

The even better part for me, as a programmer, is that besides everything the CMS gives you, you have the full power of the Laravel framework. Artisan commands, the scheduler, controllers, everything you already know. The stack looks like this: Statamic 6, Laravel 13, PHP 8.4, Tailwind CSS 4.

A bonus of everything being a file: the content lives in git too, not just the code. GitHub is the meeting point between my laptop and the live server. I push to main, GitHub Actions runs a deploy.sh on the server and in less than a minute it’s live. When the server changes something by itself (the YouTube sync, which I’ll tell you about in a second), it also commits and pushes, marked with [skip ci], so it doesn’t end up redeploying itself forever.

What happens on the site by itself

This is the part I’m most proud of. Almost nothing has to be done by hand anymore.

The video archive syncs with YouTube

We now livestream the church services on YouTube. When a new scheduled livestream shows up, it’s copied automatically to the archive on the site. The sync runs every 10 minutes, plus at the start time of a service and then 3 and 5 minutes after, so the red LIVE now badge in the header shows up as fast as possible:

Schedule::command('sega:youtube-sync')
    ->everyMinute()
    ->when(fn () => now()->minute % 10 === 0
        || ServiceSchedule::isStreamCheckDue(GlobalSet::find('settings')?->inDefaultSite()?->get('schedule') ?? []))
    ->withoutOverlapping();

Schedule::command('sega:youtube-sync --all')->dailyAt('04:30')->withoutOverlapping();

Every night it goes through the whole channel. Anything deleted from YouTube gets unpublished on the site too.

The video archive on bisericasega.ro, synced automatically with YouTube
The video archive: more than 2,500 recordings, with filters for livestreams, video clips and the 2008–2020 archive.

I also brought over the old archive: around 1,400 recordings from 2008–2020. For now many of them can’t be played, because they were served by a server that physically sits at the church and is currently turned off. But every entry kept its file name, so if that server comes back, I fill in one variable in .env and the old archive works again.

Winter time applies by itself

From the last Sunday of October until the last Sunday of March, the site automatically shows the winter schedule. There are no “events” to create. In the settings there’s just the weekly schedule, and a service can also have a winter time. The code that decides is basically one line:

$winter = static::isTime($row['winter_time'] ?? null) && ! $day->setTime(12, 0)->isDST();

Meaning: if on that day Romania isn’t on summer time, the winter time is used. Done. Nobody has to remember to change the time on the site when the clocks change. (Fun fact: I’m writing this exactly on the weekend the clocks go back, and the site already switched by itself to the winter schedule for tomorrow :)) )

The church's weekly schedule with winter time applied automatically
The Sunday evening and Thursday services already have the “Ora de iarnă” (winter time) label. I didn’t click anything.

The same schedule is also used to calculate the “next service” and the countdown on the homepage.

Sermons: from a two-hour livestream to an MP3 in five minutes

This is my favorite part. I made myself a command, php artisan sega:predica, which runs on my computer, not on the server:

  1. It downloads the audio from the YouTube livestream (with yt-dlp).
  2. It transcribes it locally, with Whisper (whisper-cli, the large-v3-turbo model). A two-hour service gets transcribed in about a minute and a half on an M-series Mac.
  3. It sends the transcript, with timestamps, to Claude through the API. Claude finds where the sermon starts and ends and proposes a title, the Bible passage, a 2–3 sentence summary and the preacher’s name. It costs somewhere around 15–30 cents per service.
  4. It shows me everything so I can check it. The cuts snap to pauses in speech and I can listen to the first and last 15 seconds before I accept. Nothing reaches the site without my confirmation.
  5. It cuts the sermon into an MP3, mono at 64 kbps, with the volume evened out, so all the sermons play at the same loudness:
'ffmpeg', '-hide_banner', '-loglevel', 'error', '-y',
'-ss', (string) $start, '-to', (string) $end, '-i', $audio,
'-vn', '-ac', '1', '-ar', '44100', '-c:a', 'libmp3lame', '-b:a', '64k',
// Even out the volume so every sermon plays at the same loudness.
'-af', 'loudnorm=I=-16:TP=-1.5:LRA=11',
  1. It uploads the MP3 to Cloudflare R2, so it doesn’t take up space on my server (R2 has no bandwidth fees, and the 10 GB in the free tier will last for years), then it publishes the sermon on the site, linked to the video of the whole service.
A sermon page on bisericasega.ro, with an audio player and a switch to video
A sermon page: the title, the preacher and the passage come from Claude’s proposal (checked by me). The Audio/Video buttons switch between the MP3 and the service video.

On the sermon page you can switch between audio and video at the same point, you can watch the whole service, not just the sermon, and the Bible text that was read shows up too, verse by verse. And here’s a small nostalgic moment: the Bible text (Cornilescu) comes from the data of my old bible-api project, which I made around 12 years ago, also for the church website.

The sermon summary and the Bible text shown verse by verse
The automatically written summary and the Bible text, taken from my old bible-api.

A few things I learned along the way:

  • Whisper invents phrases when there’s music. On the instrumental parts it calmly writes things like “Thanks for watching!” or “See you at my next recipe!”. Nobody said anything like that in church, I promise :)) In the prompt I tell Claude explicitly that lines like these are music, not speech.
  • The answer comes back as JSON validated by a schema. I don’t parse free text anymore, I get the fields directly: start, end, title, passage, summary, preacher, plus a confidence, so I know where to look more carefully.
  • Spelling matters. I ask it to write the way the church writes: “Isus”, never “Iisus”.

In short: in five minutes at most I have a sermon cut out, with a title, the text, the preacher and the main idea, uploaded to the site and linked to the service it belongs to.

A podcast on Spotify and Apple Podcasts, almost for free

Since the sermons already have an MP3, a title, a summary and a date, it was easy to make an XML feed: bisericasega.ro/podcast.xml. It’s an RSS 2.0 feed with Apple’s podcast tags, generated by a small Laravel controller that takes the published sermons and leaves out any episode whose MP3 can’t be read, so it never publishes something broken.

Thanks to it, the sermons are now a podcast (in Romanian):

The sermon list with links to Spotify and Apple Podcasts
The sermon list, with a filter by preacher and the podcast badges.

Speed and design

On Google PageSpeed I often get 100 on desktop, and on mobile somewhere between 94 and 97, depending on how the test runs at that moment. Just today, while writing this, desktop came out at 100 in all four categories:

Google PageSpeed Insights on desktop: 100 for Performance, Accessibility, Best Practices and SEO
PageSpeed Insights, desktop, October 24, 2026.

A few small things helped: the CSS is inlined on the live page, the map only loads when you scroll down to it, Google Analytics only starts at the first interaction or after 5 seconds, and after every deploy the main pages are already warmed up in the cache, so the first visitors don’t have to wait.

I did the design mostly with Claude (Opus). I tweaked it a bit by hand and told it what to change, but overall I think we now have a modern website. It also has dark mode, following the phone’s setting, search across the whole site (diacritics don’t matter) and short links like bisericasega.ro/l/<code> for posters and QR codes.

The bisericasega.ro homepage in dark mode
The same page in dark mode. It switches by itself based on the device setting.

And so I wouldn’t break anything that already existed, the old October CMS addresses still work: old links and Google results redirect to the new pages.

Conclusion

I’m really happy with Statamic. For anyone who knows Laravel, it’s an extremely good CMS: it helps you without getting in your way, and you still have the whole framework at your disposal. I recommend this stack.

But what I’m happiest about is that it’s low maintenance. I don’t have to go in and change anything unless something actually changes in the rules. The videos land in the archive a few minutes after they show up on YouTube, winter time sets itself, and a sermon I can cut and upload in a few minutes.

Without AI, this would probably have been a one-week project. This way, I did it in about eight hours of work, and that’s being generous: if I actually add it up, I think it was less. Back in the day you could work a whole month on a site like this, now it was done in one working day. I like the times we live in.

What do you think? What would be worth changing, what would be worth adding? I’d say it’s a useful website for a church: not too much information, not too little. And I like how it turned out.

PS: The site is here: bisericasega.ro (it has an English version too). Statamic docs, for the curious: statamic.dev.

The conversation continues here.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.