Every church administrator knows the feeling. The website still shows last year's Easter service times. The pastor listed under Our Leadership left eighteen months ago. The photo gallery is from a fundraiser nobody can quite place. Someone built the site with good intentions, learned just enough to keep it ticking, and then moved on — and now the page that visitors find first is a quiet record of everything the congregation has not gotten around to fixing.

Hiring someone to sort it out is expensive, and it rarely addresses the real problem: updating a church website should not require specialist skills, and it should not depend entirely on one person who holds all the knowledge. This guide walks through what Daviah provides to help a church keep its website current — and is honest about one thing it does not yet solve.

A website that exists the moment you sign up

With most website tools, building a site is itself a project. You start with a blank page, make decisions about layout and structure, and eventually produce something that resembles a real website — weeks later, if everything goes smoothly. When a new church is created on Daviah, a website is generated from a design straight away, with a front page and pages for the church's sections already in place, ready to edit.

There are eight designs in five styles — Heritage, Ledger, Meridian, Vantage and Plate — and the design can be changed later from the office. The site gets its own address on the platform from the start. On the Website and Members plan, the Daviah team handles the domain connection: they register the church's own domain, the church adds one DNS record, and the security certificate is issued automatically.

Editing pages without writing a line of code

The most common reason a church website goes stale is that whoever is responsible for it does not feel confident enough to touch it. Pages on Daviah are built from a library of 42 ready-made sections. A church administrator adds a section, fills in the text, and reorders things — there is no code, no template language, and nothing that requires a developer's eye.

Before anything goes live, a draft page can be previewed through a private link. Whoever is checking it sees exactly what visitors will see before approving it for publication. That one step removes a good deal of the anxiety that stops people making changes in the first place.

Giving someone website responsibility without giving them the keys to everything

In a small congregation, it is rarely practical for the church administrator to be the only person keeping the website current. But handing over the full office — with giving records, congregation details and meeting notes — to a volunteer who only needs to post a notice is not sensible either.

Daviah has a Website Editor role for exactly this situation. Someone given that role can edit the site without any access to the congregation's money or member records. A trusted volunteer, a member of the congregation who is comfortable with a computer, or someone helping from home can keep the website current while the administrator keeps control of everything else.

Events, news and leadership that reflect what is in the office

A large part of what makes a church website feel stale is that the information on it no longer matches what is actually happening. The website draws its events, news notices and photo galleries from what is entered in the office — so when an administrator adds a service event or posts a notice, it appears on the website without a separate publishing step.

The same applies to Our Leadership. The public site can show the church's current officers, taken from the officer records in the office. When a Pastor, Church Secretary or Treasurer changes, the website reflects that as soon as the officer record is updated — no one has to remember to edit a separate page.

The person entering next Sunday's service into the office does not need to think about the website at all. The website draws from what they have already done.

A little help with the writing and the flyers

One reason church website pages go stale is that writing about events feels like an extra task on an already full day. The office can draft wording about an event for a person to read, edit and approve — nothing is saved or published until someone approves it, so the church is always in control of what goes out.

For events that need a flyer or a social image, the office can generate a printable flyer, a square social image, a portrait social image and an email banner, with the event's details already typeset. The Website and Members plan includes 40 pieces of generated artwork each month. Neither of these tools removes the need for a person to read and approve what is produced — they remove the blank-page problem that makes the task feel harder than it is.

What Daviah does not yet solve: when the website volunteer leaves

It would not be honest to leave this out. One of the most difficult moments in a church's website history is when whoever has been maintaining it moves on. All the knowledge of how things are set up, what is half-finished, and what decisions were made leaves with them.

Daviah does not have a handover or succession feature for this. There is no role-transfer process, no built-in documentation of what was configured and why, and no structured way to brief the next person. What it does offer is the ability to invite new administrators or a new Website Editor to the office — so access can be managed and a new person can be added before the previous one leaves. But that is an organisational step the church has to take for itself. The tool will not prompt anyone to do it.

Questions

Does the church need to hire someone to build the initial website?

No. A website is created from a design the moment the church is set up on Daviah, with a front page and pages for the church's sections already in place. The church's own people edit it from there using a library of 42 ready-made sections — no code or developer needed.

Can a volunteer update the website without seeing the congregation's giving records?

Yes. The Website Editor role lets someone edit the site without any access to money or member records. It is designed for a trusted volunteer who handles the website and nothing else.

If the pastor changes, does someone have to remember to update the website separately?

No. The page that shows Our Leadership is drawn from the officer records in the office. When the officer record is updated, the website reflects the change — no separate edit is needed.

What happens to a draft page before it goes live?

Any unpublished page can be previewed through a private link, so whoever is checking it can see exactly what visitors will see before approving it for publication.

Does the church need to arrange its own domain and security certificate?

On the Website and Members plan, the Daviah team handles the domain connection. They register the domain, the church adds one DNS record, and the security certificate is issued automatically.

What if the person who has been maintaining the website leaves?

Daviah does not have a formal handover or succession feature. The church can invite a new administrator or Website Editor before the previous person leaves, and access can be managed from the office — but there is no built-in process to document what was set up or brief the next person. That step is the church's to take.

Read next