A site in four languages for a German security and facility-management platform.
- Client
- Wallenwein Administration & Development, Stuttgart
- The product
- A digital guard tour system, in use since 2003
- What I did
- The public site, in four languages, built to their server
- 4languages: German, English, Spanish and FrenchChecked on the live site, 13 October 2026
- 0requests to other servers before the visitor consentsChecked on the live site, 13 October 2026
- 0Node servers needed: the site is plain files on ApacheFrom the build
01The brief
FM24 is a guard tour and facility-management platform. Since 2003 it has helped security companies, public authorities and corporations document and control safety-critical work.
Its public site needed more than German, and it had to run on the company’s own servers: a legacy Apache stack with no Node runtime. The work goes on, in direct partnership with their team: page by page, the site is being modernized, made more accessible and readied for international markets.
02What I built
Four languages from one build
German, English, Spanish and French are generated at build time, and the site greets each visitor in their browser’s language.
Plain files on their own server
The finished site is exported as prerendered files and copied onto the existing Apache server. No new hosting, and nothing extra to run.
Consent before anything loads
reCAPTCHA and embedded video wait for the visitor’s opt-in. Until then nothing is sent to anyone else, and the form says plainly why its spam check is off.
On a phone, 390 pixels wide.
03Under the hood
Next.js · Static export · Build-time i18n · Legacy Apache
- No runtime to host
- The client’s servers have no Node, so the whole site is prerendered at build time and served as files.
- Language on arrival
- Translations are built in, not fetched, and the browser’s language picks the first page a visitor sees.
- A consent gate that holds
- Third-party scripts load only after opt-in, in line with the GDPR.
04In their words
“He doesn’t simply complete assigned work—he takes the time to understand the underlying architecture, asks the right questions, identifies potential improvements, and contributes valuable ideas of his own.”