Walk through a sample prompt, generated preview, revision request, export package, and deployment path using the same public proof assets Foundry ships as source.
Brief
I need a modern website for a mobile mechanic in Pittsburgh. Customers should be able to see services, trust me quickly, and request a quote. Make it feel tough, reliable, and local — not like a generic repair shop template.
Emergency service, local proof, and a quote path above the fold.
Step 1
I need a modern website for a mobile mechanic in Pittsburgh. Customers should be able to see services, trust me quickly, and request a quote. Make it feel tough, reliable, and local — not like a generic repair shop template.
The request captures the business, audience, trust problem, desired action, visual tone, and what the user wants to avoid.
Step 2
The generated preview includes a direct hero, service packages, proof blocks, service area, emergency CTA, FAQ, and quote path.
This sample mirrors the source-export contract: ordinary pages, styling, small interactions, and editable content data.
Step 3
Make the quote request stronger, add emergency service proof, and move the service area near the top.
Revision requests update the generated surface while preserving preview, files, and export ownership.
Step 4
The final ZIP contains HTML, CSS, JavaScript, editable data, deploy configuration, and hosting notes.
Upload the package to common static hosts or keep the files as owned source for later editing.
This walkthrough is sample-backed, so visitors can inspect the product flow without opening a live AI generation session.
The demo points to the public sample export route so the ownership claim is tied to downloadable files, not only screenshots.