Itinera — System Overview

RepoWiki root page · Team 2 Conference Case Study — Global Luxury Travel & Trip Planning Platform

What Is Itinera

Itinera is an end-to-end luxury travel orchestration platform built as a fullstack monorepo for the Team 2 conference case study. It combines:

A Laravel REST API (fullstack/Backend) with 237 registered routes covering auth, catalog, trips, commerce, chat, and system services.

A vanilla JavaScript web app (fullstack/Frontend) with a boarding-pass aesthetic, ~35 static HTML pages, and zero build step for the public site.

Payments via PayMob (hosted checkout + HMAC-verified webhooks).

AI features via Groq LLM (itinerary generation, review, enhancement, concierge) with per-user quota tracking.

Executive reporting via DomPDF / OpenSpout with queued generation.

Live weather via Open-Meteo, cached in Redis.

Section sources: README.md

Monorepo Layout

Team2-Conference-Project/
├── fullstack/
│   ├── Backend/      # Laravel API (PHP, JWT, MySQL, Redis, PayMob, Groq)
│   └── Frontend/     # Vanilla JS app (HTML5, CSS3, GSAP, no framework)
├── database/         # Root-level auxiliary DB assets
├── docs/             # Project-level documents
├── tasks/            # Sprint/task notes
├── .github/workflows # CI (Pint lint + PHPUnit)
├── Dockerfile        # Dual-role image: SERVICE_ROLE=frontend|backend
└── railway.json      # Railway deployment descriptor

The single root Dockerfile builds either a nginx static frontend or a php-fpm + nginx + supervisor backend depending on the SERVICE_ROLE build argument — one repo, two deployable Railway services.

Section sources: README.md, Dockerfile, railway.json

Core Capability Map

Domain	Backend module	Highlights
Account	`app/Http/Controllers/Account`	JWT auth, refresh rotation, email verification, social login (Google/Facebook), admin user management
Catalog	`app/Http/Controllers/Catalog`	Countries, cities, destinations, hotels, flights, restaurants, attractions, stats; fixture seeding
Trips	`app/Http/Controllers/Trips`	CRUD, itinerary items, attach/detach, fork, AI generate/review/enhance, maps, reviews
Commerce	`app/Http/Controllers/Commerce`	Plans/subscriptions, checkout strategies, PayMob gateway + webhook, agency marketplace
Chat	`app/Http/Controllers/Chat`	Conversations + messages between users
System	`app/Http/Controllers/System`	Weather, reports (PDF/XLSX), settings, surveys, contact/newsletter, flags, notifications, dashboard

Section sources: fullstack/Backend/routes/api.php

System Context Diagram

Diagram sources: routes/api.php, composer.json, config/services.php

Key Numbers

Metric	Value	Source
API routes	237	`rg -c "Route::" routes/api.php`
Migrations	44 files	`database/migrations`
Seeders	34 classes + JSON fixtures	`database/seeders`
Feature/unit tests	50+ test classes	`tests/Feature`, `tests/Unit`
Frontend pages	~35 HTML pages (+ admin/, agency/, auth/)	`fullstack/Frontend`
Frontend JS modules	33 files under `js/`	`fullstack/Frontend/js`

Section sources: repository tree inspection, 2026-08-23 @ commit 0c14fa54.

Where To Go Next

New to setup → Getting Started Guide

How layers fit together → Architecture Overview

Stack versions & rationale → Technology Stack

Service internals → Backend Services

UI structure → Frontend Application

Deployment & CI → Infrastructure

Endpoint catalogue → API Reference

Itinera — System Overview

Table of Contents#

What Is Itinera#

Monorepo Layout#

Core Capability Map#

System Context Diagram#

Key Numbers#