Where it lives
Every build ends up in one of three homes, and picking the right one takes thirty seconds:
- A shared link (rung one). Publish the Artifact and you get a public URL you can put in a bio, a post, or an email. Fastest path; perfect for quizzes, calculators, and one-off client pages.
- Its own hosted page (rung two). A website builder like Hostinger Horizons hosts your build at a real web address and handles the technical side. Best for landing pages and anything you want at your own domain.
- Embedded in your existing site. Most site platforms have an "embed" or "HTML" block — paste in the code the AI gives you and your tool appears right inside a page you already have.
Custom domains, in plain English
A custom domain is just your own web address — yourbusiness.com/quiz instead of a long random link. You buy the name once a year (often through the same host), and in the builder's settings you point it at your page. That's the whole concept. Don't let the word "DNS" scare you; the tool walks you through it, and if you get stuck, paste the tool's instructions into your chat and ask it to explain each step like you're not technical.
The data question: where do the emails GO?
This is the step most people skip, and it quietly wastes every sign-up. When someone types their email into your quiz or landing page, that address has to land somewhere you can actually use — your email tool — or it's gone. The clean way to handle this on beginner tools is to let your email platform own the form.
In MailerLite (or your email tool), create a form or embed, copy the code it gives you, and have the AI drop that into your build in place of its own email box:
Replace the email sign-up in this build with my email tool's form instead of a plain box, so subscribers go straight into my list. Here's the embed code from [MailerLite / my email tool]: [paste the embed code]. Keep the same look and the same thank-you message after someone signs up.
Some rung-one previews won't accept an outside form. Two easy fallbacks: (1) rebuild the page on rung two, where connecting an email tool is a built-in feature, or (2) have the sign-up button link straight to a MailerLite landing page you made for the offer. Either way, the golden rule holds: the email must reach your list, not just your tool.
What NOT to build on beginner tools
Vibe coding is safe for the projects in this course. It is not the place for anything holding sensitive information. On rung-one and rung-two tools, never build something that stores:
- Passwords or logins you're responsible for securing. Real accounts need real security you can't verify here.
- Payments or card details. Use a proper checkout (Stripe, a store platform) — never a form you built yourself.
- Health, financial, or other private personal data. If a leak would harm someone, it doesn't belong on a beginner build.
Ask yourself: "If this page's contents were posted publicly tomorrow, would anyone be harmed?" If yes, don't build it on these tools. Collecting an email for a quiz result — fine. Storing a client's banking details — never.
Back up your work
Two habits mean you never lose a build:
- Keep the conversation. Your chat history is your project file — it holds every decision and can rebuild the thing. Don't delete it.
- Export the code. Ask the AI to give you the full code and save it in a file, even if you can't read a line of it. It's your insurance: "Give me the complete final code for this as one file I can download and keep."
Your ship-it checklist
Before you call anything done, run these five. This page remembers what you've checked.
Tested on a phone. Opened it on my actual phone and tapped every button — not just the desktop preview.
Emails reach my list. Did a real test sign-up and confirmed the address landed in MailerLite — not stuck in the tool.
Nothing sensitive stored. No passwords, payments, or private personal data living on this build.
The link works from the outside. Opened the public/shared link in a private browser window — not just my editor — and it loads clean.
Backed up. Kept the conversation and exported the final code to a file I've saved somewhere safe.
Five checks, then post the link. Done and live beats perfect and hidden — you can always improve it next weekend with one more D.R.I.V.E. loop.