Client Delivery

Shohraty

Trilingual, RTL-first commerce and CMS platform for an Algerian marketing agency: a public site, an admin backoffice, and a versioned form-schema engine, live on the client's own infrastructure.

LiveLive, private repoTrilingual CMS and commerce platform / Mar - Sep 2026

Problem

The agency needed to run its own content, services, intake forms, careers and store without a developer in the loop — in three languages, under Algerian data protection law, and on infrastructure it owns rather than rents abroad.

Solution

A NestJS API with separate public and admin surfaces over one Prisma schema, a Refine backoffice for staff, and a Next.js public site. Service intake forms are authored by admins and frozen as immutable schema versions, so a form can change without invalidating the requests already answered against the previous shape.

Key Features

Admin-authored service intake forms: steps and fields defined in AR/FR/EN, frozen as an immutable ServiceFormVersion, and rendered as a multi-step wizard the frontend never hard-codes

Every submission records the schema version it answered, so changing a form never orphans the requests already collected against the old one

Google Sheets sync with per-row status, attempt counts and retry-with-backoff; a column-shape change spawns a new version and its own service-vN tab

Two API surfaces over one schema: open and throttled at /api/public/*, JWT cookie plus CSRF at /api/admin/*

Arabic as the default locale with RTL as the base case, and a language-aware fallback chain when a translation is missing

Algerian localisation as a constraint, not a translation: DZD pricing, wilaya and commune data, local phone validation, CCP and BaridiMob payment methods

Cookie consent gated on Algerian Law 18-07, with analytics and ad pixels loading through GTM only after the matching category is accepted

Hardening pass before launch: request timeouts, a global error boundary, on-demand revalidation, image optimisation, and accessible names on every icon-only control

Role

Lead engineer across all three repositories, from data model to deployment on the client's own VPS. I worked with the agency's team during the first month; from June onward I worked alone. Built for Nightbyte; the repositories are private.

Stack

Next.js 16React 19TypeScriptnext-intlNestJS 11Prisma 7PostgreSQLRefineTipTapTailwind CSSJWT + CSRFGoogle Sheets APISharpJestnginx

Links

shohraty.dz

System map

3 repos / 1 schema

Two client apps, two API surfaces, one schema. The violet path is the part worth asking about: an admin authors a form, the backend freezes it as an immutable version, the public wizard renders that version, and every submission is stamped with the version it answered before a retrying job mirrors it into a per-version spreadsheet tab.

Shohraty Screenshots

7 views

Shohraty Arabic homepage on desktop: right-aligned navigation, Arabic headline, and three growth statistic cards on a purple gradient. — The live Arabic homepage. Arabic is the default locale and the whole layout is right-to-left, not a mirrored afterthought.

The same Shohraty homepage in English: navigation, headline, and statistic cards all mirrored to left-to-right order. — The same page in English. Direction, navigation order and card sequence all flip from one content tree — the pair is the clearest proof the RTL work is real.

Step three of the Shohraty service request wizard showing an admin-defined text field, industry dropdown, and a three-option radio group in Arabic. — Step 3 of 8 in the service request wizard. None of these fields is in the frontend code: an admin authored them in three languages and the backend froze that definition as an immutable form version.

First step of the Shohraty request wizard with an eight-dot progress indicator and two name fields. — The wizard renders whatever the current schema version defines, including how many steps there are. The progress indicator is generated, not hard-coded.

Shohraty services page in Arabic: the page header, a search field and the first three service cards. — Services are CMS records, not routes. Each one carries its own translations, FAQ, workflow phases and request form.

Shohraty cookie consent dialog in Arabic, citing Algerian data protection law 18-07, with separate switches for analytics and marketing cookies. — Consent is gated on Algerian Law 18-07, with per-category opt-in. Analytics and ad pixels only fire through GTM once the matching category is accepted.

Shohraty Arabic homepage on a phone-sized viewport with stacked statistic cards. — The Arabic homepage at 390px. RTL has to survive every breakpoint, not just the desktop one.