A website for a club or association: what it needs and how much work it is

"We already have a Facebook group." And straight after that: "But who is going to keep a website updated?" Those are the two objections I hear most often from clubs and associations, and both are fair. A club has no marketing budget — what it has is a secretary doing all of this in the evening, after work. So let me go through it in order: what a club website actually needs, where things really break down (not on the website, but in member communication) and how much work is left once the site is live.

Why a Facebook group isn't enough

I am not saying Facebook is bad. For day-to-day chatter and photos from the last outing it works well. There are simply a few things it cannot do:

• Nobody finds a group they aren't already looking for. Someone typing "hiking club near me" or "how to join a rowing club" into Google lands on websites, not inside closed groups.
• Posts disappear. What you posted in March is effectively gone by June. Your statutes, your membership form and your training schedule need an address that stays put.
• An account is required. A share of the people your club would interest — often the older ones — are not on social media at all.
• The group isn't yours. Someone else decides its rules, its reach and whether it exists. Your domain and your website are yours.

A website doesn't replace Facebook, and Facebook doesn't replace a website. The site is what stays: the public face of the club, findable by people who don't know you yet.

What a club website should contain

Surprisingly little. A club site that does its job usually has:

1. Who you are and what you do — a few sentences at the top of the front page. Not the full history since founding, but what you would say to someone at a stall.
2. How to join — often the single most common reason for a visit. Conditions, the membership fee (or at least who sets it and when), a form to download and where to send it.
3. Events and news — with date, time and place. Without this section a site starts to look abandoned, however tidy everything else is.
4. A photo gallery — for clubs, almost always one of the most visited parts of the site. Images need to be resized for the web, otherwise the site crawls on a phone.
5. Club documents — statutes, minutes of the general meeting, the annual report. Members find them on their own and the secretary stops emailing attachments.
6. Contact and formal details — the full registered name, address, email, and where relevant the registration number and bank account for fees or donations.

All of this can happily live on a single page with sections. Split it up when there is genuinely more content — not the other way round. Don't build fifteen subpages you will then have to fill.

Member communication — where it really breaks down

A website handles everything that is public. What remains is everything aimed at members: the notice for the general meeting, the membership fee reminder, a change of time. In practice it goes like this — the secretary opens a spreadsheet of members, copies the addresses into their own mailbox and hits send. Two problems follow.

• Everyone can see everyone's address. Put the members in the "To" or "Cc" field and each recipient also receives a list of everybody else's email addresses. That is a disclosure of personal data nobody agreed to — data protection rules apply to clubs and associations just as they do to companies.
• Providers throttle mail like this. A few dozen addresses at once from an ordinary mailbox easily lands in the spam folder, or the server refuses to send at all.

So for Društvo naturistov K naravi, alongside the website, I also built a small desktop program called KNaravi pošta ("KNaravi mail"). It does the following:

• keeps the addresses in its own database (SQLite) on the club's computer; they can be imported from a spreadsheet or a CSV file;
• sends a separate message to each member, so no recipient ever sees anyone else's address;
• inserts a personal greeting — write the {ime} placeholder ("name" in Slovene) in the template and each member reads their own name;
• attaches files (the notice, the minutes, a payment slip);
• pauses for a few seconds between messages so the outgoing server doesn't read the batch as spam;
• also receives mail over IMAP and by default shows only messages from members in the database — adverts and cold offers stay out of sight.

The data stays on the club's own computer. That project is exactly why custom desktop software is now one of the studio's services — not as a compulsory add-on to a website, but as an option for when it turns out the real problem is somewhere else.

None of which means every club needs its own program. It does mean that "how do we reach our members?" belongs in the conversation about the website, not a year after it.

How much work it is — and who does it

Honestly: a website is not a one-off cost and it is not work-free. There are two separate things here.

What runs by itself and is paid once a year: the domain, the hosting and the SSL certificate. After launch you don't touch these.

What needs a person:

• publishing an event or a piece of news — a few minutes, provided the site was built so that this is possible at all;
• photos from an outing — usually the biggest job, because someone has to pick them and prepare them for the web;
• a once-a-year review: contacts, committee members, documents, perhaps the membership fee.

So the real question isn't how much work it is, but who does it. There are three routes:

1. Someone in the club who enjoys it. The cheapest option — for as long as that person stays. Plenty of club websites freeze on the day the secretary steps down.
2. Maintenance by whoever built the site. The club sends the text and the photos, the changes get published for them. Less freedom, but the site stays alive.
3. A mix of the two. The club posts its own news; bigger changes and anything technical go back to the developer. For most clubs this is the sensible one.

Whichever you pick, sort out two things immediately: register the domain in the club's name — not the developer's, and not the private address of a former chairperson — and write the access details down somewhere the next committee will find them. A small thing that saves a great deal of trouble when the leadership changes.

A real example: knaravi.si

The first club website I built is knaravi.si — a presentation site with a photo gallery for Društvo naturistov K naravi, a Slovenian naturist association. I wrote up the full project story separately, from the design approach built around the colours of nature to the copywriting and the ongoing updates: the knaravi.si project story (in Slovene).

Two things turned out to matter more than they sounded at the start:

• Readability before scope. The content has to work for older members too — large enough type, short paragraphs, no jargon.
• Speed of publishing before number of pages. A site where news appears the same day feels alive. A site with fifteen subpages and a two-year-old latest post does not, however good it looks.

And a third thing, the one that led to the program: the website on its own did not solve member communication. That was a separate pain and it needed a separate tool.

If you're thinking about a site for your club

Start from what the site is supposed to solve. Is the goal that new members find you? That everyone can reach the statutes and the minutes? That you stop answering the same question on the phone? The answer tells you how big the site needs to be — and whether member communication should be sorted out alongside it.

To begin with, a simple, clear and fast site you know how to update is plenty. Everything else can be added later, once it's clear you actually need it.