Example scenario
A last-minute change to a public event
An event’s start time changes, but the homepage, schedule listing and link already shared with the public can end up showing different information.
How would we approach it?
We manage the event from one record. When an editor publishes the change, both the schedule and event page update, and previously saved links continue to work.
Give visitors a reliable public record
A visitor may be checking a date, reading a published statement or looking for a biography to cite. A journalist should be able to locate the current biography, approved photographs and press contact without searching through several social feeds. We organise those routes around the material you plan to publish and give important records an address that can be referenced later.
Each entry can carry the relevant date, status and contact details. For example, when the venue changes for an event, editors can update the existing page and keep the link already shared publicly. For cancellation notices, the page can show the current status and when it was updated.
Keep the publisher and official services clear
An officeholder's personal information site and an official municipal services site have different publishers and responsibilities. The header, footer and contact page identify who publishes the personal site. Links to official services can explain the transaction and identify the municipality as the destination.
We agree which correspondence belongs with the site's editor and which should go to an official office. Public enquiries can use a published contact route appropriate to the site. Residents looking for municipal records, transactions or formal applications can reach the official service through a clearly labelled link.
Make it easy to update on a busy day
The editorial team can work with defined fields for statements, events and biographies. Where there are several editors, we scope permissions for drafting, review and publication. A handover exercise might involve publishing a statement, replacing a press photograph and updating the date on an existing event.
We also review how the public pages behave on phones and slow connections. Text alternatives for images, readable headings and properly described attachments help people use the site in different ways. If a particular date is likely to bring a large increase in visits, we discuss hosting capacity, media sizes and how rapidly staff need updates to appear.
Keep access and materials under clear ownership
Before launch, we agree who holds the domain, who approves publication and where the editable files and documents live. We document the permissions your team needs, the agreed arrangements for backups and which maintenance tasks remain with the owner. If you already have a domain and archive, we can evaluate what should carry over so existing citations still work.
Questions before you start
How will people distinguish the personal site from the institution’s official website?
The site clearly identifies its publisher, domain and contact details. It can host a biography, public schedule and press materials. Links to official services name the destination and the action available on the institution’s own site.
What should we prepare for the first release?
Start with a verified biography, cleared portraits, public contact details and any existing press material. If the schedule or statements archive is not ready, we agree who will maintain it and when it can be added.
Will an old link break if the details of an event change?
Each event can keep a stable URL. The time and venue can be updated on that page, with a visible rescheduled or cancelled status when needed. Editors can archive events or remove them from the upcoming schedule according to their permissions.
How can journalists download portraits and statements?
A single press page can provide approved portraits, a short biography and statements. Files can be labelled with their latest update, publication status and any usage note. The handover includes an example of replacing an old file.
Who controls the domain, content and administration?
Domain and hosting ownership are agreed in the proposal. Editorial approval, publishing and maintenance roles are documented at handover. The content owner confirms image usage rights and which versions of files are approved for publication.