A little look around

Start a Project
All insights
Inside the Studio

Behind three languages: the button is part of the translation too

How we approach English, French and Dutch across the website, from tone and page links to the confirmation email at the end.

A hand holding a stack of books against a plain wall

A translation is not finished when every English sentence has a French or Dutch equivalent. It is finished when the page makes sense in that language and the next step works too.

On the RDBK site, that meant treating language as part of the product rather than a separate text file delivered at the end.

We kept the intent, changed the wording

Our English voice is direct, warm and lightly playful. Reproducing it word for word can make another language sound strangely stiff. We look for a natural way to carry the same intention instead.

A heading still needs to introduce the section. A button still needs to explain its action. A small joke is optional if it does not travel well. The reader should not have to reconstruct the English sentence to understand it.

We followed the journey beyond the page

Navigation, translated URLs, form labels, errors and emails all belong to the experience. So do Rico’s suggested messages. A French suggestion should send a French message, not quietly switch the conversation to English.

Newsletter signup follows the page language too. Asking visitors to choose the same language again adds a decision they have already made.

We let the words test the layout

Dutch labels can need more room than their English counterparts. French punctuation and sentence rhythm change the balance of a heading. We check cards, buttons and mobile menus with the actual text, rather than assuming the shortest version represents every language.

The answer is not always smaller type. Sometimes the container needs to grow, the line break needs freedom or the wording needs a better edit.

We made the source editable

The content tools let the studio edit English as well as translations and exchange content through JSON. That keeps the original copy open to improvement instead of treating it as untouchable.

Every change still needs a view of the connected versions. The useful question is not only “did we translate this?” but “does this journey still feel coherent?”

For planning your own project, start with our bilingual website checklist. The small details are where language stops feeling like a setting and starts feeling like the website.

More from the studio

Enough reading?

Let's make something
worth talking about.

If one of these ideas sparked a thought about your own website, we'd love to hear it.

Your choice

Choose which optional cookies you are comfortable with. You can change this whenever you like.

Strictly Necessary

Required to remember your preferences on this website.

Always active
Marketing

Not in use. We do not run advertising-tracking cookies on this website.

Not in use
Read the Cookie Policy

Rico

Your RDBK studio assistant

Rico waving hello

A little help, right here.

Hi, I’m Rico.

Good questions are my thing.
What would you like to know?

AI assistant · Enter to send

AI chat via Google Gemini. Please don’t share sensitive details. Privacy Policy