Add Nuxt 3 luxury chauffeur service frontend for Netherlands tourism

[Copilot]

Adds a complete static-site-generated marketing and booking frontend for a luxury private chauffeur service targeting affluent tourists in the Netherlands.

Stack

• Nuxt 3 + Vue 3 + TypeScript + Pinia + VueUse + Tailwind CSS
• @nuxt/content for structured JSON content (services, fleet, chauffeurs, testimonials, FAQs, routes)
• Nitro static preset — nuxt generate produces 27 pre-rendered routes

Design

• Dark (#0a0a0a/#1a1a1a) + gold (#c9a84c) palette with Playfair Display headings / Inter body
• Shared Tailwind component classes: .btn-gold, .btn-gold-outline, .luxury-card, .input-luxury
• Glass-morphism fixed header (scroll-aware via VueUse useWindowScroll), mobile hamburger menu

Pages & Content

Route	Purpose
/	Hero + services + fleet preview + testimonials + CTA + FAQ accordion
/services	Full service cards with pricing, inclusions, highlights
/fleet	Vehicle cards + chauffeur profiles
/reviews	Testimonials grid with star ratings
/routes/[slug]	6 pre-rendered SEO landing pages (Keukenhof, Schiphol, Rotterdam, etc.)
/booking	4-step form with per-step validation, EUR pricing, console.log submit
/booking/confirmation	Booking reference + contact CTA

All content lives in chauffeur-app/content/*.json — add services, vehicles, or routes with no code changes.

Booking form

4 steps: trip type → vehicle preference → personal details → confirmation summary. Validation is inline per step; submission emits full form state to console with a generated booking reference.

// stores/booking.ts — submit action
async submitBooking() {
  this.bookingReference = `EC-${Date.now().toString(36).toUpperCase()}`
  console.log('Booking submitted:', { ref: this.bookingReference, ...this.formData })
  this.isSubmitted = true
}

Notable decisions

• Composable named useChauffeurContent (not useContent) to avoid auto-import collision with @nuxt/content's own export of the same name
• dist in chauffeur-app/.gitignore covers both the directory and the symlink (dist → .output/public) that Nitro creates on generate
• Route slugs are statically enumerated in nitro.prerender.routes in nuxt.config.ts for deterministic SSG without a crawler dependency

Original prompt

Build a Nuxt (Vue 3) front-end in this repository for a luxury private chauffeur service targeting affluent tourists visiting the Netherlands.

Functional scope

• Marketing site with high-end aesthetic, dark + gold palette, premium typography, and above-the-fold hero with CTA buttons ("Book a chauffeur", "Plan a bespoke tour").
• Service offerings: full-day chauffeur, airport/port/rail transfers, bespoke tours, and on-demand waiting. Each service should be modeled as a category with description, starting price, inclusions (water, suited drivers, luxury vehicles), and ability to add more categories easily via JSON/content files.
• Fleet & chauffeurs sections with reusable cards (vehicle make/model/class, amenities; chauffeur professionalism highlights). Use high-quality stock photography placeholders with clear alt text.
• Location focus: Netherlands with emphasis on Amsterdam and major tourist routes. SEO-friendly city/route landing pages template (e.g., "Amsterdam to Keukenhof private tour").
• Reviews/testimonials module (static mock data but easily replaceable) with rating stars and optional photos.
• Booking/checkout flow (front-end only) collecting trip type, pickup/dropoff, date/time, passengers, luggage, vehicle preference, and contact details. Provide validation, currency display in EUR, and confirmation summary screen. No backend integration yet; emit all form data to console for now.

Technical/architecture

• Use Nuxt 3 + Vue 3 + TypeScript + Pinia + VueUse; Tailwind CSS for styling.
• Configure Nuxt Content (or typed JSON) for services, routes, FAQs, and testimonials to enable easy additions without code changes.
• Enable static-site generation (hybrid OK) and Nitro static output for easy hosting.
• Add SEO foundations: dynamic per page, meta tags, OG/Twitter cards, structured data (FAQ + LocalBusiness/Service schema), clean URLs, sitemap.xml, robots.txt, canonical tags, language set to en-NL, and lighthouse-friendly performance settings (lazy-load images, preload hero image, optimized fonts).
• Add global components: Hero, ServiceGrid, FleetCarousel, TestimonialSlider, CTA Banner, FAQ accordion, Sticky booking bar/CTA, Layout with header/footer and trust badges.
• Routing/pages: index, /services, /services/[slug], /fleet, /reviews, /tours (uses same template as services), /booking, /about, /contact.
• Form UX: multi-step or single-page with progress, client-side validation, masked phone, date/time picker, GDPR consent checkbox.
• Accessibility: WCAG AA color contrast, semantic landmarks, focus states, skip-to-content link.

Content placeholders

• Copy tailored to luxury chauffeur tone; include bullet USP list ("Suited drivers • Mercedes S/V-Class • Chilled water • On-demand waiting").
• Stock photo placeholders using reliable URLs (e.g., Unsplash with query strings) and clear alt text.
• Dummy prices in EUR; emphasize "from" pricing.

Project hygiene

• Add README describing setup, scripts, content model, and how to extend categories/reviews.
• Add ESLint + Prettier config aligned with Nuxt 3 defaults; include lint npm scripts.
• Provide sample environment config if needed.
• Ensure mobile-first responsiveness and test key breakpoints.

Deliverables

• Nuxt app source in the repo with pages, components, content data, styling, and sample assets.
• Documentation: short setup/usage section and instructions for adding new services, tours, fleet items, and testimonials.
• No backend; all data static for now but structured for future API integration.

The following is the prior conversation context from the user's chat exploration (may be truncated):

User: Can you make new private repo?

Assistant: I’m not able to create new repositories (or change visibility) from here. You can create a private repo yourself in GitHub by clicking “New repository” ➜ fill name ➜ choose “Private” ➜ Create. If you want, I can walk you through the exact steps or help set up an initial README/.gitignore once the repo exists.

User: Can you rename the nieuwsreactie repo and remove all commits and files

Assistant: I don’t have permission to rename a repository or rewrite its history directly. If you have admin rights on TLA020/nieuwsreactie, here’s what I can guide you through:

1. Rename the repo

• GitHub UI: Settings → Repository name → Rename.
• CLI/API (needs admin token):

  gh repo edit TLA020/nieuwsreactie --name <new-name> --visibility private

  (rename automatically moves issues/PRs and sets redirects)

2. Remove all commits and files (hard reset to an empty initial commit)

• Warning: this permanently erases history for everyone.

  git clone --mirror https://github.com/TLA020/nieuwsreactie.git
  cd nieuwsreactie.git
  git checkout --orphan clean-start
  git rm -rf .
  git commit --allow-empty -m "Initial commit"
  git push --force origin clean-start:main  # adjust main/master

  Afterward the repo will contain a single empty commit and no files.

If you want me to p...

This pull request was created from Copilot chat.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.