Verity App, Now in Two Languages!
Lost in translation
This one took a while. Probably longer than I expected.
Making Verity multilingual sounded simple at first: add Spanish to the app, let customers create websites in English or Spanish, maybe add a language switcher. Done.
Naturally, that was not even remotely the real job 🤓
Once you support more than one language properly, the language stops being just text on a screen. It affects routes, saved preferences, website content, booking flows, services, legal pages, SEO, publishing, previews, redirects, and about twelve other things that suddenly decide they also have an opinion.
So this turned into one of those implementations where every time I thought I had reached the end, another part of the system quietly raised its hand.
The Verity app itself is now available in English and Spanish. That meant more than translating buttons and labels. The selected language now follows the customer across the authenticated app, including dashboard routes and the saved account preference.
Then there were customer websites. A Verity site can now be published in English, Spanish, or both at the same time. Each language has its own content, while things that should remain shared, like branding and global website settings, stay shared.
The Website Editor can work with each enabled language separately. Customers can add another language, choose the default one, remove one without destroying the work they already did, and switch between languages while editing.
And when a site is multilingual, the public website gets a language switcher too. That part sounds innocent. It was not.
The switcher has to keep you on the equivalent page. Home goes to home. Privacy goes to privacy. Terms go to terms. The right language has to be used by the booking flow. Search engines need the right canonical and alternate language metadata. The sitemap has to contain the right routes. The default language has to behave properly without pretending the other language does not exist.
Appointments made things even more interesting. Services are operational data, so I did not want a separate English service and Spanish service pretending to be two different things. It is still one service. It just has different presentation in each language.
That sounds obvious when written in one sentence. It was considerably less obvious while implementing it.
The Booking Widget now follows the language of the website route, so someone booking from the Spanish site sees the booking experience in Spanish, with the correct localized service information.
And the publishing system had to change too. Verity still publishes one website as one unit. It does not treat every language as a separate site. One publication builds the complete multilingual site, including every enabled language, legal page, redirect, sitemap, and route.
That was important to me because I did not want multilingual support to become another layer of duplicated state waiting to break later.
There was a fair amount of swearing involved. A lot of checking whether one language was accidentally falling back to another. A lot of asking why something was still in English when everything around it was already in Spanish. A lot of discovering that a “small” language feature had somehow reached from the frontend all the way down into publication and service ownership.
But it is done.
Seeing Verity running in Spanish, then opening a customer site with both English and Spanish, switching between them, editing both, booking in the right language, and watching the whole thing behave like it was always designed that way was genuinely satisfying.
And this feels like more than just another feature shipped.
For me, this is one of those changes that makes Verity feel much closer to the product I actually want to build: something that can genuinely support how small businesses work, instead of quietly assuming everyone works in English.
That matters, especially for the kind of businesses Verity is meant for. A lot of independent professionals serve customers in more than one language, and they should not need separate websites, separate booking tools, or some awkward workaround just to do that properly.
So the real takeaway is not that Verity now has a language switcher.
It is that Verity can now serve more people without asking them to change the way they communicate with their customers.
That feels like a meaningful step forward.
There is still more I want to do here, but this was a big one, and I am very glad to finally be on the other side of it.
