SEK·All projects ↗

2026 / digital · fullstack

Parfum House

A bilingual, WhatsApp-enabled luxury storefront.

A French/Arabic perfume catalogue with RTL support, discovery and WhatsApp ordering.

  • Next.js
  • TypeScript
  • Tailwind CSS
  • next-intl
  • Framer Motion

01 / PROBLEM STATEMENT

Why this work exists

A Moroccan luxury catalogue needs rich product discovery and bilingual presentation while keeping ordering operationally simple through WhatsApp.

Data and source material

  • Typed static product and collection records
  • French and Arabic translation dictionaries
  • Product attributes including brand, concentration, volume, notes, tags, collection, availability, and merchandising flags

02 / SOLUTION OVERVIEW

From input to usable output

Typed product data drives filters, galleries, collections and localized routes ending in WhatsApp.

  1. 01

    Navigate locale-aware French or Arabic routes

  2. 02

    Filter products by gender, brand, concentration, and price

  3. 03

    Inspect galleries and fragrance notes

  4. 04

    Move from discovery to a WhatsApp order handoff

03 / TECHNICAL ARCHITECTURE

Implemented components

Documented component map
01

Next.js App Router → locale routes → typed catalogue → responsive UI

Diagram synthesized from the pinned repository documentation; it is explanatory, not a runtime topology capture.

04 / METHODOLOGY & IMPLEMENTATION

Decisions that shape the system

  • Next.js locale routes and next-intl coordinate French/Arabic rendering and right-to-left layout.
  • Typed catalogue data drives reusable product and collection components.
  • Next.js metadata, structured product data, sitemap generation, image optimization, and lazy loading support discoverability and performance.

Implemented capabilities

  • French/Arabic
  • RTL
  • Filters
  • Collections
  • WhatsApp
  • Sitemap

05 / RESULTS & EVIDENCE

What the source supports

  • The repository documents a responsive bilingual storefront prototype with catalogue, collections, product detail, SEO, and WhatsApp integration.
  • No completed commerce backend or transaction result is claimed.

Results preserve the repository’s units, evaluation framing, and stated limitations. Missing evidence is not converted into a claim.

06 / CHALLENGES & LIMITATIONS

Where the evidence stops

  • The README explicitly instructs replacing placeholder product and collection images.
  • Ordering depends on configured WhatsApp data; there is no documented inventory or payment backend.

07 / WHAT THIS DEMONSTRATES

Engineering signal

Internationalized product design, RTL support, typed content modelling, responsive commerce UI, and an intentional lightweight order handoff.

08 / SOURCE & RELATED WORK

Trace the evidence

Audited files

README.md · src/app/ · src/components/ · src/data/