Publish to Vercel
Station 2 / 2
BMFeedback

GitHub & Vercel · 02 / 02

Publish to Vercel

Put your project online with a public preview link. Import your GitHub repository, deploy, then test the main action on the live site.

Publish to Vercel

What this is

Vercel is a public preview host. It takes your GitHub repository and gives your project a live URL anyone can open. It is shared by both Vibe 101 and Vibe 102, and it is the strongest proof when accounts and time allow.

Why it matters

A live URL lets a tutor, friend, or reviewer open your build without any setup. Deployment is strong proof, but it is not mandatory. If Wi-Fi, accounts, or time block you, a screenshot plus a clear explanation is still a valid finish.

What to do

Deploy the repository

  1. Sign in to Vercel with GitHub.
  2. Import your project repository.
  3. Accept the detected framework settings unless your tutor says otherwise.
  4. Deploy.
  5. Open the live URL.
  6. Test the main action again on the live site.

Vibe 102 live test

If you built a localStorage app, prove the data survives on the live site:

  • Add an item.
  • Edit or update an item.
  • Delete an item.
  • Refresh the page.
  • Confirm the data still appears if localStorage is expected.

If deployment blocks you

Do not lose your finish over a failed deploy. Capture a screenshot or local preview and give the 60-second explanation instead. That still counts as minimum proof.

Common mistakes

  • Changing framework settings you were not asked to change.
  • Deploying but never opening the live URL to confirm it loads.
  • Claiming localStorage works on the live site without refreshing.
  • Treating a failed deploy as a failed session.

Next step

Record your strongest proof back on the Proof and Sharing page.