How to build a website with AI and publish it in 10 minutes

Build a business-card website: [name and profession: e.g., massage therapist Anna Smith], [city or “online”].
Sections:
1. Hero: name, profession, one line about the main benefit for clients and a “Book a session” button that opens WhatsApp from the contacts.
2. About me: experience, training and approach — 3–4 sentences, suggest the text and I will adjust it.
3. Services with prices: [one line per service: Back massage — $60]
4. Testimonials: three cards, sample text for now — I will replace it.
5. Contacts.

Contacts: phone [phone number] as a tel: link, so it can be called with one tap; WhatsApp [WhatsApp number] (wa.me link); address [street, city] with an “Open in Google Maps” button; opening hours [opening hours].

Footer: © year and the owner's details — [your name or business name], [email address].

Look: light and calm, lots of white space; system fonts.
Photos: do not hotlink images from other sites: where a photo is needed, put a placeholder block labeled “photo” — I will replace it with my own files from the images/ folder.

Output requirements:
— a single index.html file: styles in <style>, scripts in <script>;
— no external libraries, fonts or CDNs, relative paths only, no stubs like href="#" or example.com;
— mobile-first, then desktop: nothing overflows at 360 px, buttons at least 44 px tall;
— <html lang="en">, meta charset UTF-8 and viewport, a title under 60 characters and a meta description under 160; a single h1 per page, alt on images;
— a link preview for messengers: og:title, og:description and og:image with the full address https://[your-site.tuqo.app or your domain]/images/og.jpg (I will add the 1200×630 image myself);
— a favicon right in the code: <link rel="icon" href="data:image/svg+xml,…"> with a simple symbol in the brand color.

Output the whole file as one code block, with no explanations inside the code.

Build a landing page that sells: [what you sell: e.g., bathroom renovation], [city or “nationwide”].
Sections:
1. Hero: a benefit-driven headline, a subheadline and a “Get a quote” button.
2. Problems clients come with — 4 cards.
3. How we work — 4 numbered steps.
4. Pricing — if there are several packages, highlight the middle one as popular: [package prices or “make up three packages, I will adjust”]
5. Guarantees and timelines.
6. Testimonials — three cards, sample text for now, I will replace it.
7. FAQ — 5 questions that expand on click.
8. Lead form. Every button on the page smoothly scrolls to it.
9. Contacts.

Contacts: phone [phone number] as a tel: link, so it can be called with one tap; WhatsApp [WhatsApp number] (wa.me link); email [email address] as a mailto: link.

Lead form — fields: name, phone, comment, and a “Send” button. Build it as a plain <form> with name attributes on the fields. Do not wire up sending: I will take the form code from the Forms tab in the Tuqo panel.

Privacy, in plain language (I will review the text myself):
— privacy.html “Privacy Policy”: who runs the site — [your name or business name]; what is collected and why: the form — name, phone, comment, to reply to the request; Tuqo receives and stores form submissions on the owner's behalf; how long it is kept; how to ask for a copy or deletion — write to [email for privacy requests];
— a checkbox “I agree to the processing of my data under the Privacy Policy” next to the form: unchecked by default, required, name="consent" — the form does not send without it;
— a “Privacy Policy” link under the form button and in the footer.

Footer: © year and the owner's details — [your name or business name], [email address].

Look: bright and bold, large headings; system fonts.
Photos: do not hotlink images from other sites: where a photo is needed, put a placeholder block labeled “photo” — I will replace it with my own files from the images/ folder.

Output requirements:
— files: index.html, privacy.html, styles.css; the same header and footer on every page, relative links between pages;
— no external libraries, fonts or CDNs, relative paths only, no stubs like href="#" or example.com;
— mobile-first, then desktop: nothing overflows at 360 px, buttons at least 44 px tall;
— <html lang="en">, meta charset UTF-8 and viewport, a title under 60 characters and a meta description under 160 — its own on each page; a single h1 per page, alt on images;
— a link preview for messengers: og:title, og:description and og:image with the full address https://[your-site.tuqo.app or your domain]/images/og.jpg (I will add the 1200×630 image myself);
— a favicon right in the code: <link rel="icon" href="data:image/svg+xml,…"> with a simple symbol in the brand color.

Output each file as a separate code block with the file name above it, with no explanations inside the code.

