/
Plaza de Vogel

Family restaurant & cafetaria · Hengstdijk, NL

Same site. Now in code.

Our 2025 site for the venue, moved page for page off a rented page builder into code, in three languages, with four forms that reach the inbox.

Plaza de Vogel already had the site it wanted. We had designed it. The job was to move it, page for page, off a rented page builder and into code.

Plaza de Vogel is the family restaurant and cafetaria on recreation park De Vogel in Hengstdijk, near Hulst: a restaurant, a cafetaria and an indoor playground under one roof, with the covered pool and the petting zoo a few steps away. The site has spoken Dutch, English and German since its first version. In 2025 we designed and built that site on a page builder. In spring 2026 we rebuilt it as code: the same seventeen pages, the same three languages, one content system for the menu and the hours, and four forms that mail the venue directly. Nothing for the team or the guests to relearn. What changed sits underneath: the site no longer depends on a builder subscription, and its findability, its forms and its content are ours to keep in order.

Specs

Disciplines

Design (2025), the move into code, content system, forms, findability

Languages

Dutch, English, German

Size

17 pages, 51 addresses, 4 forms

Period

2025 to 2026, in care

Context

What had to hold

A page-for-page move has one rule: the visitor notices nothing, and the venue gains everything underneath.

Nothing to relearn.

The venue and its guests knew the site. Every page, every menu line and every button had to land in the same place, or the move would cost the team the familiarity it had already paid for.

Three languages, one truth.

Dutch, English and German had to stay complete after the move. A dish renamed in Dutch has to change in English and German too, without three separate edits.

A menu that changes by season.

Seventy-five dishes in eight categories, plus party packages, opening hours per venue and vacancies. The venue changes them, and a change must never wait for a developer.

Forms that actually arrive.

A kids-party booking or a group quote is real money for the venue. A form that thanks the visitor while the message never left is worse than no form at all.

Execution

What we did

Nine days to port every page, then a season of care: languages, content, forms, findability.

1

Ported, page for page

Between 30 March and 8 April 2026 every page moved from the page builder into code, with the old site's own export as the spec. Seventeen pages, same layout, same words, same buttons.

2

Three languages kept whole

Dutch at the root, English and German alongside, 51 addresses in the sitemap. A translation pass on 12 April 2026 closed every gap between the three, down to the form labels and the confirmation emails.

3

Content in one system

The menu (75 dishes in eight categories, counted on 7 September 2026), four party packages, opening hours for restaurant, kitchen, cafetaria and pool, reviews and vacancies live in one content system. A dish is one entry carrying its Dutch, English and German name and description. A vacancy set to inactive disappears from every page and every language at once.

4

Four forms, straight to the inbox

Contact, group quote, kids-party booking and job application each mail the venue and send the visitor a confirmation. The party form carries the package, the date, arrival and eating time, number of children, extras and the cake wish, so the team reads a booking, not a question.

5

Live status, local time

The bar at the top shows whether the restaurant and the cafetaria are open right now, computed in Amsterdam time, and a dedicated hours page lists all four venues week by week. The agenda carries the summer programme.

6

Findable, and proven

On 31 July 2026 an audit scored the site 72 of 100: AI assistants were being turned away at the door by a setting nobody had chosen. The same day all eleven checks passed at 100: assistants welcomed, a plain summary for them to read, titles fixed, the FAQ in the form they read, the address corrected.

7

Checked after a summer live

On 2 September 2026 the four forms were tested end to end: the recipient corrected to the venue's own address, two test messages delivered, and a refused send now shows the visitor an error instead of a thank-you.

Roadmap

In care

A live site is work that continues. Three things run, one is planned.

Currently Optimizing

Forms watched

Every send passes through one door that checks the mail service's answer. A refused message answers with an error, never with a thank-you page for mail that never left.

Findability held at 100

Any change to what assistants and search engines read from the site is followed by a re-audit against the live address, with the score and the date recorded.

Content edits on request

Menu, hours, packages and vacancies change in the content system. The June 2026 round restructured the navigation, split food from drinks and added the hours page.

The Backlog

A first measured season

Analytics run behind consent, so clicks to reserve and to order are counted honestly. The next round gets planned from a full season of those numbers, not from guesses.

"We designed their first site, so we knew every corner of it. Moving it into code changed nothing the guests see and everything underneath: three languages we keep whole, a menu the team changes in one place, and forms that land where they should."

Vonzie Studio

Want a site that gets better every quarter too?

Start the conversation.

Page-for-page moveThree languagesOne content systemFour formsFindability 100/100In care