Most branch websites are built once, by whoever could, and then slowly stop being true. The calendar is last season's. The committee page names somebody who moved away. There is a PDF.
That is not a design problem. It is that the site was built to be looked at rather than used, so nobody has a reason to open it twice.
A branch site that stays alive does four things, and only the first faces the public:
The last three are what make somebody open it on a Tuesday. A site that only does the first is a poster, and posters go out of date.
Would anybody be annoyed if this were wrong? If the answer is no, the page will go out of date and nobody will notice, which means it should not exist. A dive calendar people book on is corrected within a day. A "Latest News" section is not.
If updating the boat's insurance date means emailing the one person who has the login, the date will be wrong for most of the year. Anything a club would ever change (the committee, the kit list, the calendar, the dive sites, the club's own address) belongs on the site itself, editable by the officer whose job it is.
The moment a club has to ask somebody outside it to change something true about itself, that thing starts going out of date.
Not "be responsive". Work: on one bar of signal, in the rain, in gloves, on a five-year-old Android, for somebody who has not opened it since June and does not remember a password. That last part is why per-person codes beat accounts for a club: nobody is locked out of a Saturday because they cannot remember which email they used.
Written while building FoxFace Diving, a website that runs a diving club: the calendar, the kit store, the boat and the committee's paperwork, for one price with nothing held back.