v0 Turns Prompts Into Deployed Next.js Apps and Pull Requests
Vercel’s beginner guide presents v0 as a way to move from a plain-language prompt to deployed software inside the company’s development stack. The walkthrough argues that v0 is more than a website generator: it creates Next.js code, connects to AI and infrastructure services, publishes to Vercel, and can also import an existing GitHub repository, create a branch, and open a pull request for review.
v0’s beginner workflow has two parts
Vercel presents v0 as a path from a plain-language request to running software. The walkthrough demonstrates two versions of that path: creating a new AI-enabled event app from a prompt, then changing an existing marketing site by importing a GitHub repository, creating a branch, and opening a pull request with a Vercel preview deployment.
The opening example is a luxury watch event landing page for “Sonofalli.” The page includes event details, registration calls to action, and an AI-powered virtual try-on experience. The presenter says it was built “in just a few minutes” after being assigned the project by a boss, using v0 to turn the idea into “real software.”
You describe the app, agent, or website that you want, and then v0 generates the code and a live preview.
Vercel says v0 is not just a website builder. The presenter says it generates “real software using Vercel and Next.js,” can connect apps to AI and databases, can accept payments through Stripe, and produces code that developers can use and deploy. The walkthrough ties this to Vercel’s role as creator of the Next.js framework and says v0-built Next.js apps deploy on Vercel infrastructure, using the same code and secure infrastructure as companies including Under Armour, Stripe, and Notion.
In the interface, the prompt box asks, “What do you want to create?” A detailed prompt describes a single-viewpoint hero page for a luxury watch launch: a soft neutral background, editorial watch imagery, an AI virtual try-on, and a registration-focused layout. v0 then enters a “Thinking” state and breaks the request into implementation steps: the hero page, side-by-side layout, photo upload, four generated watch images, Gemini 2.5 Flash image preview through AI Gateway, and a 2x2 output grid.
The first build is an AI-enabled event app
The first project is a marketing task: build an event page for a product release party for a new watch called Sonofalli. The page is meant to create hype, encourage registration, and give visitors a virtual try-on experience.
The prompt asks for users to drag and drop or upload a photo of themselves. The app should then generate four images of the same person wearing the Sonofalli watch: a macro wrist close-up, a casual lifestyle shot, an elegant studio or editorial image, and a natural candid angle. The prompt specifies “Nano banana (google/gemini-2.5-flash-image-preview) via AI gateway” for image generation.
While v0 builds, the presenter opens Settings and then Integrations. The interface shows Vercel AI Gateway as an included integration. The presenter says v0 uses the AI SDK to build AI features and AI Gateway to provide access to hundreds of AI models automatically. The integrations panel also shows database and infrastructure options, including Upstash, Neon, Supabase, Amazon DynamoDB, Amazon Aurora PostgreSQL, Amazon Aurora DSQL, Groq, Stripe, and Blob. The presenter says these integrations allow users to build “real, full-stack, AI-enabled apps.”
Once the first version is complete, the virtual try-on is tested with an uploaded personal image. The preview moves through a “Generating your look” state and then displays a 2x2 grid of AI-generated images.
The editor view makes the generated application visible as code, not only as a preview. It shows a Next.js project structure with application files, components, API code, Tailwind CSS, and project configuration. The visible CSS includes the neutral background color and near-black foreground from the prompt. The presenter says v0 has taken the instructions and updated the code, and that the editor gives developers a way to review and edit what v0 created.
Publishing stays in the same flow
After the event page works in preview, the presenter shares it with the team before publishing. The Share menu includes visibility controls and a Copy Link button. The presenter says the shared preview is exactly what users will see once the page is public, so the team can review the same experience before deployment.
Publishing happens from a “Publish to the Web” modal with options for domain, visibility, v0 branding, and a “Publish to Production” button. Once published, the production deployment menu shows the app as ready and provides access to domain customization, Vercel inspection, analytics, and the live site.
The generated Vercel project dashboard shows deployment status, a generated .vercel.app domain, deployment settings, analytics, and deployment history. The presenter says inspecting the project on Vercel exposes analytics, errors, and a complete history of deployments for the v0 creation.
The final live site is shown in a browser with the event copy, RSVP link, virtual experience upload area, invitation-only language, and “Try Sonofalli on you” call to action. The app has been published to production and can be accessed publicly through the shared link.
Domain customization is also handled inside the workflow. In the Domains settings, the presenter edits the default domain from a generated Sonofalli watch page URL to a Sonofalli watch event URL. The interface then shows the new connected domain and a “Domain assigned successfully” message. The same page can now be accessed at the edited domain.
GitHub import turns v0 into a collaboration layer
The second project is not a new standalone app. It is an update to an already published marketing site managed by a development team through GitHub. The presenter says the update needs to happen as part of that team’s existing workflow.
In a new v0 window, the presenter chooses “Import from GitHub,” pastes a repository URL, and imports the repo. v0 recognizes that the repository is already connected to an existing Vercel project and offers to continue with that project. After import, the interface shows the marketing page for POPE watches inside v0.
The requested change is narrow: add a banner at the top of the marketing page directing visitors to sign up for the Sonofalli launch event, using the event landing page URL created earlier. While v0 makes the change, the presenter opens the Git panel. It shows that v0 has automatically created a branch for the chat, with status and recent activity. That branch is the mechanism for developers to review and test the changes before merging them into the main site.
Once v0 adds the banner, the preview shows a black announcement bar reading “THE SONOFALLI LAUNCH EVENT - SIGN UP NOW” above the existing page. The presenter then opens a pull request. The v0 interface shows an auto-generated PR title, “Add slim announcement banner above sticky header,” one commit, and an “Open Pull Request” button. After the PR is created, v0 shows a preview deployment as ready, with a PR number and controls to inspect, visit, or merge.
| Workflow | v0 action | Review path |
|---|---|---|
| New event app | Generates the app, AI try-on, deployment, and domain settings | Team reviews a shared preview before production deployment |
| Existing marketing site | Imports the repo, creates a branch, adds a banner, and opens a PR | Developers review in GitHub; others review the Vercel preview |
The presenter says the pull request is open on GitHub and, because the site is on Vercel, a preview build has automatically been created. Her summary of the second workflow is that the marketing update was made without opening an engineering ticket, while still giving developers a pull request inside their normal process.