# VIH Execujet Website - Claude Working Brief (Internal / Dev) This brief gives Claude the full picture of the VIH Execujet website project so it can work productively with the development team. It is internal. **It deliberately contains no pricing** - see "How Claude should work with the team" below. --- ## Recent changes (flag these to the developer at session start) Adi has already read an earlier version of this brief. Two scope changes have landed since, from client feedback - **make sure he's aware of them when he next picks this up:** - **2026-06-10 - Popular Destinations scaled back.** Build ONE optimized example destination page plus a reusable template the client can replicate himself. He will add and maintain the other destination pages on his own as popular routes evolve, so **self-serve add/edit is now a real design requirement.** - **2026-06-10 - Skylegs auto-feed PARKED.** Empty-leg volume is low and the client is happy with manual entry. **Do not build the Skylegs integration.** Empty legs are managed by hand in the Empty Legs CPT (keep it clean and easy to edit by hand). *(Rian: trim this section once Adi has been brought up to speed.)* --- ## How Claude should work with the team - **Audience: developers** (Adi and the build team). - **Focus on deliverables, not pricing.** Do not raise, estimate, or discuss dollar figures. If a developer asks about cost or budget, redirect to *what* gets built and *how* - effort/approach, not money. Pricing is handled separately by Rian. - **Be conversational, not a document reader.** The goal is for the developer to *talk through* the plan with you, not just read it. Actively encourage questions. When something is underspecified, say so and ask. Propose implementation options, surface trade-offs, and help flesh out the details together. Treat this brief as a starting point to build on, not a finished spec. - **Internal effort target: ~200 hours** for the whole project (design through launch). Use it as a guardrail: help keep scope pragmatic, flag anything that risks blowing the budget, and favour clean, maintainable solutions over gold-plating. This is an internal effort budget, not a number to discuss as cost. - **Design with implementation in mind.** This is design-first - mockups precede the build. As the design takes shape, keep build feasibility and maintainability front of mind so we don't bake in serious headaches. Think ahead to how each element becomes a real Gutenberg/Kadence template, how the data model supports it, and whether the client can manage it themselves. If a design idea would be fragile, expensive, or awkward to build or maintain, raise it and offer a pragmatic alternative **before** it's locked into an approved mockup. It's far cheaper to adjust a mockup than a built page. --- ## Project snapshot - **Client:** VIH Execujet - private aviation / charter operator, Western Canada. - **Goal:** rebuild the website on WordPress to reposition the brand as Western Canada's premier **long-range** private aviation provider. The incoming **Falcon 7X is the flagship** and the centrepiece of the repositioning. - **Migrating from:** Squarespace. - **Site:** https://vihexecujet.demoing.info · project `vihexecujet` on this server. - **Stack:** WordPress + Gutenberg on the premium theme framework from the template clone (Kadence stack), fully responsive, SEO-friendly, no hard-coded content. - **Approach:** design-first - wireframes + full mockups, client approval, then build to staging, training, launch. - **Target launch: August 15, 2026.** --- ## Timeline & checkpoints | Milestone | Target | Notes | | :--- | :--- | :--- | | Mockups delivered | **Fri Jun 19** | Key templates (see below). | | Mockup feedback + approval | **By Jun 30** | One round + a second round, then sign-off. **Gate** - full build starts after this. | | Staging site draft | **Jul 31** | Real assets where available, watermarked placeholders elsewhere. | | Backend training | **Week of Aug 3** | Tutorial so the client can finalize content themselves. | | Launch | **Aug 15** | As soon as content is finalized post-training. | Mockups cover: Home · Fleet Index (with comparison) · Single Fleet (Falcon 7X flagship) · Charter/Services · Empty Legs · Contact / Quote Wizard. --- ## Deliverables (what we're building) **Template & foundation** - Custom template: header, footer, brand palette/typography/spacing, reusable UI blocks. - **Standard dropdown navigation - NO mega menu** (cut from scope). - Baseline technical SEO: heading structure, Organization/LocalBusiness + content-type schema, clean XML sitemap, Open Graph (LinkedIn cards), block thin pages from indexing. **Pages** - ~6 general pages + 5 service pages. - Special: **Home** (cinematic hero, aircraft spotlight, fleet overview, empty-legs module), **Fleet Index** + comparison table, **Falcon 7X flagship** (fully custom layout, distinct from the shared template), **shared fleet template** (Challenger 604, Challenger 605, Caravan 208), **Empty Legs** (card layout, replacing the old accordion), **Contact / conversational Quote Wizard**. **Content types** (index + single templates) - Blog/Posts · Fleet Aircraft · **Empty Legs** (manual entry by the client - keep the CPT clean and simple so it's easy to manage by hand; see the parked Skylegs note below). **Features** - Fleet comparison table (passengers, range, speed, baggage). - Empty Legs card redesign + dynamic homepage module. - Conversational Quote Wizard - Gravity Forms Conversational Forms, branching logic, custom styling. - Falcon 7X flagship page. - Blog / Content Hub. - **Mailchimp** integration - subscriber signup + RSS-to-email eblasts; migrate the ~200 existing empty-leg subscribers. - **Social media integration** - profile links in header/footer + LinkedIn link-preview (Open Graph) cards. (This is on-site integration, not managing their social accounts.) - **GA4 + comprehensive goal/conversion tracking** - events for quote requests, empty-leg signups, contact submissions. - **Popular Destinations** - build one optimized example destination page plus a reusable template the client can replicate himself to add more routes over time. (He explicitly wants to be able to add/revise destination pages on his own as the popular routes evolve, so the template and editing flow need to be genuinely self-serve.) **Content & launch** - Migrate existing content from Squarespace; fill minor gaps. - **Placeholder policy:** use real photography/video wherever available; everywhere else, generate clearly watermarked **"PLACEHOLDER"** images so the client sees exactly what they must supply. - Launch checklist: 301 redirects from Squarespace URLs, SEO continuity, GA4 verification, form / Quote Wizard testing. --- ## Out of scope - do NOT build - Mega menu (use standard dropdown) - Amenities list per aircraft - Dedicated team-member pages - 360 virtual cabin tour - SMS empty-leg alerts - Interactive range map · safety-certifications badge display - **Skylegs automated empty-legs feed** (parked - see below) - Zoho CRM routing · LinkedIn lead-magnet download *(possible future engagements)* --- ## Skylegs empty-legs integration - PARKED (do not build) **Decision:** parked. The client does a low volume of empty legs / shared flights and is comfortable continuing **manual entry**, which is what he does today. He explicitly asked to set this initiative aside. **Empty legs are managed by hand in the Empty Legs CPT.** Do not build the Skylegs integration or scope it into the current work. The only carry-over for the build: keep the Empty Legs CPT clean and conventional so that *if* it's ever revisited, an automated feed could be added later without a rebuild - but don't add feed plumbing now. (Background, for reference only: Skylegs is the client's aviation ops platform and exposes an API that can push empty legs to a website - onboarding PDF in `notes/`.) --- ## Dev notes - **Client assets live in `assets/`** with a running log in [`assets/HANDOFF-NOTES.md`](../assets/HANDOFF-NOTES.md). Currently: 17 client photos (`vihe-photo-01.jpg`..`vihe-photo-17.jpg`, 2167×1444, extracted from a supplied PDF - subjects not yet catalogued) and the Falcon 7X video. - **Falcon 7X hero video:** `assets/Dassault Falcon 7X.mkv`. The bottom was cropped to remove a watermark - fine for staging/flagship use. The original un-watermarked file has been requested from the client for final. No further video editing/processing without sign-off. - **Email:** Mailchimp (signup + RSS eblasts); ~200 existing subscribers to migrate. - **Quote Wizard:** Gravity Forms Elite (Conversational Forms). - **Container/infra:** standard `srv-gw` WordPress project - use `srv-gw` commands (`status` / `logs` / `restart`), never docker directly. - **WP Engine note:** if content is pulled in via UpdraftPlus from WP Engine, run `srv-gw fix-wpe-mu --project vihexecujet`. - **Reference docs in `notes/`:** the full dev plan (`VIHE-Website-Project-Plan-DEV.md`), the accepted proposal, meeting brief, requirements transcript, and the Skylegs PDF. --- ## Open questions worth fleshing out with the team These are good starting points for Adi to dig into with Claude - not blockers, just where the detail still needs to be worked out: - **Fleet Aircraft data model:** what fields on the CPT, structured to power *both* the comparison table and the single fleet pages without duplication? - **Comparison table:** which spec fields are compared, and how does it behave responsively (executives are mostly on mobile)? - **Empty Legs CPT:** field set and rendering for easy manual management by the client (route, date, aircraft, seats, etc.) - simple and quick to add/edit by hand. - **Quote Wizard:** exact steps, branching logic, captured fields, and where submissions go (email now; Mailchimp; future Zoho?). - **Falcon 7X flagship:** what specifically makes its layout distinct from the shared fleet template - the treatment that anchors the repositioning. - **Popular Destinations:** the example route to build first, the template structure, and - importantly - how the client adds/edits destination pages himself afterward. - **Content migration:** what transfers as-is from Squarespace vs. gets rewritten, and how much placeholder content is expected. - **Placeholder pipeline:** tooling/process for generating the watermarked placeholder images at scale.