myjourny-frontend

The public-facing MyJourny website — the marketing site for MyJourny, the travel marketplace connecting travellers with local guides for curated experiences.

Environments

Dev => https://myjourny-frontend.vercel.app Prod => https://myjourny.io

Problem

Finding an authentic, local-led travel experience is harder than it should be. Generic listing sites and map apps surface the same crowded landmarks and stale reviews, with no reliable way to tell which local guides are trustworthy, available, and worth paying. On the other side, local guides have no real marketplace: no easy way to list an experience, get discovered by the right traveller, take a booking, and actually get paid — so a lot of great local expertise never reaches the travellers who'd pay for it.

Value proposition

MyJourny connects travellers with vetted local guides for bookable, curated experiences — verified guides, integrated payments and payouts, and semantic discovery, replacing generic listings with real local expertise.

This site is MyJourny's public front door and a full product surface. Travellers discover experiences, sign up or log in, manage their profile and preferences, save wishlists, and book and pay, all against the itin API. See docs/ARCHITECTURE.md for how it fits together.

Stack

• Next.js (App Router) + TypeScript

• Tailwind CSS v4

• shadcn/ui (base-nova style, matching admin's config)

• TanStack Query for data fetching

• Vitest + React Testing Library + MSW for unit and component tests, and Playwright for E2E

Conventions

New code follows MVVM in feature folders (features/<feature>/{model,view-model,view}), and every feature ships with tests. CI and branch protection enforce this. Read CONTRIBUTING.md before opening a PR. AI agents also follow AGENTS.md.

Pull requests

• Describe the product change first. The PR template asks who is affected, what they saw before and what they see after, and how a reviewer can check it on the Vercel preview. Technical notes come second and are optional. pr-format enforces this.
• Ask for the AI review by commenting @myjourny on the PR once it's ready. The bot posts inline comments and answers replies to them. The required ai-review check turns green when no 🔴 blockers are left unresolved. Every push resets it to pending. See .github/helios/README.md.
• To merge, a PR needs ci, pr-format and ai-review green, plus approval from a code-owner team.

Other conventions: no src/ dir, the @/* import alias, npm as the package manager (Node 22, see .nvmrc), and components/providers.tsx for app-wide providers.

Getting Started

npm ci
npm run dev        # http://localhost:3000
npm run check      # lint + typecheck + tests + architecture check (run before every push)
npm run test:e2e   # Playwright (run `npx playwright install chromium` once first)

Learn More

• Next.js Documentation
• shadcn/ui Documentation
• TanStack Query Documentation