Content editor
This is the part that means nobody needs Bo to change a phone number or swap a photo. Sign in, edit, save — the public pages update.
Storage is blocked on this address, so edits won't carry to the public
pages. Deploy the site to a web address (or run a local server) for this to work.
Who can do this? In the real build, board members and a couple of
named volunteers — through the association's own accounts, with Google sign-in in
front of it. Here it's simulated, so treat it as a demonstration of
the idea rather than a lock on a door.
Preview the site → Registration page Sponsors page About page
Save or reset
Changes apply to the public pages straight away. Reset puts the original wording back.
What this shows the board
- Nobody is locked out. Any authorised volunteer can fix the text — not one person with the password.
- No code, no developer, no waiting. Changing a headline or a photo is a form, not a job.
- It survives the person. The content lives in the association's own system, not in someone's head or inbox.
Honest limit: in this demo the images and text are stored in the
visitor's browser. The real system stores text in a database and images in object
storage, with a history of who changed what — and that is exactly why the real
version needs the association to own the accounts.