Skip to content
serpico.

Religious community

A Parish Website with a Custom Admin Panel

For a UGCC (Ukrainian Greek Catholic Church) parish in Lviv, we built a website with news, a service schedule, sermons with a player and a gallery, plus a custom admin panel where the parish manages all content itself. The project has 27 screens and 33 APIs.

Client
UGCC parish in Lviv
Region
Lviv, Ukraine
Timeframe
June - August 2026
Tech stack
Next.js 16 · React 19 · Tailwind CSS v4 · Supabase · Vercel · Власна аналітика · Карти
screens
27
APIs
33
commits
325
A Parish Website with a Custom Admin Panel

Challenge

The parish needed a website it could easily update on its own, without contacting a developer every time the schedule changes or a news item comes up.

For a parish website, this is harder than it seems:

  • the service schedule is regular but has exceptions: holy days, time changes, individual days;
  • sermons need to be published with audio or video and a convenient player;
  • the parish has several communities, and each wants its own page;
  • news is often prepared in advance and has to go live on a specific day;
  • several people work on the site, so separate accounts with invitations are needed.

Website builders offer basic pages but lack a schedule with exceptions, sections for priests and saints, or community management. The parish also wanted to see how visitors use the site without complex third-party tools. And all of this had to be clear to non-technical people who run the parish website every day and should not have to deal with code.

What we did

We built the website and admin panel on Next.js 16, React 19, Tailwind CSS v4 and Supabase, deployed on Vercel. From June to August 2026, the project accumulated 325 commits, 27 screens and 33 APIs.

Public site

  • an about the parish page;
  • news;
  • service schedule;
  • sermons with an embedded player;
  • community pages;
  • gallery.

Admin panel

  • news with an editor and scheduled publishing;
  • page management;
  • a schedule with exceptions for holy days and special days;
  • sermons, communities and gallery;
  • sections for priests and saints;
  • users with invitations;
  • site settings;
  • built-in analytics: sessions and events;
  • map.

We designed the admin panel around the parish's specific tasks, so each section matches what actually needs updating. The person running the site does not have to deal with unnecessary settings.

Results

The parish got a website and a full-featured admin panel where it manages news, the schedule, sermons, communities and the gallery on its own. A news item can be prepared in advance and scheduled for the right day, and a holiday schedule change can be entered as an exception without rewriting the whole schedule.

What this delivers:

  • content is updated without a developer;
  • several people work in their own accounts, and new ones are added by invitation;
  • sermons are available with a player right on the site;
  • built-in analytics shows sessions and events without third-party services.

We do not cite traffic figures, because the goal of the project is a convenient tool for the community, not an ad campaign.

What makes this project special

Most parish websites are built with website builders or templates, where the schedule is just text and sermons are links to third-party platforms. Here, the schedule has a structure with exceptions, sermons have their own player, and priests, saints and communities have their own sections in the admin panel.

The project's scope, 27 screens and 33 APIs, is comparable to business systems, even though it is used by non-technical people. That is why we focused primarily on keeping the admin panel simple.

Published: · Updated:

Questions about this project

How long does it take to build a website with a custom admin panel?

We ran this project from June to August 2026, and it has 27 screens and 33 APIs. For your organization, the timeline depends on the number of sections and what exactly needs to be managed through the admin panel.

What drives the cost of a website for a community or organization?

The price depends on the number of admin modules, public pages and integrations. A schedule with exceptions, a sermon player or built-in analytics add to the scope compared with a simple brochure website.

Can non-technical people update the site?

Yes, the admin panel is designed around the parish's specific tasks: news, schedule, sermons, communities, gallery. New people are added by invitation, and everyone works in their own account.

How does the service schedule with exceptions work?

The main schedule is set once, and exceptions are added for holy days or special days. This way you do not have to rewrite the whole schedule because of a single change.

Why build your own analytics when third-party services exist?

The built-in analytics shows sessions and events right in the admin panel, without separate dashboards. This is convenient for people who do not want to deal with complex tools.

Who supports the site and who owns the code?

We set the terms for code ownership, access and support in the contract before work begins. New sections can be added to the same admin panel without rebuilding the site from scratch.

More case studies

A CRM for a Meat Producer's Marketplaces, Orders and Pricing
Web Development

A CRM for a Meat Producer's Marketplaces, Orders and Pricing

For a Lviv meat processing producer, we built a single dashboard that brings together feeds, orders, stock, shipping labels and prices from the client's own WooCommerce store and the MauDau and Rozetka marketplaces. The system now has 18 screens, 74 API routes, 6 roles and 5 scheduled automated jobs.

screens in the dashboard
18
API routes
74
Read case study →
Hurtom: A B2B CRM and Wholesale Customer Portal
Web Development

Hurtom: A B2B CRM and Wholesale Customer Portal

Hurtom brings wholesale orders, order picking with actual weights, documents and account balances together in one CRM with a separate customer portal. Thanks to a ready foundation from a previous project, the first working version with all modules was ready in about 3 hours.

screens in the CRM
19
screens in the customer portal
9
Read case study →
Adding New Products to 1C (BAS): A Workflow Across 5 Departments
Web Development

Adding New Products to 1C (BAS): A Workflow Across 5 Departments

Instead of an Excel template, we built a tool where 5 departments fill in a new product card in parallel, the CFO approves it, and accounting exports the BAS technical sheet with one click. Development took 6 days.

days of development
6
departments in the workflow
5
Read case study →

Want results like these?

Tell us about your goals and we'll estimate your project's growth potential.

Free consultation

Tell us about your project and we'll prepare a growth plan