The Club Restaurant is the restaurant of the Tennis Club de la Seymaz, in Chêne-Bourg. It is open to everyone, members or not: home cooking, a weekly lunch menu at CHF 20, a large free car park, a quiet terrace by the Seymaz river. The old site ran on WordPress.
Leave WordPress without losing control: a fast site in French and English that the team updates itself, with the weekly menu up front. And booking and private hire requests that always get through.
What I put in place
- A bespoke site in French and English: home, menu, pizza to take away, a family page, terrace, events, private hire, booking.
- Static pages at the restaurant’s own host (OVH), edited by the team in Lumineth Hub, with a preview before publishing.
- The weekly menu, entered each week in the Hub, shown at the top of the home page and picked up by the club’s site.
- An events calendar, and opening hours kept in a single place.
- Booking and private hire forms relayed at the host.
- Local positioning: families, parking, the quiet of the Seymaz, a CHF 20 menu.
Leaving WordPress
I replaced the old WordPress site with a bespoke site in French and English, built with Lumineth Hub. The published pages are static files at the restaurant’s own host, OVH. The team edits text and photos in the Hub, checks the preview, then publishes.
The weekly menu, entered once
The menu changes every week, at CHF 20 for lunch. The restaurant enters it in the Hub: it appears at the top of the home page and is picked up by the Restaurant page of the club’s site. One entry, two sites. It can be prepared at the weekend to go live on Monday, and a reminder goes out by e-mail if the next week is not ready.
Opening hours and events
Opening hours are set in the Hub: standard weeks per season, public holidays, exceptional closures. The site shows them from that single source. The same hours can be sent to the restaurant’s Google listing, through Windsor.ai, with a preview before sending. The calendar lists the restaurant’s and the club’s evenings.
Requests that always get through
Booking a table or asking for private hire goes through a form on the site. A relay installed at the host sends the e-mail from the restaurant’s own server, then passes the request to the Hub. If the Hub does not answer, the e-mail still goes out and the request waits its turn.
Speaking to local families
The site puts forward what brings people to the Club: the CHF 20 weekly menu, the large free car park, the quiet by the Seymaz, the car-free space where children play. A family page gathers this for parents. Terrace, private hire, birthdays, pizza to take away: each local search has its page.
The site
The new site is meant for the address theclubgeneva.ch, in place of the old WordPress site.
Measured result
| Lighthouse, measured locally on 2 October 2026 | Score / 100 |
|---|---|
| Accessibility | 100 |
| Best practices | 100 |
| SEO | 100 |
Measured locally, on the version of the site ready to publish. Performance will be measured on the live site, at the host.
Frequently asked questions
Why leave WordPress?
For a site the team keeps alive on its own, with no plugins to update: the published pages are static at the host, and editing happens in Lumineth Hub, with a preview before publishing.
Who updates the weekly menu?
The restaurant team, in the Hub. The menu appears on the restaurant’s site and on the club’s, with no second entry.
What happens if the Hub is unavailable?
The site stays online: its pages are at the host. So do the forms: the e-mail leaves from the restaurant’s server, and the request reaches the Hub as soon as it answers.
What are the measured results?
100 in accessibility, 100 in best practices and 100 in SEO with Lighthouse, measured locally on 2 October 2026, before going live.
A comparable case on your side?
Tell me what costs you time; I get back to you within 24 business hours with a first read, no obligation.