# Archer

## Motion implementation and acceptance

Implement the interactions specified in the brief. The catalogue recording is a visual reference and the poster is a loading, error or reduced-motion fallback. Implement the moving scene separately from both.
- Catalogue recording (reference only): https://media.scrollhaus.ai/previews/archer.stream-b765eb16.mp4
- Poster (still fallback only): https://scrollhaus.ai/thumbs/archer.webp

For scroll-scrubbed video, use a muted inline video, wait for loaded metadata, and map section progress in both directions to the video timeline. Seek when the target changes and coalesce seeks while one is pending. For a frame sequence, draw the indexed frame to canvas as scroll progress changes. For scripted, CSS or 3D motion, recreate the triggers and transforms in the brief. Use normal playback for clips described as loops.

Test at two different scroll positions and then scroll back. Confirm the video time and visible frame change, or confirm the specified canvas, CSS or 3D state changes. If a required source fails, report its URL and the missing motion before calling the build complete.

Create a responsive React + TypeScript + Vite + Tailwind CSS website. Use small components for navigation, hero, interactive stage, content sections and footer. Put media URLs in src/lib/assets.ts and animations in cleaned-up hooks. Do not output a giant HTML file, an iframe, or a screenshot pretending to be the website.

## Design direction
Built with /frontend-design and /ui-ux-pro-max from a reference brief: closely recreate the layout and scroll choreography of a live reference site (jeskojets.com-style private-jet luxury site, explored directly via browser tools rather than a walkthrough video, which wasn't found in the project folder) using the user's own two supplied images -- a black private jet in flight and a champagne-gold-framed airplane window view -- rather than the reference's own assets or typography.

Palette and type: --ink: #0A0908; --paper: #F3F0EA; --ink-2: rgba(243,240,234,.62); --ink-3: rgba(243,240,234,.32).
Font families: Inter,ui-sans-serif,system-ui,sans-serif / Fraunces,ui-serif,serif / Fraunces,serif / Inter,sans-serif.
Font stylesheet: https://fonts.googleapis.com/css2?family=Fraunces:wght@400;500;600;700&family=Inter:wght@300;400;500;600&display=swap

## Layout and copy
“Beyond luxury.” → “Your space.Your pace.” → “Every detail,entirely yours.” → “A space of your own” → “Entirely on your schedule” → “Considered in every detail” → “Your world.Closer.” → “Here.” → “Anywhere.” → “The journey,in their words.” → “Make it extraordinary.”
Preserve that section order (for a one-screen concept, preserve that one-screen composition), real text and distinctive composition. Use the asset map below for additional labels, body copy, colors and asset roles. Do not add unrelated dashboard sections or generic filler.

## Motion and interaction
Section sequence mirrors the reference exactly: hero (jet -> window) -> Signature Aircraft (spec plate on a champagne-cream break) -> Life on Board (numbered detail rows) -> Destinations (route list) -> Perspective (From/To pair) -> Guest Perspectives (auto-scrolling testimonial marquee, honestly labelled as sample stories) -> closing CTA.
Use React refs for canvas/video/3D and effects with cleanup for listeners and animation frames. Keep scroll progress reversible and independent of React rerenders. Match the demonstrated interaction, not just its opening still.

## Exact media
Asset and content map (JSON, not HTML): https://scrollhaus.ai/build-assets/archer.json
Visual demo: https://media.scrollhaus.ai/previews/archer.stream-b765eb16.mp4
Thumbnail / loading poster: https://scrollhaus.ai/thumbs/archer.webp
- image: https://media.scrollhaus.ai/sites/archer/assets/jet.jpg
- image: https://media.scrollhaus.ai/sites/archer/assets/window.jpg

Read the JSON map before implementing; its referenceNotes contain the full design and motion details. Follow this React/TypeScript instruction when historical notes mention a different stack or standalone HTML. Keep source media at neutral saturation and contrast; do not add colour boosts. Use its exact URLs, including query strings. Resolve every asset independently; do not turn the thumbnail into the full-screen hero. Do not replace missing media with stock pictures. Report a failed URL and keep a useful loading/error state.

## Responsive behavior and finish
At 1440×900 keep the reference's text/image balance. At 390×844 stack content deliberately, use touch equivalents for hover/drag, keep faces/products uncropped, and avoid horizontal overflow. Videos that loop must be muted and playsInline; do not hide real scroll motion behind an autoplay loop. Honor reduced motion, keep keyboard access, and pause offscreen/hidden-tab rendering.

Run the production build. Check desktop and phone layouts, every supplied image/video/model, the main interaction in both directions, navigation and CTAs. Keep demo-only forms/cart UI local unless a backend is explicitly requested. Compare against the reference; report any unverified differences rather than claiming a guaranteed match.