Build a small multi-page website from a description
This example asks for a ceramics studio site with About, Pricing and Contact pages in warm colours. Each page is its own HTML file with shared navigation.
Kiln & CoLanding pageExample — not saved until you change it
What the planner understood
Confidence85%
website→meansLanding page template
studio→meansLanding page template
Kiln & Co→meansapp name
ceramics→meanstheme preset “sunset”
about→means“About” page
contact→means“Contact” page
pricing→means“Pricing” page
Feasibility, templates and prompt history
Feasibility
NATIVELight and dark theme
NATIVEResponsive layout
Start from a template
Picking a template keeps the name, colours and fields from your description.
Prompt history
Off by default. Prompts are only kept in this browser if you turn this on.
Sandboxed · network off · fits 772px
App type
Landing page — Hero, features, pricing, testimonials and FAQ sections.
Pages and sections
index.html
⋮⋮Hero
⋮⋮Features
⋮⋮Testimonials
⋮⋮Call to action
about.html
⋮⋮About
⋮⋮Team
⋮⋮Stats
contact.html
⋮⋮Contact form
pricing.html
⋮⋮Pricing
⋮⋮FAQ
Drag sections to reorder, or use the arrow buttons. Navigation links are generated for every page.
Wireframe
HomeHeader + navHeroFeaturesTestimonialsCall to actionFooter
AboutHeader + navAboutTeamStatsFooter
ContactHeader + navContact formFooter
PricingHeader + navPricingFAQFooter
Component library (8)
Native <dialog> with focus return, Escape to close and a labelled title.
<button class="btn btn-primary" type="button" data-open-dialog="demo-dialog">Open dialog</button>
<dialog class="c-modal" id="demo-dialog" aria-labelledby="demo-dialog-title">
<h2 id="demo-dialog-title">Delete this project?</h2>
<p>This removes it from this device. You can export a copy first.</p>
<div class="c-modal-actions">
<button class="btn" type="button" data-close-dialog>Cancel</button>
<button class="btn btn-primary" type="button" data-close-dialog value="confirm">Delete</button>
</div>
</dialog>
Real pages, not one long scroll
Ask for “about, pricing and contact pages” and you get about.html, pricing.html and contact.html, each with the same header, a menu that marks the current page, and a mobile menu button. Links work inside the preview: click them and the preview switches page.
Sections such as hero, features, testimonials, pricing, team, gallery, FAQ and contact are building blocks. In the Plan tab you can drag them into a different order, move them with the keyboard, add a section from the library or remove one.
Honest forms
The contact and sign-up forms validate input and save submissions in the visitor’s browser. They do not email you — a static site cannot — and the generated page says so. Connect a form service or your own backend after export if you need delivery.
Hosting the result
The export is plain HTML, CSS and JavaScript with a README. Upload the folder to any static host. An optional package.json pins Vite for a local dev server, but nothing needs to be built.
Frequently asked questions
Can I use my own domain?
Yes, after you deploy the exported files to a static host that supports custom domains. AIWebApp does not host sites.
Are the placeholder images and stats real?
No. Gallery tiles, quotes and numbers are labelled placeholders so they are easy to find and replace.
Is the HTML SEO-friendly?
Each page has a title, meta description, one h1, landmarks and semantic sections. Add your own content and descriptions before publishing.