Edgenivo Logo

GitHub and Next Steps

In a handful of videos, we went from a blank prompt to a live website at a custom domain. With a working contact form. With a database. With email notifications. All without writing a line of code.

Time to talk about what you can do from here.

Browse other integrations

Go to Settings > Integrations in v0. We've already used Supabase, but the same flow connects you to:

  • Other databases if Supabase isn't your thing
  • Stripe, if you ever want to actually sell plants and collect money

Stripe in particular is worth knowing about. The day Green Thumb Goods becomes a real business is the day you'd integrate Stripe and let v0 wire up checkout, products, and payments the same way it wired up the contact form.

Back the project up to GitHub

Open the Project menu (...) > Settings > GitHub and select Connect. From there:

  1. Under Git Scope, pick the GitHub account or organization that will own the repo.
  2. Enter a Repository Name (call it whatever you want, like green-thumb-goods-website).
  3. Select Create Repository. v0 creates a private repository and pushes the project's files into it.

Now every file v0 generated lives in a real GitHub repository, with its full history. From here on, that repo is the source of truth for the project's code, so treat it with care. Delete it and the code may be gone for good. The branch menu next to Publish opens the branch on GitHub whenever you want to browse the code.

Why bother with GitHub?

Two reasons. First, your code gets real version control, with every change recorded in Git. Second, it opens the door to collaborating with developers later. If you ever want a friend to help customize the code, GitHub is how they'd join in.

Where to go from here

The site is real, but it doesn't have to stay where it is. v0 isn't a one-shot tool. It's a place you keep coming back to.

  • Add new features with prompts: a blog, a newsletter signup, a plant care quiz.
  • Roll back if a change goes sideways. Versions never go away.
  • Iterate on copy any time the season changes or you've got a new product.
  • Edit the GitHub repo if you want to dig into the code itself someday.

You started this course never having built a website. Now you have one. Domain, database, email, source code, all wired up and running. Pretty slick, right?

Was this helpful?

supported.