Build a portfolio website: [name and specialty: e.g., wedding photographer Maria], [city].
Sections:
1. Hero: name, specialty and a “Discuss a project” button that opens WhatsApp from the contacts.
2. A gallery of 12 works in a grid (two columns on phones); clicking a photo opens it full screen, arrows and swipe switch photos, Esc and a close button close it.
3. Services and prices: [one line per service: Wedding shoot — from $1,500]
4. Contacts.
The photos will be in the images/ folder named 01.jpg … 12.jpg — use these paths right away, add loading="lazy" and alt text describing each work.

Contacts: phone [phone number] as a tel: link, so it can be called with one tap; WhatsApp [WhatsApp number] (wa.me link).

Footer: © year and the owner's details — [your name or business name], [email address].

Look: light and calm, lots of white space; system fonts.

Output requirements:
— a single index.html file: styles in <style>, scripts in <script>;
— no external libraries, fonts or CDNs, relative paths only, no stubs like href="#" or example.com;
— mobile-first, then desktop: nothing overflows at 360 px, buttons at least 44 px tall;
— <html lang="en">, meta charset UTF-8 and viewport, a title under 60 characters and a meta description under 160; a single h1 per page, alt on images;
— a link preview for messengers: og:title, og:description and og:image with the full address https://[your-site.tuqo.app or your domain]/images/og.jpg (I will add the 1200×630 image myself);
— a favicon right in the code: <link rel="icon" href="data:image/svg+xml,…"> with a simple symbol in the brand color.

Output the whole file as one code block, with no explanations inside the code.

