Deploy and Share

You have iterated. The home page looks good. The branches page exists. The admissions page has a working-looking contact form. Now you make it live and put it in front of one real person.

1. Hit Publish

Inside the Lovable workspace, at the top right, you will find a button labelled Publish (sometimes called Deploy or Share).

Click it.

Lovable will:

1. Take a snapshot of your current preview.
2. Build a production version of it.
3. Deploy it to a public URL.

This takes 20-60 seconds. You will see a progress bar. At the end, Lovable shows you a URL like:

https://aurora-public-school.lovable.app

That URL is your project. It is live. Anyone in the world can visit it from any device.

2. Verify It Works

Open the URL in a new private/incognito tab (so you see what a fresh visitor sees, not your Lovable session).

Walk through the site:

• Home page loads. Hero photo shows up. Headline is readable.
• Click "Branches" in the navigation. The branches page loads.
• Click a branch — does it do anything? (Probably not for now — that's fine.)
• Click "Admissions." Fill in the contact form. Click submit. Does the success message appear?
• Scroll on every page. Anything that looks broken in the wild?

Now open the same URL on your phone. Pinch-zoom on photos. Tap navigation. Try to fill the contact form with the on-screen keyboard. Anything truly broken?

Fix anything truly broken with one more round of prompts. Don't chase polish. Fix only what would embarrass you in front of a real person.

3. Add a Custom Domain (Optional)

Lovable's .lovable.app URLs are fine for Project 1. But if this is for a real school you intend to actually use, you can attach a custom domain like auroraschool.in.

In Lovable's project settings:

1. Find "Custom Domain" or "Domains."
2. Enter the domain you bought.
3. Lovable shows you DNS records to add at your domain registrar (GoDaddy, Namecheap, BigRock, etc.).
4. Add those records. Wait 10-30 minutes.
5. The site now lives at https://auroraschool.in.

You can skip this for Project 1. We will set up a proper custom domain via Vercel in Project 2 anyway, where you have full control.

4. Share With One Person

This is the most important step in the entire project.

Pick one person — not five — who you trust to give you honest feedback. A spouse, a sibling, a parent, a close friend, a fellow trainee.

Send them this exact message (or your version of it):

"Hey — I built this in an afternoon. It's a school landing page. Could you spend 2 minutes clicking around and tell me what you think? Particularly: is anything confusing? Is anything off?"

URL: [your URL]

Wait.

When they reply, note down everything they say. Even the things you disagree with.

Common feedback you might get:

• "The hero photo is great but I can't read the white text on it."
• "Where do I apply? I see the steps but no button."
• "The phone number isn't on the home page. I had to dig."
• "I tapped the logo on mobile and nothing happened."
• "It looks nice but I have no idea what kind of school this is."

Pick the 2-3 most useful pieces of feedback. Spend 30 minutes addressing them in Lovable.

Then re-publish. Send the same person the same URL again (it stays the same):

"Made the changes. Thanks for the feedback."

5. Why This Matters More Than the Site Itself

The site you built in Project 1 is not the point. Most of you will never use this URL again after Project 2. The site is throwaway.

What is not throwaway is the cycle you just did:

1. Decided what to build.
2. Built it.
3. Shipped it.
4. Got real feedback.
5. Improved it.
6. Shipped again.

That cycle is the entire job. Every real developer does this same loop, on every project, every week, for their entire career. The cycle gets longer (months instead of days), the tools get fancier (real codebases, CI/CD, test suites), but the shape is identical.

You just did the cycle for the first time. From now on, when someone says "ship it," you know what that feels like.

6. Save Your Work

Before moving on:

1. Copy your URL somewhere safe — your notes file, a personal Notion, your phone. You will refer back to it.
2. Screenshot the home page of your published site. Phone size and desktop size. Save them in a folder named project-1/ somewhere on your computer.
3. Note down your final prompt count. Roughly how many prompts did you write? 30? 60? More? Useful for noticing your own growth in Project 2.
4. Write down 3 things you would do differently next time. Not about the site — about the process. Did you over-prompt? Did you waste time on details? Did you skip the share-with-one-person step? Write it down.

7. What's Next

You have a published site. You have feedback. You have a feel for what shipping is.

The next page (checklist.mdx) is a simple done/not-done checklist for Project 1. If everything is ticked, you are ready for Project 2.

In Project 2, the same school. The same content. But built on real code, hosted on real infrastructure, with real engineering practices. You will type things Lovable would have generated, and by the end of it, you will be able to explain every file in the project.

After that, Project 3 builds the actual school system: enrolment, attendance, exams, payments, multi-branch, multi-persona. Real software for a real domain.

For now — well done. Most people who say they want to learn to code never get to step "shipped a live URL." You did.