# Customize PixelForge

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: Midnight blue · electric purple · Poppins.
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:
- Watch portraits fade out and return one by one; pause or resume the sequence.
- Hover, focus or tap a portrait to enlarge it while the other portraits ease smaller.
- Motion stops offscreen, in a hidden tab, or with reduced-motion preferences.
- Open a team member’s sample profile from a social control.
- Open the project form, complete required fields and preview a submission.
- Use the mobile menu, Escape key and focus return.
- Navigate directly to the team and project sections.

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.