Build a Avada alternative

# Production website build brief

Act as a product designer, information architect, senior frontend engineer, accessibility specialist, and evidence auditor. Build an original multipurpose business and commerce website. The result must solve this outcome: Build a complete business site from a governed page system instead of accumulating unrelated blocks. Build the complete independent capability alternative.

## Operating mode
Deliver the complete production architecture.

## Inputs to request before building
- Organization, product, or operator name
- Primary audience and the decision they need to make
- Verified offers, prices, availability, policies, locations, and contact routes
- Owned brand assets, photography, product media, and content rights
- Required services, current stack, deployment target, and maintenance owner
- One primary conversion action and its measurable completion receipt

Do not fill a missing business fact with plausible copy. Render a visible Needs evidence state and identify the owner who must provide it.

## Required page system
1. Decision-led home
2. Offer architecture
3. Proof and case studies
4. Commerce or booking path
5. Support and policies

Give every route one clear job, one H1, an answer-first introduction, and a distinct information hierarchy. Shared components may establish consistency, but adjacent routes must not become copy swaps.

## Interaction system
- Reusable section patterns
- Clear page hierarchy
- Accessible responsive controls
- Content-state consistency

Use semantic controls, visible keyboard focus, 44px mobile targets, descriptive names, stable loading states, useful empty states, and explicit error recovery. Honor reduced-motion preferences. Do not bind continuous React state to scroll or pointer position. At 390px, the document must have zero horizontal overflow.

## Evidence and trust system
- Verified operating facts
- Labeled estimates
- Source-backed proof
- Explicit missing inputs

Separate observed, measured, estimated, benchmark, and planning values. Show source, date, method, and confidence near numerical claims. Do not invent reviews, customer logos, certifications, urgency, inventory, revenue, performance, or legal compliance.

## Conversion system
- One primary offer
- Qualified handoff
- Receipt-backed completion state

The primary action must remain consistent across hero, navigation, relevant content, and completion state. Server-owned products and prices override client input. External services are adapters, not the source of truth. Sensitive actions require an explicit human approval boundary.

## Visual direction
Create an original composition from the outcome and content model. Do not imitate a named theme, marketplace demo, screenshot, logo, codebase, page arrangement, typography pairing, animation sequence, or visual signature. Use one coherent theme, one restrained accent, strong typographic hierarchy, owned media, explicit image dimensions, and a responsive grid. Avoid generic gradient glow, decorative dashboards, fake browser chrome, and motion that competes with the primary task.

## Engineering contract
- Use a production-ready React and Next.js architecture with Server Components by default.
- Isolate interactive leaves and keep secrets, entitlements, pricing, and writes on the server.
- Add typed content models, validation, error boundaries, and deterministic identifiers.
- Provide unique metadata, canonical URL, Open Graph fields, CreativeWork or relevant truthful JSON-LD, sitemap membership, a Markdown alternate, and accessible RSS/API discovery.
- Budget for LCP below 2.5 seconds, INP below 200 milliseconds, and CLS below 0.1.
- Add analytics events for view, primary action, form completion, and outcome receipt without collecting unnecessary personal data.

## Deliverables
Return the route map, component map, typed data contracts, complete source files, setup commands, test commands, content checklist, and deployment notes. Include desktop and mobile acceptance evidence. Do not return placeholder comments or omit failure states.

## Acceptance gate
The project passes type checking, production build, metadata and structured-data validation, desktop and 390px browser journeys, keyboard navigation, reduced motion, broken-media inspection, console and request audits, prompt originality checks, and a final source-rights review.