SerhiiNadolskyi
Hire me

Auto3P · CH · 2023–2025

Auto3P: WordPress, localisation and integrations for a Swiss insurtech

Service pages, a site taken from one language to four, a branded email template and a monday.com lead flow for a Swiss insurtech.

Localisation
4languages

English, Spanish, Romanian and Turkish. Turkish got its own font, the brand font has no ş or ğ.

Auto3P (Europe) AG is a Swiss automotive-insurance technology company that works with insurers and fleets in several countries. Its site names Allianz, Generali and Zurich among its clients.

I first built service pages for it in 2023, through a partner agency. The lead of that project, by then at Auto3P, brought me back directly in 2024 as the site’s developer: four languages, new product pages and smaller jobs for the platform and the team. I had almost no server access, so every theme file reached production through the company’s R&D.

Projects

  1. 2023

    WordPress block theme service pages from Figma

    Service pages from Figma, which I built on Auto3P’s custom block theme through a partner agency.

    The pages share one «services» template in the Site Editor, and repeated sections are block patterns, so each is edited in one place. The claims-management section runs on CSS counters: an editor duplicates a block, the new step numbers itself, and text and image switch sides. For desktop I also prototyped an SVG animation for the designer to decide on.

    I handed the pages over in July 2023, and the agency lead reviewed them along the way.

    Stack: WordPress, Gutenberg, CSS, SVG

  2. 2024

    HTML email template for password reset

    A branded «Reset Your Password» email for the platform, built to look right in real mail clients, old ones too.

    I built it from the full design file for exact sizes and colours, in nested tables up to 500 px wide with inline CSS, because many mail clients ignore normal stylesheets. It has the brand font with Arial as a fallback, a smaller heading and icon on narrow phones, a slot for the user name, a note on how long the link works and a support contact. I tested it with real sends through SendGrid on a MacBook and an iPhone, and gave it to the platform team with a short note on why the CSS is inline.

    Stack: HTML, CSS

  3. 2024

    Make and monday.com integration for website leads

    The team got its website leads by email. I built a proof of concept that turns each form lead into a monday.com item through Make.

    I tried a route through Gmail first and dropped it, because it didn’t carry the fields the team needed. The Make scenario creates an item from each form submission. The first items arrived empty, and the cause was monday’s own automation, which fills the item’s content in this setup. With it in place, the items came in complete.

    In August 2024 the flow worked on one form, with a plan to extend it to three forms in all four languages, in the company’s own accounts.

    Stack: WordPress, Make, monday.com

  4. 2024–2025

    WordPress localisation and new product pages

    I took the company’s custom block theme site from English to Spanish, Romanian and Turkish and added pages for new product lines, on an AWS production behind a firewall with no FTP or server access after a server move.

    • I built the Fleet Management page from Figma, and later Auto Insurance Carriers with animations and videos from an outside design studio. The page templates came with video guides, so the designers swap those files themselves.
    • The site strings went into each new language through WPML. One native speaker per language checked them on a test copy, and I tracked it all in a sheet with a status per language.
    • The brand font had no ş or ğ, so the Turkish pages got a second font in their own stylesheet. The other languages stayed untouched.
    • I rebuilt the header menu from Figma: sticky, adaptive, with a working burger on mobile and a clearer language switcher.
    • At one point the Site Editor stopped saving on production. I reproduced it and wrote down the exact steps with a video, and the company’s R&D found a firewall rule behind it. After their change I retested the editor and the contact form.
    • Before every production change I made a full backup, and after the server move production was restored from that backup.

    The site now runs in English, Spanish, Romanian and Turkish, with the new product pages live and the insurance page live in English, Spanish and Romanian.

    Stack: WordPress, Gutenberg, WPML, JavaScript, CSS, Lottie

Contact

Have something similar?

Use the form or message me on LinkedIn.

Already working with me on Upwork? Write there.