The person who built the site knew what they were doing. Or at least, they knew more than everyone else. So they became the one who updated it — and over time, without anyone deciding it should work that way, the whole thing depended on them. When their situation changed, the site stopped changing too. Services listed for the wrong time. A menu that no longer matched what was on offer. An events page that stopped in the middle of last year. A staff page with names of people who had moved on.

The problem is not that nobody cares. The people running these organisations care a great deal about making a good impression. The problem is that the tools got in the way. Editing the site required skills most people on the team did not have, or access they had not been given, or confidence that came only from doing it often — and most people did not do it often enough to stay confident. This guide explains what Daviah changes about that situation, and what it does not. It covers four kinds of organisation — churches, clubs, schools and restaurants — because the pain is the same in all of them, even if the words are different.

A website that exists before you have done anything

With most tools, setting up a website is itself a project. You choose a template, arrange a layout, fill in placeholder text, and spend a week before anything looks presentable. Daviah skips that entirely. When a new organisation is created, a website is built from a design at that moment — a front page and pages for the organisation's sections, ready to edit.

The site is not public until you choose to make it so, which means you can take time getting it right without worrying about what visitors see in the meantime. There are eight designs across five styles to choose from, and the design can be changed later from the office. What this gives you is a starting point that looks like something, on the day you sign up, without any specialist involved.

Editing pages without writing code or calling for help

Pages are built from a library of forty-two ready-made sections. The people who run the organisation add sections, reorder them and edit the words directly — no code, no specialist, no support ticket to raise before a change can happen.

Before any edited page goes live, it can be previewed through a private link. That means whoever is making the change can check that it looks right first, which removes one of the reasons people hold back from touching the site at all — the fear of publishing something that looks broken.

Giving someone website responsibility without handing over everything

One reason website updates pile up is that the only people with access are the same people who manage the money and the member records. Giving a new volunteer access to update the site means giving them access to things they should not need to see.

Daviah separates this with a Website Editor role. Someone given that role can edit the site without access to the money or member records. If that person later steps away, another person can be invited to take on the same role. The site and its content stay in the office.

Events, news and leadership drawn from what is already in the office

A common reason websites go stale is that updating the site is a separate task from running the organisation. An event gets added to the internal calendar, and then someone has to remember to also add it to the website. When that second step gets missed — and it often does — the site falls behind.

The events, news notices and photo albums shown on the site are drawn from what is entered in the office, and the Officers page reflects the leadership records held there. Enter something once, and the site reflects it.

For churches: the congregation sees what is actually happening

A church website is often the first thing a visitor checks before deciding whether to attend a service. If the times are wrong or the Leadership page shows people who have moved on, that impression is hard to recover. The Congregation — the people already attending — also rely on the site for dates, notices and Ministry information.

Because the site draws from the office, a Church Administrator entering a new event or updating Leadership details does not need to remember to update the website separately. The AI draft tool can help with wording for a notice or event — the Administrator reads it, edits it and approves it before anything is saved or published.

The one thing Daviah does not solve is what happens when the person who has been maintaining the site leaves and there is no handover. There is no documentation tool or succession feature built in. The Website Editor role means you can invite someone new — but the knowledge of how to use the site travels with whoever held it.

For clubs: the Committee stops fielding questions the site should answer

When a club's website is out of date, Members go looking for answers in other places — messaging groups, emails, whoever they can reach on the Committee. The Committee ends up answering the same questions repeatedly, because the site has stopped being reliable.

The Club Administrator or Secretary can edit the site directly, without technical help. Events, news and the Officers list are drawn from the office. A contact form on the site captures enquiries and routes them into the office, so nothing lands in a personal inbox and gets lost.

One thing this does not fix: information that has spread across external messaging apps and social platforms stays there. Daviah does not pull content in from those channels or consolidate them. What it does is make the club's own site easier to keep accurate, so it becomes a reliable place to send people.

For schools: urgent updates without the dread of breaking something

School office staff are already carrying a full workload. Updating the website is one more thing on the list, and if the tool feels risky — if there is a chance of accidentally breaking something — it gets put off. Urgent notices go out through other channels instead, or parents are left without the information they need.

The block editor is designed to be used by people who are not developers. A School Administrator or School Secretary can add a section, update a page and check it through the private preview link before it goes live. The Website Editor role means a staff member can be given editing access without being given access to Student records or Fees.

One area this guide cannot address: compliance requirements for school websites vary by district or governing body, and Daviah does not have features built around regulatory or legal compliance. If your school has specific requirements about what must appear on its site, that is a question to take to your District or Board separately.

For restaurants: the menu that matches what you are actually serving

Keeping the website and menu accurate is time-consuming, and Owners rarely have the time or technical skill to do it themselves. Outdated information drives customers away. A menu or product catalogue can be published on the website on any paid plan, without paying for online ordering.

The Owner or a Manager can edit the site using the block editor, without needing a developer or a web agency. The Website Editor role means someone can be given responsibility for keeping the site current without being given access to Takings or Staff records.

This guide is about the restaurant's own website. Keeping information accurate on Google, social media or aggregators is a separate task, and Daviah does not update those channels. What it addresses is making the restaurant's own site easier to keep current — so that the version customers find there reflects what is on offer today.

Questions

Does the site need to be rebuilt from scratch when we sign up?

No. When a new organisation is created, a website is built from a design at that moment, with a front page and pages for the organisation's sections already in place. You edit what is there rather than starting from a blank page.

Can someone edit the website without seeing our financial records or member details?

Yes. The Website Editor role lets someone edit the site without access to the money or member records. You can invite as many people as you need into that role.

Do we have to update the website separately every time we add an event in the office?

Events, news notices and photo albums shown on the site are drawn from what is entered in the office. Adding an event in the office means it appears on the site without a separate update step.

Can we check how a page looks before it goes live?

Yes. Unpublished pages can be previewed through a private link before they go live. That includes pages you are editing for the first time and pages you are updating.

What happens when the person who has been updating the website leaves?

Another person can be invited to take on the Website Editor role. The site and its content stay in the office. The one thing Daviah does not provide is a handover or documentation tool — knowledge of how to use the site travels with whoever held it, and that is worth planning for separately.

What does it cost to publish a menu on the website?

A menu or product catalogue can be published on the website on any paid plan, without paying for online ordering. The Website plan is $29.99 a month, or $300 a year.

Read next