Back
02
Client Project — Production
2025Live in production
Live Site

From zero online presence to a multilingual business platform

How I transformed a transport service from WhatsApp-based operations into a structured, self-managed digital platform serving international clients.

Quick Highlights
01

Built a full CMS with drag-and-drop content ordering and optimized media handling

02

Implemented secure authentication with role-based access control

03

Delivered multilingual content management across 4 locales

Client PlatformMultilingual CMSSEO InfrastructureProduction System
5
Problems
6
Decisions
5
Results
coreNext.js 16React 19TypeScript
backendMongoDBMongooseZodJWT Authbcrypt
featuresCloudinary (Image CDN)Sharp (Optimization)DnD Kit (Drag & Drop)Resend (Email)
systemTailwind CSS 4Framer Motion
testing
01
Context

Start with the situation before the implementation

10 signals frame the real scope before the solution appears

Problem

What needed to change

5 friction points identified before moving into execution

01

The business had no online presence and relied entirely on WhatsApp and word-of-mouth

02

Potential clients had no way to evaluate services or trust the business online

03

All content (photos, pricing, services) was scattered across messaging apps

04

No multilingual support despite serving international clients

Impact

Why it mattered to the business

5 business consequences made the problem impossible to ignore

01

The business was invisible to international clients searching online

02

Missed opportunities for partnerships with hotels, riads, and agencies

03

Content duplication and loss across multiple communication channels

04

Zero organic traffic due to lack of SEO presence

02
Solution

Move from diagnosis into deliberate decisions

6 trade-offs explain how the solution took shape

Decisions

Why these choices held up

A focused view of the structural decisions that shaped the final system.

01

Used Server Components by default for performance and scalability

02

Handled all mutations via Server Actions instead of REST APIs

03

Designed a 4-locale system with culturally adapted content

04

Implemented a singleton MongoDB connection for stability in serverless environments

03
System

Keep the architecture readable at a glance

A shorter systems view up front, with deeper engineering details available later.

Architecture

How the core pieces fit together

4 structural patterns describe the blueprint without dropping into full technical depth

01

Next.js App Router with SSR/SSG for public pages and Server Actions for admin

02

Centralized /lib layer handling db, auth, i18n, validation, SEO, and integrations

03

MongoDB Atlas for data, Cloudinary for image CDN, Resend for email handling

04

Modular content models supporting multilingual fields (EN, FR, ES, AR)

04
Results

What changed after shipping

5 measurable improvements surface the outcome without forcing a deep read

Results

What improved after launch

A concise outcome layer first, with the full set available on demand.

+

The business moved from offline-only to a fully functional online platform

+

4-language support enabled access to international customers

+

Client can now manage all content independently via admin dashboard

+

Improved credibility for B2B partnerships with hotels and agencies

What's next?

The real value was not the website itself — it was giving the business control over its digital presence and growth.

Next Project: Medical Transport SaaS Platform & Pricing EngineBack to HomepageStart a Conversation