Every club has one. The person who built the website years ago, who knows the password, who is the only one who can change the fixtures list or the Subscription rate when it goes up. For a long time this works well enough. Then that person gets a new job, or moves away, or simply runs out of time — and the site quietly freezes. The AGM notice is still there from two seasons back. The Officers page lists someone who retired. The contact details go to an inbox nobody checks. Members start asking questions that the site should already answer, and the same small group of Committee volunteers ends up fielding every one of them.

One part of this problem — information scattered across messaging groups, email threads and social platforms — is not something Daviah solves. No part of the platform pulls content in from those external channels, and this guide will not pretend otherwise. What Daviah does address is the part that begins with the website itself: getting a site that exists from the moment the club signs up, giving more than one person the ability to update it, and making sure the pages members look up most often reflect what is actually in the office.

A site that exists from the first minute

One reason club websites go stale is that building the original one took enormous effort from a single capable volunteer. When that person leaves, nobody wants to repeat the work — so nothing changes, or the old site simply stays up indefinitely.

When a new organisation signs up on Daviah, a website is created from a design at that moment, with a front page and pages for the club's sections, ready to edit. No setup project, no blank canvas to fill from scratch. The site exists; the Committee's job is to keep it current, not to build it.

Editing pages without writing a line of code

The other reason sites go stale is that editing them requires technical knowledge that most Committee volunteers do not have and have no reason to acquire. If updating the Subscriptions page means logging into a hosting account and editing a template, it simply will not happen.

Pages on Daviah are built from a library of ready-made sections. A Committee member adds a section, moves it, fills it in and saves — no code involved. Before anything goes live, an unpublished page can be previewed through a private link, so whoever made the change can check it looks right first.

Giving someone website responsibility without handing over everything

A common reason clubs do not spread website editing more widely is understandable caution: giving someone access to the site often means giving them access to everything. A volunteer who is happy to update the news and fix the contact details should not need to see financial records or member information to do it.

Daviah has a Website Editor role that lets someone edit the site without access to member records or money. The Administrator can invite additional people to help run the organisation, each with the access level their role requires and no more.

Events, news, galleries and Officers drawn from the office

A significant part of the stale-site problem is duplication: someone adds an event to the club's record, then has to separately update the website to mention it. When the second step gets skipped — and it often does — the site falls behind.

On Daviah, the site shows the club's events, news notices and photo albums drawn from what is entered in the office. The Officers page on the public site is taken from the officer records, so it reflects who actually holds each role. When a role changes in those records, the page reflects the change — there is no separate editing step to forget.

A contact form that lands in the office

Members who cannot find what they need on the site turn to the Committee directly — a pattern that takes up time the Committee does not have. A contact form helps only if someone actually sees the enquiries.

Every Daviah site has a contact form with spam defences and rate limits. Enquiries land in the office, where the Administrator and officers can see them, rather than routing to a personal email address that may belong to whoever set the site up originally.

A domain address that belongs to the club, connected for you

When a website is tied to a personal account or a domain registered in one volunteer's name, the club can lose access to it when that person leaves. Getting the domain transferred is a project in itself.

On Website and Members, the club's own domain is connected by the Daviah team. The team registers it, and the club adds one DNS record; the security certificate is issued automatically.

What this guide does not cover

This guide addresses the stale-website side of the problem: a site that exists immediately, that more than one person can update, and that reflects the club's actual records for events, news and Officers.

The other side — information scattered across messaging groups, email threads and social media platforms — is not answered here, because no part of Daviah pulls content in from those external channels or consolidates them into one place. If that is the problem causing the most pain, this guide is honest that it does not solve it.

Questions

Does the club need a web developer to get started?

No. When the organisation signs up, a website is created from a design immediately, with a front page and pages for the club's sections already in place. Pages are edited using a library of ready-made sections — no code is involved.

Can more than one person update the site?

Yes. An Administrator can invite other people to help, and anyone given the Website Editor role can edit site content without being able to see member records or financial information.

What happens to the Officers page when a role changes?

The Officers page on the public site is drawn from the officer records in the office. When a role changes in those records, the page reflects it — there is no separate update needed on the site itself.

Can someone check a page before it goes live?

Yes. Unpublished pages can be previewed through a private link before they are published, so whoever made the change can confirm it looks right first.

Where do contact form enquiries go?

Enquiries from the site's contact form land in the office, where the Administrator and officers can see them. They do not route to a personal email address.

Does Daviah help with information scattered across messaging apps and social media?

No. Daviah does not pull in or consolidate content from external messaging groups, email threads or social platforms. This guide covers the website itself, not those other channels.

Read next