Go live

Our workshop homepage is ready to publish. We'll give it a public URL on Vercel, then check that someone can open it without signing in.

So far, we've viewed the website inside v0 while editing it. Publishing creates a deployment: a version of the application running on Vercel. The version serving the website's main address is called production.

Outcome

Publish Small Hours Studio and verify that its production URL opens the workshop catalog without requiring a sign-in.

Hands-on exercise 1.3

Check the version we're publishing

Open the same v0 chat we've used throughout this section. Check that the latest preview includes the edit from “Shape the Site.” The two workshops should still have their original prices and durations, and the page should identify Small Hours Studio as a demo.

If the preview includes a booking form or a payment button, correct that before publishing. Our first release is a catalog. We'll build the interest form in Section 4.

Requirements:

1. Publish the reviewed homepage to a Vercel project you can manage.
2. Use its provided vercel.app address for this exercise.
3. Check the website in a private browser window while signed out.
4. Save the production URL and the connected Vercel project name.

Publish from v0

Select Publish in the chat header. v0 and Vercel use the same account. Complete any sign-in prompts and choose the account or team where you'll manage the website.

Before confirming, review the Vercel plan associated with that account. v0 generation and Vercel hosting have separate usage limits. Vercel's Hobby plan is for personal, non-commercial use; keep this a fictional learning project if that's the plan you're using.

The first-publish flow guides us through the project setup. If it asks for a project name, use small-hours-studio or an available variation. Keep the connection to that project for later lessons.

Choose public access for this demo when the visibility step is available. Use the provided vercel.app domain, which is the website address. A purchased domain is optional and can wait.

Confirm Publish and watch the deployment progress. During the build, Vercel prepares the application code to run. Wait for the deployment to finish successfully before opening the website link. If it fails, use the troubleshooting steps below.

Find the address visitors will use

Open the published website and copy its production URL. v0's Publish panel shows the selected domain; we can also confirm it in the connected Vercel project's domain settings.

We'll keep two bookmarks:

Copying the chat address into a message would send someone to our work in v0. Use the production URL when sharing the website.

Try It

Open a private or incognito browser window. Without signing in, paste the production URL into the address bar. The Small Hours Studio homepage should load directly.

Select “Find your workshop” and read the catalog. Our reference content in complete/lib/workshops.ts has these values:

Print something good: 3 hours, $65, materials included.
A garden in a pot: 2 hours, $45, materials included.

Check those facts and the edit from lesson 1.2 on your deployed page. These lines describe the course's sample content; your site's layout can differ.

Open the same production URL on your phone, or narrow the private window. Confirm that the catalog fits and the main link works. Then close the v0 editor tab and reload the website. Vercel serves the deployed application independently of the editor.

The website asks visitors to sign in

First confirm that you copied the production domain from the Publish panel. A chat link or a protected preview may require an account.

If the production domain itself is protected, open Project menu → Settings → Vercel Project in v0 and review production visibility. Make this demo public where your permissions allow it, then repeat the signed-out check. A team policy may require the project owner's help; leave unrelated projects' protection settings unchanged.

Publishing fails during the build

Open the failed deployment's build logs. They describe what happened while Vercel prepared the app. Use Fix Build or Fix with v0 if offered, or paste the relevant error into the chat and ask v0 to fix it while preserving the catalog. Remove any sensitive values from copied logs.

Check the corrected preview before publishing again. Fixes may consume v0 credits. Repeatedly selecting Publish without changing the cause will usually reproduce the error.

Commit

Save the production URL beside the chat bookmark in your course notes. Record the Vercel project name and the account or team that owns it. We'll use that connection when we bring the website onto our computer.

This checkpoint is the published page and its saved address. We'll introduce Git commits in Section 2.

Done-When

• The production URL loads without a sign-in in a private window.
• Both workshops display the correct facts and the edit from lesson 1.2.
• The catalog fits at phone width, and “Find your workshop” works.
• The production URL and Vercel project details are saved with the chat bookmark.

Solution

Your homepage should now be published. Check it against these steps:

1. Open the reviewed v0 project and select Publish.
2. Confirm the Vercel project, choose public visibility where available, and keep the provided domain.
3. Publish and wait for a successful deployment.
4. Open the production URL while signed out and check the workshop catalog.
5. Save that URL and the Vercel project details in your notes.

Future edits need another publication step to reach this address. From v0, we'll use Publish → Publish Changes after reviewing an update. For now, keep this first release available while we set up a local workspace.