Create one factual event sheet
Start with the facts that must remain consistent: title, date, time zone, address, access information and the route for questions or booking. Give the sheet an owner. Use it to prepare both language versions rather than translating an old page from memory.
Separate confirmed facts from details still being arranged. Do not publish a convenient guess for a start time or accessibility feature. A shorter accurate page is more useful than a complete-looking page that sends visitors to the wrong place.
Make language switching predictable
Give each version its own clear address and link directly to the equivalent page in the other language. A language switch should not drop someone onto a homepage where they have to find the event again. Keep essential navigation labels understandable.
Set the page language in the HTML and mark passages in another language when needed. Use text for practical details instead of relying on a bilingual image. W3C’s page-language guidance explains how language information supports browsers and assistive technology.
Correct both versions together
When a venue or time changes, update the factual sheet and both published pages. Check the visible details and the destination of any booking link. If a notice is prominent in one language, make sure the corresponding notice appears in the other.
After the event, decide whether the page should become an archive or be removed with a useful replacement route. Leaving an expired booking link active can create confusion long after the event itself is over.
Keep in mind
- Use a shared factual sheet
- Link equivalent language pages
- Publish practical details as text
- Update both versions after changes