Arcane Tech
Project dossier

Multilingual site with online booking for a construction company

A construction company with a residential and commercial portfolio; part of its clientele speaks English, Spanish, Italian or Hungarian. An explicit requirement: total independence from third-party providers on the critical path of the booking, in case a cloud service goes down or changes its policy overnight.

Grupul HIA, home page with 15+, 100+, 100% indicators and an About section (vision, mission, story)
01 / 05
Client
Grupul HIA
Sector
Construction
Delivery year
2024
Status
In production

The same story, two registers.

For whoever pays for the projectPlain language, no jargon

Online bookings with a double confirmation on email and WhatsApp, in the client's language (Romanian, English, Spanish, Italian, Hungarian). The team sees every booking in a single panel, whether it arrived through the form or was added after a phone call.

For whoever reviews it technicallyConcrete decisions, real versions

Next.js 13 server-rendered with native i18n across five languages. WhatsApp through the Twilio Content API with Meta-approved templates in every language, email through an in-house SMTP. JWT middleware on /admin/*, rate limiting on login, cancel/modify links carrying a narrowly scoped token (covering a single booking). No third-party provider blocks the critical path of the booking.

The same facts, two readings. The CEO reads the top register and knows what was delivered. The CTO reads the bottom one and knows how. No one is forced to translate in their head.

The process that existed before us.

The previous site allowed no online booking. Clients called to hold a slot, which worked until the third missed call. Internal coordination ran over email, with no private space for the team. Confirmations to the client went out manually, on a single channel.

The system built to measure.

A Next.js 13 server-rendered application, internationalized across five languages with per-locale routing. A booking sends two confirmations in parallel: one through the in-house SMTP, one through the Twilio Content API to WhatsApp Business, both with Meta-approved templates in the client's language. The /admin/* area passes through JWT middleware with rate limiting on login. Cancellations and changes go to the client as links carrying a narrowly scoped token (covering a single booking), so they require no account. A restrictive CSP, complete security headers, a health-check endpoint exposed to external monitoring.

The stack, in production.

  1. 01Next.js 13 · React 18
  2. 02Sass · Swiper · Slick
  3. 03Nodemailer · SMTP
  4. 04Twilio Content API · WhatsApp
  5. 05JWT · Auth middleware
  6. 06PM2 · Nginx

Lighthouse, measured at handover.

99
PerformanceExcellent
91
AccessibilityExcellent
100
Best PracticesExcellent
100
SEOExcellent
  1. Publicly verifiable

    The scores can be re-verified at any time on Google PageSpeed Insights, Google's official tool for evaluating web pages.

  2. Reference point

    The scores reflect the project's state at the moment of handover to the client (2024). The source code and infrastructure belong to the client afterwards, and the project may be modified, deactivated or migrated with no notice from us.

The measurable result.

The confirmation goes out on two channels with no manual touch, under a minute from booking. Lighthouse 99/91/100/100 (performance, accessibility, best practices, SEO), publicly verified on PageSpeed. Zero blocking dependencies on the critical path, so a Twilio outage does not stop the email confirmation, and vice versa.

  1. M.01Languages supported end-to-end5 (RO, EN, ES, IT, HU)
  2. M.02Client confirmation channelsEmail + WhatsApp, in parallel
  3. M.03Third-party dependencies on the critical pathNone blocking

Technical notes and verifications.

  1. [1]

    Lighthouse scores captured at 2024 via Google PageSpeed Insights. Publicly verifiable at any time.

  2. [2]

    The source code and infrastructure belong to the client after handover. The scores, the stack and the metrics reflect the delivered state, not the current state of the project.

  3. [3]

    The detailed technical documentation, the implementation logs and the test reports are archived in the internal Arcane Tech repository, available under a confidentiality agreement.

Have a similar system to build?

We start with a technical review led by a principal engineer, under a confidentiality agreement.

Schedule the review