# Customize ORDISHO

Use the included index.html and local assets/ folder as the starting point.

Brand: [YOUR BRAND]
Audience: [WHO USES IT]
Purpose: [PRIMARY TASK]
Verified content: [PEOPLE / PRODUCTS / PRICES / REAL CLAIMS]
Primary action: [ACTION AND DESTINATION]
Approved assets: [REPLACEMENT IMAGES AND THEIR RIGHTS]

Preserve this visual direction: Vivid orange · warm white · Inter.
Keep the reference layout, image proportions and section rhythm. Adapt it for 375, 768, 1024 and 1440px widths with readable text, visible focus, keyboard controls and reduced-motion support. Keep the HTML, CSS and JavaScript editable and all assets local.

Retain or deliberately replace these working interactions:
- Switch dashboard tabs, expand campaign details and prepare a local sample email draft.
- Select customer segments, location and industry, then preview the sample audience.
- Change reporting periods and switch four keyboard-accessible workflow tabs.
- Try registration, login, sample-plan, payment and language previews without sending data.
- Use the responsive menu, real section links, native dialog focus and Escape dismissal.

Reference names, portraits, prices, testimonials, ratings and customer counts are sample content. Replace them with approved material and verified claims before publishing. The MIT license covers the implementation and instructions, not the supplied brand/photographic imagery; see ASSETS.md and the font/icon notices.

Do not invent successful checkout, authentication, email delivery, orders, backend storage or deployment. Do not add remote scripts, analytics, credentials or services unless requested. Keep local demo actions explicitly labeled inside their result dialogs.

Deliver the updated source and assets, verify the main journey and every in-page link, and report the checks and remaining service integrations.