Your website with AI: from brief to checked prototype
Build a small landing page from a synthetic brief, check mobile layout, links and content rights. Prepare a safe file allowlist for future publication.
A small website helps customers understand an offer, its price and the next step. For a first version, accurate text and working navigation matter more than a complex stack or a promise to build everything in two hours.
Task: use AI to create a one-page service prototype from an entirely synthetic brief.
Result: a local landing page with three offers, FAQs and an honest contact section. No enquiry submission or internet publication.
A good fit if: you need a first page for a service, workshop or small project. A shop with payments, a customer account area and personal data processing require separate development.
What you need: an AI editor with a working folder and a browser. Simple HTML needs no GitHub, domain, npm or paid hosting. Chat without file access can provide file contents but cannot check the site for you.
Limitation: you can set aside two hours for a first attempt, but that does not guarantee an online business ready to launch. Revisions, phone checks, content rights and publication take additional time.
Prototype first, real enquiries later
The practice page below offers fictional indoor plant care services. The prices, name and terms exist only for this exercise. There are no third-party photos, reviews, logos, copied templates or customer figures.
The “How to get in touch” link leads to an explanation that no real contact channel is connected yet. This is a deliberate limitation. Showing “Request sent” without a working channel misleads visitors. Saving something in localStorage does not send it to the owner either.
One task for AI
Create a local one-page landing page from the synthetic brief below. All necessary input is in this message. Do not publish anything or connect external services.
ENVIRONMENT:
Create a new plant-demo folder without overwriting existing files. If the name is taken, choose an unused name and report it. Check file and browser access. Use plain HTML and CSS without a build step, JavaScript, npm, libraries, external fonts, CDN, maps, analytics or images. The page must open locally as index.html. If a browser is unavailable, perform the available static checks and mark visual and interactive checks “not verified”. Do not install programs or change settings without approval.
SYNTHETIC BRIEF:
Name: “Practice Green Workshop”. At the top and in the contact section, clearly state: “Practice prototype. Services and prices are fictional. Enquiries are not accepted”.
Audience: small-office owners who want clear help with indoor plants.
Heading: “Straightforward plant care for a small office”.
Subheading: “Three practice options: a care review, a monthly plan and repotting help”.
Offers:
P1 — Care review: 90000 UZS; online, 30 minutes; result: a list of recommendations.
P2 — Monthly plan: 180000 UZS; online, 60 minutes; result: a care schedule for 5 plants.
P3 — Repotting help: 250000 UZS; in person, 60 minutes; materials cost extra, and their exact cost is currently unknown.
All amounts are for practice. Do not invent an address, phone number, Telegram username, available slots, guarantees of saving a plant or profit growth.
Three steps: choose an option; clarify details with the specialist; agree on a time. Do not claim that bookings are already open.
FAQ: “Are materials included in the price?” — “Materials for P3 cost extra; the cost needs to be confirmed”. “Can I book on the website?” — “No, this is a practice prototype that does not accept enquiries”. “Where is the in-person meeting?” — “No address has been provided yet; it needs to be agreed”.
The main link “View options” leads to #formats. “How to get in touch” leads to #contact. The #contact section explains: “No contact channel is connected. This is a practice prototype; nothing is sent”. Do not create a form, mailto, tel or a link to an invented account.
DESIGN AND CONTENT:
English, lang=en, UTF-8, viewport, one h1, logical h2 headings and semantic header/main/footer. Tab title: “Practice Green Workshop — prototype”, with a description free of advertising promises. Light background, dark text, a muted green accent and a system font. Create decorative elements with CSS, without third-party materials. Visible link focus, keyboard access, readable text and no animations. Every link must have a clear label and an existing target.
FILES AND SAFETY:
Create public/index.html and public/styles.css; separately create README.md, RIGHTS.md, QA.md and .gitignore. The allowlist for future publication contains only public/index.html and public/styles.css. The publication root is the public folder: its allowed contents are sent to the host, so the homepage is at / and styles are at /styles.css, without /public in the public URL. Do not create a repository or upload even these files in this task.
In RIGHTS.md, list the original practice text and CSS and the absence of external images/fonts/logos/reviews. Do not copy third-party templates or paid materials. In .gitignore, exclude .env, .env.*, *.log and support files. Do not create secrets. Before reporting, read both public files in full and check for tokens, passwords, personal contacts, external URLs and hidden requests. Do not treat pattern searches as a guarantee that no secrets are present.
ACCEPTANCE:
1. Open the page locally; check widths of 360 and 1280 CSS pixels. There must be no horizontal scrolling, clipped text, overlaps or missing sections.
2. At both sizes, show the practice warning, three options with exact prices and durations, three steps, all three FAQs and the honest contact section. The unknown address and material cost must remain unknown.
3. Both navigation links lead to the correct sections. Links can be reached with Tab and activated with Enter, with visible focus. Text and navigation remain accessible at 200% zoom.
4. Clicking “How to get in touch” sends no data and shows no success message. There are no forms, JavaScript, localStorage, fetch, network integrations or external resources. The browser's Network panel shows no HTTP(S) requests from the page; the page still works with networking disabled.
5. Check for lang, charset, viewport, title, description, exactly one h1 and unique id values. Ensure a contrast ratio of at least 4.5:1 for normal text; record the colors used and the measurement if a tool is available, otherwise mark the measurement unverified.
6. Compare the file tree with the future publication allowlist. README, RIGHTS, QA, .gitignore and any hidden files are not for publication. There must be no other files in public.
Perform the checks available in your environment. In QA.md, record the method, actual result and “passed/failed/not verified” for each check. Attach screenshots of both sizes only if you actually captured them, and store them outside public. Do not present source analysis as a browser test. Fix any errors and rerun the checks.
In README, provide clear instructions for opening public/index.html and describe what needs agreement for a real version: approved content and rights, a real contact recipient, hosting and commercial-use terms, the exact file list and permission to publish.
Get separate approval for new connections, publication, spending, data sharing, permissions and agreements. Do not bypass denials. Finish by showing the files, what was actually checked, what remains unverified and one next step. Do not report a public URL: this task does not create one.
Assess the result with a few checks
Open public/index.html. All three cards should remain readable on a narrow screen: 90 000, 180 000 and 250 000 UZS. The third must clearly state that materials cost extra, without an invented amount. Click “How to get in touch”: you should reach the practice-mode explanation, not see “Thank you, your request has been sent”.
Check two more things: the page uses no external resources, and the public folder contains only the two authorized files. A screenshot of an attractive first screen does not replace checking links, keyboard access and the rest of the content.
What is needed before publication
- Confirm the offer. Replace synthetic data only with approved facts. Do not add customers, results, addresses or reviews that do not exist.
- Check rights. An image or text being publicly accessible online does not grant permission to use it. WIPO explains this. For third-party templates, check the license for both code and included materials, commercial use and attribution. Do not copy paid lessons or someone else's private source code.
- Check people and brands in photos. Even when a photo license permits commercial use, rights relating to recognizable people, private property and trademarks still matter: see the Unsplash explanation. Use a logo or review only with a verified basis and agreed publication; do not invent a review or attribute it to someone. If in doubt, leave it out.
- Choose a real contact channel. The simplest next stage is an agreed link to the owner's real contact address. Verify the recipient and that the link opens. This still does not guarantee that a visitor sent a message. A form needs server-side processing, protection against abuse, clear data-handling rules and tests of successful and failed delivery. Never put a Telegram bot token in the frontend.
- Agree on the publication destination and files. Check the final files themselves, including hidden files and built artifacts. Publish only the approved allowlist; do not ask to “upload the whole folder”.
.gitignorehelps with Git but does not prevent a manual archive upload or remove a secret from history.
Hosting and domains: no promise of “free forever”
The local exercise needs no hosting. For a business website, check the chosen provider's current terms, limits, commercial use, automatic renewal and extra-feature costs. Vercel Hobby is for personal, non-commercial use, so it cannot automatically be recommended as a free plan for a business website. This is stated in the Vercel documentation. A paid plan is not mandatory: first compare suitable terms, then agree on the choice and spending.
If you previously used Google Domains, note the official announcement: its customers became Squarespace customers, and domain migration was completed on 10 July 2024. Choose a registrar based on the domain extension you need, current registration and renewal prices, and ownership and transfer rules. Agree separately on a domain purchase, DNS changes, repository access and acceptance of terms.
After authorized publication, check the actual public address, HTTPS, mobile layout, links and absence of extra files. A local check does not establish these in advance.
Common mistakes and the next step
- “Make it prettier.” Describe an observable issue: “At 360 pixels wide, the price is clipped. Fix the card without changing the text or other sections”.
- There is a form but no delivery. Remove the form until the channel is implemented or clearly keep it as a demonstration without submission. Do not substitute browser storage for delivery.
- AI promises guaranteed sales growth. Remove the promise if there is no evidence for it. A website describes an offer; it does not create evidence for the business.
- Publishing to meet a deadline. Unchecked rights, secrets and false submission messages are reasons to stop, even if the appearance is satisfactory.
The next permitted step is to show the local prototype to the owner and approve the real text and contact channel. Then separately prepare a publication plan with the exact file list and any costs.
Frequently asked questions
Can I build a website in two hours?
You can try to put together a first local version in two hours. It is not a guarantee: phone checks, revisions, content rights and publication may take additional time.
Do I need GitHub, a domain and paid hosting for the exercise?
No. The practice page opens locally as public/index.html. For a real business website, hosting is chosen separately, with its terms, limits and potential costs checked. Vercel Hobby is for personal, non-commercial use.
Does this website accept enquiries?
No. The practice prototype has no form or data submission. “How to get in touch” leads to an explanation. A real contact channel or server-side form is connected in a separate stage after agreeing on the recipient and checking delivery.
Can I use photos, logos and reviews from the internet?
Only with appropriate rights and permissions. Availability online is not permission for commercial use. You need a verified basis for publishing reviews and logos; reviews must not be invented.
Which files can be published?
This exercise prepares an allowlist containing public/index.html and public/styles.css. The future publication root is the public folder: the homepage will be at / and styles at /styles.css, without /public in the URL. Before real publication, check the contents and agree separately on the upload. Do not upload secrets, hidden files, reports or the entire working folder.
When is the website ready to publish?
When real text and rights are approved, mobile layout and links are checked, a real contact channel is defined, secrets are excluded, and the publication destination, files and terms are agreed. After publication, check the public address and HTTPS separately.