Architecture

• Frontend (public site): Next.js 15 + TypeScript, Tailwind, Radix, GSAP, i18n, logging. Turnit Ride integration, information pages, support, fares, info‑mobility.
• Backend (API): Node.js + Express, Mongoose (MongoDB), JWT, Zod, Pino, Helmet, CORS, rate‑limiting, media uploads to Cloudinary. Exposes CRUD for content (news, offers, blocks) and RFI integrations.
• Backoffice (admin): Next.js 15, React Hook Form + Zod, MDX editor, theming, toasts. Content management and publishing with typed validations and moderation/update flows.

Frontend (live website)

• Booking: Turnit Ride widget integration with smooth handoff; parameters like origin, destination, date, adults to compose trips.
• Train search (RFI): search by train number, station → station, and real‑time status. Robust requests (error/timeout handling) and light caching for repeated queries (GET ...?station=...&date=...).
• UX & performance: responsive layout, accessible components, measured animations (GSAP), lazy media and attention to LCP/CLS. Consistent per‑locale metadata.

Backend (API)

• Data & content: v1 endpoints (/api/v1/...) for news, offers, content-blocks, infomobility, app-login, rfi.
• Security: Helmet, CORS, rate limiting, JWT with Authorization: Bearer <token>.
• Validation: zod schemas for consistent inputs and clear error messages.
• Uploads: multer + Cloudinary for media; consistent naming and public URLs.
• Logging: Pino with structured, rotating logs; pretty in development.

Backoffice (admin)

• Rich editing: MDX editor for structured content and flexible copy (e.g., news, info blocks).
• Typed forms: useForm({ resolver: zodResolver(schema) }) for robust client‑side validation.
• Operations: create/update content with unobtrusive feedback (toasts) and accessible UI. Authentication to backend via JWT sessions.

Role and collaboration

I built all three parts:

• Frontend: Turnit Ride integration, the train search based on RFI APIs, public UX, i18n and performance.
• Backend: API design (content + RFI integrations), security, validations, and uploads.
• Backoffice: admin dashboard with editor, typed forms, and publishing workflows.

Technical highlights

• Frontend: Next.js 15 + TypeScript, Tailwind + Radix, GSAP, i18n, Turnit Ride widget.
• RFI: station/number searches and real‑time status with resilient networking.
• Backend: Node/Express, MongoDB (Mongoose), JWT, Zod, Pino, Helmet, CORS, rate‑limiting.
• Media: uploads via multer and Cloudinary storage.
• Admin: Next.js, RHF + Zod, MDX editor, theming, toasts.
• Quality: consistent validation, structured logging, accessible UX, and performance tuning.