Skip to content
FREN

Context

Bilingual website for an event organizer: line-up, event pages, waitlist, VIP area, gallery and partners.

Role

Front-end development, integration and deployment

Approach

  1. 1.

    The site is built locally with Vite, then the dist/ folder is uploaded through the host's file manager.

  2. 2.

    Since hosting is static, forms go through Formspree instead of a server.

  3. 3.

    October 2026: a form in the local version targeted an Express route that does not exist in production and showed “success” without checking the response. Fixed before any deployment (response check, accessible error message).

Architecture

Solid lines: in production. Dashed: planned or inactive.

Ivoire Production — ArchitectureVisitorBrowser, FR / ENReact applicationSPA built with ViteStatic hostingdist/ uploaded by handFormspree3 formsYouTubeEmbedded videosExpress + SQLiteIn the repo, not deployed
  • Visitor : Browser, FR / EN (in production)
  • React application : SPA built with Vite (in production)
  • Static hosting : dist/ uploaded by hand (in production)
  • Formspree : 3 forms (in production)
  • YouTube : Embedded videos (in production)
  • Express + SQLite : In the repo, not deployed (planned or inactive)
  • Visitor → React application
  • Static hosting → React application
  • React application → Formspree
  • React application → YouTube
  • React application → Express + SQLite

Technology

React 19, TypeScript, Vite, Tailwind CSS 4, React Router, i18next, Motion, Formspree

Result

Source code — Private repository (client project), available on request during interviews.

Known limits

  • No automated tests yet.
  • Manual deployment: to be automated (build and upload from CI).
  • The unused Express server must be removed or actually deployed.

AI share

The starting point was generated with Google AI Studio. I then took it over and extended it (pages, bilingual content, forms, deployment). The Express server from that starting point never ran in production.