Build an invitation website: [e.g., Anna and Michael's wedding], [e.g., June 12, 2027, 3 pm].
Sections:
1. A beautiful hero with the names and the date.
2. A countdown to the event: days, hours, minutes.
3. Schedule: [the schedule of the day — suggest one, I will adjust it]
4. Venue: [venue name], [street, city] — with an “Open in Google Maps” button for this address.
5. RSVP form.
6. Host contacts.

Contacts: phone [phone number] as a tel: link, so it can be called with one tap; WhatsApp [WhatsApp number] (wa.me link).

Lead form — fields: name, attending / not attending, number of guests, dietary preferences, and a “Send” button. Build it as a plain <form> with name attributes on the fields. Do not wire up sending: I will take the form code from the Forms tab in the Tuqo panel.

Look: soft pastel, an elegant system font for headings; system fonts.
Photos: do not hotlink images from other sites: where a photo is needed, put a placeholder block labeled “photo” — I will replace it with my own files from the images/ folder.

Output requirements:
— a single index.html file: styles in <style>, scripts in <script>;
— no external libraries, fonts or CDNs, relative paths only, no stubs like href="#" or example.com;
— mobile-first, then desktop: nothing overflows at 360 px, buttons at least 44 px tall;
— <html lang="en">, meta charset UTF-8 and viewport, a title under 60 characters and a meta description under 160; a single h1 per page, alt on images;
— a link preview for messengers: og:title, og:description and og:image with the full address https://[your-site.tuqo.app or your domain]/images/og.jpg (I will add the 1200×630 image myself);
— a favicon right in the code: <link rel="icon" href="data:image/svg+xml,…"> with a simple symbol in the brand color.

Output the whole file as one code block, with no explanations inside the code.

Build an online menu for [e.g., the Grain cafe, Berlin] that guests open from a QR code on their phones.
Top: name, opening hours and a “Call” button.
Sections with sticky tabs that scroll to each section: [e.g., coffee, tea, breakfast, desserts].
Each item has a name, a short description, volume or weight and a price.
Items: [paste your menu or write “make up 5 items per section — I will replace them”]
Large font, high contrast, no heavy animations — the menu must open instantly even on a slow connection.

Contacts: phone [phone number] as a tel: link, so it can be called with one tap; address [street, city] with an “Open in Google Maps” button; opening hours [opening hours].

Footer: © year and the owner's details — [your name or business name], [email address].

Look: light and calm, lots of white space; system fonts.
Photos: no photos: inline SVG icons, gradients and bold typography.

Output requirements:
— a single index.html file: styles in <style>, scripts in <script>;
— no external libraries, fonts or CDNs, relative paths only, no stubs like href="#" or example.com;
— mobile-first, then desktop: nothing overflows at 360 px, buttons at least 44 px tall;
— <html lang="en">, meta charset UTF-8 and viewport, a title under 60 characters and a meta description under 160; a single h1 per page, alt on images;
— a link preview for messengers: og:title, og:description and og:image with the full address https://[your-site.tuqo.app or your domain]/images/og.jpg (I will add the 1200×630 image myself);
— a favicon right in the code: <link rel="icon" href="data:image/svg+xml,…"> with a simple symbol in the brand color.

Output the whole file as one code block, with no explanations inside the code.

Build an event page: [event name] — workshop, [date and time], [address or “online”].
Sections:
1. Hero: name, date, venue, price ([free or a price]) and a “Register” button.
2. Who it is for and what attendees take away — 3–4 points.
3. Schedule: [suggest one, I will adjust it]
4. Speakers — cards with name, title and one line: [sample ones for now, I will replace them]
5. Venue and directions (or a stream link).
6. Registration form.
7. Organizer contacts.

Contacts: Telegram [Telegram username] (as a link); email [email address] as a mailto: link.

Lead form — fields: name, phone, email, and a “Send” button. Build it as a plain <form> with name attributes on the fields. Do not wire up sending: I will take the form code from the Forms tab in the Tuqo panel.

Privacy, in plain language (I will review the text myself):
— privacy.html “Privacy Policy”: who runs the site — [your name or business name]; what is collected and why: the form — name, phone, email, to reply to the request; Tuqo receives and stores form submissions on the owner's behalf; how long it is kept; how to ask for a copy or deletion — write to [email for privacy requests];
— a checkbox “I agree to the processing of my data under the Privacy Policy” next to the form: unchecked by default, required, name="consent" — the form does not send without it;
— a “Privacy Policy” link under the form button and in the footer.

Footer: © year and the owner's details — [your name or business name], [email address].

Look: bright and bold, large headings; system fonts.
Photos: do not hotlink images from other sites: where a photo is needed, put a placeholder block labeled “photo” — I will replace it with my own files from the images/ folder.

Output requirements:
— files: index.html, privacy.html, styles.css; the same header and footer on every page, relative links between pages;
— no external libraries, fonts or CDNs, relative paths only, no stubs like href="#" or example.com;
— mobile-first, then desktop: nothing overflows at 360 px, buttons at least 44 px tall;
— <html lang="en">, meta charset UTF-8 and viewport, a title under 60 characters and a meta description under 160 — its own on each page; a single h1 per page, alt on images;
— a link preview for messengers: og:title, og:description and og:image with the full address https://[your-site.tuqo.app or your domain]/images/og.jpg (I will add the 1200×630 image myself);
— a favicon right in the code: <link rel="icon" href="data:image/svg+xml,…"> with a simple symbol in the brand color.

Output each file as a separate code block with the file name above it, with no explanations inside the code.

Build a landing page for an online course: [course topic] — for [e.g., beginner accountants].
Sections:
1. The promised result and an “Enroll” button.
2. Curriculum by module — an accordion, each module with a title and 3–4 topics: [suggest the modules, I will adjust them]
3. The author: [name, experience and credentials], photo placeholder.
4. Format and duration: suggest a format, I will adjust it.
5. Pricing tiers — cards: [one line per tier: Basic — $99]
6. Testimonials — three cards, sample text for now.
7. FAQ — expand on click.
8. “Enroll” form.
9. Contacts.

Contacts: Telegram [Telegram username] (as a link); email [email address] as a mailto: link.

Lead form — fields: name, phone, email, and a “Send” button. Build it as a plain <form> with name attributes on the fields. Do not wire up sending: I will take the form code from the Forms tab in the Tuqo panel.

Privacy, in plain language (I will review the text myself):
— privacy.html “Privacy Policy”: who runs the site — [your name or business name]; what is collected and why: the form — name, phone, email, to reply to the request; Tuqo receives and stores form submissions on the owner's behalf; how long it is kept; how to ask for a copy or deletion — write to [email for privacy requests];
— a checkbox “I agree to the processing of my data under the Privacy Policy” next to the form: unchecked by default, required, name="consent" — the form does not send without it;
— a “Privacy Policy” link under the form button and in the footer.

A terms.html “Terms of Sale” page: what is sold, prices, how to pay and receive it, how refunds and returns work, and the seller's details — [your name or business name], [registration or tax number, if your country requires it]. Link to it in the footer and next to the prices.

Footer: © year and the owner's details — [your name or business name], [email address].

Look: bright and bold, large headings; system fonts.
Photos: do not hotlink images from other sites: where a photo is needed, put a placeholder block labeled “photo” — I will replace it with my own files from the images/ folder.

Output requirements:
— files: index.html, privacy.html, terms.html, styles.css; the same header and footer on every page, relative links between pages;
— no external libraries, fonts or CDNs, relative paths only, no stubs like href="#" or example.com;
— mobile-first, then desktop: nothing overflows at 360 px, buttons at least 44 px tall;
— <html lang="en">, meta charset UTF-8 and viewport, a title under 60 characters and a meta description under 160 — its own on each page; a single h1 per page, alt on images;
— a link preview for messengers: og:title, og:description and og:image with the full address https://[your-site.tuqo.app or your domain]/images/og.jpg (I will add the 1200×630 image myself);
— a favicon right in the code: <link rel="icon" href="data:image/svg+xml,…"> with a simple symbol in the brand color.

Output each file as a separate code block with the file name above it, with no explanations inside the code.

Build a one-page resume: [first and last name], [target role].
Sections:
1. Summary: 2–3 sentences based on the experience below.
2. Work experience: [one line per job: company, years, what you did and achieved]
3. Skills as tags: [comma-separated].
4. Contacts.
A clean, professional look. Add a “Download PDF” button that prints the page (window.print) and print styles: no buttons or backgrounds, one or two A4 pages.

Contacts: phone [phone number] as a tel: link, so it can be called with one tap; social profile [link to your profile] (as a link); email [email address] as a mailto: link.

Look: strict business, no decorations; system fonts.
Photos: do not hotlink images from other sites: where a photo is needed, put a placeholder block labeled “photo” — I will replace it with my own files from the images/ folder.

Output requirements:
— a single index.html file: styles in <style>, scripts in <script>;
— no external libraries, fonts or CDNs, relative paths only, no stubs like href="#" or example.com;
— mobile-first, then desktop: nothing overflows at 360 px, buttons at least 44 px tall;
— <html lang="en">, meta charset UTF-8 and viewport, a title under 60 characters and a meta description under 160; a single h1 per page, alt on images;
— a link preview for messengers: og:title, og:description and og:image with the full address https://[your-site.tuqo.app or your domain]/images/og.jpg (I will add the 1200×630 image myself);
— a favicon right in the code: <link rel="icon" href="data:image/svg+xml,…"> with a simple symbol in the brand color.

Output the whole file as one code block, with no explanations inside the code.

Build a company website: [name and what it does], [city]. 4 main pages, a shared header with a menu (the active item highlighted) and a footer on every page.
1. index.html — home: a hero with a “Get a quote” button, benefits, a short services overview, testimonials.
2. services.html — services as cards: [one line per service: Apartment cleaning — from $90]
3. about.html — about the company: story and team, suggest the text
4. contacts.html — contacts and a contact form

Contacts: phone [phone number] as a tel: link, so it can be called with one tap; email [email address] as a mailto: link; address [street, city] with an “Open in Google Maps” button; opening hours [opening hours].

Lead form — fields: name, phone, comment, and a “Send” button. Build it as a plain <form> with name attributes on the fields. Do not wire up sending: I will take the form code from the Forms tab in the Tuqo panel.

Privacy, in plain language (I will review the text myself):
— privacy.html “Privacy Policy”: who runs the site — [your name or business name]; what is collected and why: the form — name, phone, comment, to reply to the request; Tuqo receives and stores form submissions on the owner's behalf; how long it is kept; how to ask for a copy or deletion — write to [email for privacy requests];
— a checkbox “I agree to the processing of my data under the Privacy Policy” next to the form: unchecked by default, required, name="consent" — the form does not send without it;
— a “Privacy Policy” link under the form button and in the footer.

Footer: © year and the owner's details — [your name or business name], [email address].

Look: strict business, no decorations; system fonts.
Photos: do not hotlink images from other sites: where a photo is needed, put a placeholder block labeled “photo” — I will replace it with my own files from the images/ folder.

Output requirements:
— files: index.html, services.html, about.html, contacts.html, privacy.html, styles.css; the same header and footer on every page, relative links between pages;
— no external libraries, fonts or CDNs, relative paths only, no stubs like href="#" or example.com;
— mobile-first, then desktop: nothing overflows at 360 px, buttons at least 44 px tall;
— <html lang="en">, meta charset UTF-8 and viewport, a title under 60 characters and a meta description under 160 — its own on each page; a single h1 per page, alt on images;
— a link preview for messengers: og:title, og:description and og:image with the full address https://[your-site.tuqo.app or your domain]/images/og.jpg (I will add the 1200×630 image myself);
— a favicon right in the code: <link rel="icon" href="data:image/svg+xml,…"> with a simple symbol in the brand color.

Output each file as a separate code block with the file name above it, with no explanations inside the code.

Build a link-in-bio page for [name or brand]: one page with all the links, to put in social profiles.
Top: a round photo or logo, the name and the line “[e.g., nail artist in Austin]”.
Below — large full-width buttons, one per row: [button name — address, one per line]
Under them — round messenger buttons from the contacts.
On phones it looks like an app, on desktop — a centered card up to 480 px wide; it opens instantly.

Contacts: WhatsApp [WhatsApp number] (wa.me link); Telegram [Telegram username] (as a link); social profile [link to your profile] (as a link).

Footer: © year and the owner's details — [your name or business name], [email address].

Look: bright and bold, large headings; system fonts.
Photos: do not hotlink images from other sites: where a photo is needed, put a placeholder block labeled “photo” — I will replace it with my own files from the images/ folder.

Output requirements:
— a single index.html file: styles in <style>, scripts in <script>;
— no external libraries, fonts or CDNs, relative paths only, no stubs like href="#" or example.com;
— mobile-first, then desktop: nothing overflows at 360 px, buttons at least 44 px tall;
— <html lang="en">, meta charset UTF-8 and viewport, a title under 60 characters and a meta description under 160; a single h1 per page, alt on images;
— a link preview for messengers: og:title, og:description and og:image with the full address https://[your-site.tuqo.app or your domain]/images/og.jpg (I will add the 1200×630 image myself);
— a favicon right in the code: <link rel="icon" href="data:image/svg+xml,…"> with a simple symbol in the brand color.

Output the whole file as one code block, with no explanations inside the code.

Build a catalog website: [name and what you sell: e.g., Hill Farm honey]. No cart or online checkout — orders go through a messenger.
Sections:
1. Hero: name, what makes you good and a “See the catalog” button.
2. Catalog as cards; each product has a photo, name, price, short description and an “Order” button.
3. Products: [products or “make up 6 products — I will replace them”]
4. The “Order” button opens WhatsApp from the contacts with the text “I'd like to order: <product>, <price>” (a wa.me link with ?text=).
5. Delivery and payment: [how you deliver and how to pay].
6. Contacts.

Contacts: phone [phone number] as a tel: link, so it can be called with one tap; WhatsApp [WhatsApp number] (wa.me link).

A terms.html “Terms of Sale” page: what is sold, prices, how to pay and receive it, how refunds and returns work, and the seller's details — [your name or business name], [registration or tax number, if your country requires it]. Link to it in the footer and next to the prices.

Footer: © year and the owner's details — [your name or business name], [email address].

Look: light and calm, lots of white space; system fonts.
Photos: do not hotlink images from other sites: where a photo is needed, put a placeholder block labeled “photo” — I will replace it with my own files from the images/ folder.

Output requirements:
— files: index.html, terms.html, styles.css; the same header and footer on every page, relative links between pages;
— no external libraries, fonts or CDNs, relative paths only, no stubs like href="#" or example.com;
— mobile-first, then desktop: nothing overflows at 360 px, buttons at least 44 px tall;
— <html lang="en">, meta charset UTF-8 and viewport, a title under 60 characters and a meta description under 160 — its own on each page; a single h1 per page, alt on images;
— a link preview for messengers: og:title, og:description and og:image with the full address https://[your-site.tuqo.app or your domain]/images/og.jpg (I will add the 1200×630 image myself);
— a favicon right in the code: <link rel="icon" href="data:image/svg+xml,…"> with a simple symbol in the brand color.

Output each file as a separate code block with the file name above it, with no explanations inside the code.

Check this website and fix:
— the layout at 360, 390 and 768 px widths: nothing overflows, no horizontal scrolling;
— buttons and links at least 44 px tall, text at least 16 px;
— text/background contrast;
— alt on every image and the h1–h3 heading order (a single h1);
— a title under 60 characters and a meta description under 160.
Return the fixed file in full, as one code block.

[paste the site code here or attach the file]

My website is published on Tuqo and the publish check found these remarks:
[copy the list from the “What to improve” block on the site page in the panel]

Fix each remark and change nothing else. Return the fixed files in full, each as a separate code block with the file name above it.

[paste the site code here or attach the files]

Build a website: [description — site type, audience, sections, style, contacts] and publish it on Tuqo.
— Create a new site with the subdomain [site-name] (Latin letters and hyphens).
— If the site has a form, connect the Tuqo lead form: get the ready form code with get_forms_overview.
— Publish it and send me the link.
— If the publish check reports remarks, fix them and publish again.