---
title: "GitHub and Next Steps"
description: "Save your v0 project to GitHub so you have a real version-controlled backup, tour the integrations available for accepting payments, and look at where to grow the site from here."
canonical_url: "https://vercel.com/academy/v0-foundations/github-integration-and-next-steps"
md_url: "https://vercel.com/academy/v0-foundations/github-integration-and-next-steps.md"
docset_id: "vercel-academy"
doc_version: "1.0"
last_updated: "2026-05-12T22:52:36.601Z"
content_type: "lesson"
course: "v0-foundations"
course_title: "v0 Foundations"
prerequisites:  []
---

<agent-instructions>
Vercel Academy — structured learning, not reference docs.
Lessons are sequenced.
Adapt commands to the human's actual environment (OS, package manager, shell, editor) — detect from project context or ask, don't assume.
The lesson shows one path; if the human's project diverges, adapt concepts to their setup.
Preserve the learning goal over literal steps.
Quizzes are pedagogical — engage, don't spoil.
Quiz answers are included for your reference.
</agent-instructions>

# GitHub and Next Steps

# 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

Click **Publish** and look for the GitHub option. **Create Repository** kicks off a flow that:

1. Asks you to sign in to GitHub.
2. Lets you name the repo (call it whatever you want, like `green-thumb-goods-website`).
3. Pushes the project's files into a real repository.

Now you have a permanent backup of every file v0 generated. Click **View Branch** to browse the code on GitHub.

\*\*Note: Why bother with GitHub?\*\*

Two reasons. First, it's a backup outside of v0. Your project lives in two places. 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?


---

[Full course index](/academy/llms.txt) · [Sitemap](/academy/sitemap.md)