Vibe CodeBeginner20 min read

Build a personal website with v0 — no code needed

Design and ship a real, live personal website in one evening with v0 — no code. Plan before you prompt, iterate from generic to intentional, fill it with content that converts, and connect your own custom domain.

Build a personal website with v0 — no code needed

Build a Personal Website With v0 — No Code Needed

In this guide, you will design and ship a real, live personal website in one evening — no coding, no templates, no designer — using v0, Vercel's AI design tool. You'll describe what you want in plain English and watch it generate a working site, then learn the part most people skip: how to guide the AI so the result looks intentional instead of generic, fill it with content that actually gets you hired or found, and deploy it to your own custom domain. By the end you'll have a polished portfolio at a real URL, plus a repeatable process you can use to spin up any small site in an hour.

This tutorial is sponsored by v0.

Difficulty: ★☆☆☆☆ (If you can describe what you want in a sentence, you can do this — zero code required)
Required Tools: A free v0 account + your content (bio, projects, links) + optionally a custom domain
Updated: July 2026

Overview

The old way to get a personal website was a bad set of choices: wrestle a template that never quite fit, pay a developer four figures, or learn to code first. v0 removes the tradeoff. It's Vercel's AI design tool: you describe the site you want in plain English, it generates a real, functioning website — actual responsive layout, real components, deployable code — and you refine it by chatting. No template to fight, no invoice, no HTML.

But "describe it and it appears" hides where the quality actually comes from. Anyone can type "make me a portfolio" and get a generic result that looks like every other AI-generated site. The difference between a site that says "made in five minutes by AI" and one that says "this person has taste" is entirely in how you direct the tool — the specificity of your prompts, the references you point it at, the order you polish in, and the content you feed it. That direction is the real skill, and it's most of this tutorial.

This article does four things. First, it gets you oriented in v0 and — crucially — makes you plan your content before you prompt, because the biggest mistake is prompting into a blank mind. Second, it walks the generation and iteration loop: the first prompt that sets the foundation, then the conversational refinement that turns generic into intentional. Third, it covers the content and polish that actually matter for a portfolio — what to put in each section, and the design refinements that make recruiters and clients take you seriously. Fourth, it ships the thing: deploy to a live URL and connect your own custom domain, so you end with a real website, not a preview.

The honest goal: by the end of this article, you have a live personal website at a URL you can put on your CV and in your bio — one that looks deliberately designed, not AI-defaulted. "I'll make a website someday" is not the goal. "Here's my site" — pasted into a chat tonight — is.

Who This Is Useful For

  • Job-seekers, freelancers, and creatives who need a portfolio or personal site but have no time, budget, or coding skills
  • Anyone whose "website" is currently a LinkedIn URL or nothing, and who knows they're losing opportunities because of it
  • People who tried website builders (Wix, Squarespace) and found them slow, templated, or fiddly — v0's describe-and-generate approach is a different experience
  • Complete beginners who want a real, deployed site tonight — and a process they can reuse for a landing page, an event site, or a side project next week
  • What You Will Learn

    By the end of this article, you'll be able to do five things:

  • Navigate v0 and understand what it's doing — generating real, deployable web code from your descriptions
  • Plan your content and design direction before prompting, which is what separates a specific result from a generic one
  • Write the first prompt that gives your site a strong foundation, then iterate conversationally to make it intentional
  • Fill each portfolio section with content that actually converts a visitor into an opportunity
  • Deploy your site to a live URL and connect your own custom domain — ending with a real website, not a preview
  • What You Need

  • A free v0 account. Sign up at v0.dev — the free tier is enough to design and deploy a personal site.
  • Your content, gathered loosely. A short bio, 3–6 projects or work samples with a sentence each, your links (email, LinkedIn, GitHub, socials), and a photo if you want one. Rough notes are fine — you'll refine in place.
  • About an hour. Fifteen minutes to plan and prompt, thirty to iterate and add content, fifteen to deploy and connect a domain.
  • Optionally, a custom domain (like yourname.com). Not required to go live — you get a free vercel.app URL — but a custom domain makes it yours. You can buy one during the deploy step.
  • Step 1 — Understand What v0 Is (And Isn't)

    Thirty seconds of framing so you direct the tool instead of fighting it.

    v0 is an AI design tool that generates real web code from descriptions. You chat with it the way you'd brief a designer — "a portfolio with a hero, an about section, a projects grid, and a contact form; modern and warm with an indigo accent" — and it produces an actual, working website you can see, refine, and deploy. Under the hood it's writing genuine responsive code (the same kind a front-end developer would), which is why the output is a real deployable site, not a screenshot or a locked template.

    Two things follow from that, and they shape how you'll work:

  • It's conversational and iterative, not one-shot. You are not writing one perfect prompt and getting a finished site. You're having a back-and-forth — generate, look, adjust, repeat — exactly like directing a designer who turns edits around in seconds. Expecting the first output to be final is the most common source of disappointment; expecting to refine it in five rounds is the path to a great result.
  • The output is genuinely yours and genuinely live. Because v0 generates real code and deploys on Vercel, the end result is a real website at a real URL, and you can connect your own domain. This isn't a mockup you'll rebuild elsewhere — it's the actual site.
  • The mindset that works: treat v0 like a fast, talented designer you're directing — not a search box you're querying. The quality of what you get back is a direct function of the quality of your direction, which is why the next step is about you, not the tool.


    Step 2 — Plan Before You Prompt (The Step That Decides Quality)

    The single biggest mistake is opening v0 with a blank mind and typing "make me a portfolio." A vague brief produces a generic site — not because the tool is weak, but because you gave it nothing specific to build. Five minutes of planning is what makes the difference, and it's all offline.

    Decide four things before you type a word:

  • Purpose and audience. A portfolio to get hired reads differently from one to attract freelance clients or to be a personal hub. Who's visiting, and what do you want them to do — email you, hire you, see your work, read your writing? This decides everything else.
  • Sections. For most personal sites: a hero (your name, what you do, one line of positioning), an about section, a projects/work grid, and a contact section. Add or cut based on purpose — a writer needs a writing list; a designer needs big visuals; a developer needs a projects grid with links.
  • A design direction, in nameable terms. Not "make it nice" — specifics you can hand the AI: a vibe (minimal, bold, playful, editorial), a color feel (warm neutrals with an indigo accent; dark and high-contrast; soft pastels), and a typography feel (big and confident; clean and understated). This is where those reference sites from Step 1 turn into words.
  • Your actual content, gathered. Bio, project descriptions, links. You don't need final copy, but having your raw material next to you means you fill real content instead of leaving "lorem ipsum" that makes the site look unfinished.
  • This five-minute plan is the brief. Everything downstream — the prompt, the iterations, the result — is only as good as this.


    Step 3 — Write the First Prompt

    Now the plan becomes a prompt. The goal of the first prompt is a strong foundation to refine — not a finished site. Pack your Step 2 plan into it, because specificity is what separates a distinctive first draft from a generic one.

    A strong first prompt names the purpose, the sections, and the design direction in one go:

    
    A personal portfolio website for a [your role], [your name].

    Sections:

  • Hero: my name, the line "[your one-line positioning]", and a "Get in touch" button

  • About: a short bio section with a photo on the side

  • Projects: a grid of project cards, each with a title, one-line description, and a link

  • Contact: my email and links to LinkedIn and GitHub
  • Design: [minimal / bold / editorial], [warm neutrals with an indigo accent],
    [big confident typography]. Clean spacing, fully responsive, with a dark mode toggle.

    Notice what makes this work: it's the Step 2 plan, transcribed. The sections are listed, the design direction is in nameable terms, the positioning line is included. v0 generates from specifics, so specifics are what you feed it. A one-line "make me a portfolio" prompt would produce the beige average of every portfolio; this produces something shaped by your actual choices.

    Send it, and v0 generates your foundation — a real, responsive site matching your brief. It won't be perfect. That's expected and correct — the next step is where good becomes great.


    Step 4 — Iterate Conversationally Until It's Intentional

    This is where generic becomes yours, and it's the step people underuse. You refine by chatting — each message a specific, single-purpose edit — and v0 updates the site in seconds. The skill is giving clear, one-thing-at-a-time directions, exactly like art-directing a designer.

    Refine in this order — it's the sequence that compounds well:

    1. Layout and structure first. "Make the hero full-height." "Move the about photo to the left." "Make the projects a 2-column grid instead of 3." Get the bones right before the paint.
    2. Then typography. "Make the headings bigger and bolder." "Use a more elegant serif for headings, keep the body clean and sans-serif." Type carries more of the 'designed' feeling than people expect.
    3. Then color and detail. "Deepen the accent to a richer indigo." "Add more breathing room between sections." "Give the project cards a subtle hover lift."
    4. Then the extras. "Add a dark mode toggle." "Add smooth scroll to the nav links." "Add a subtle gradient behind the hero."

    Two rules make iteration effective:

  • One change per message. "Make the hero bolder, change the colors, add a footer, and fix the spacing" gives the model four targets and it'll do them unevenly. "Make the hero headline bigger and bolder" gives it one, and it nails it. Small, precise edits compound into a polished result; big vague ones produce mush.
  • React to what you see, in plain language. You don't need design vocabulary. "This feels cramped" → it adds spacing. "The accent is too loud" → it tones it down. "This looks generic" → ask specifically: "make the hero more distinctive with larger type and an asymmetric layout." Describe the problem or the fix in normal words; the tool translates.
  • Five to ten of these small rounds is the difference between an obvious AI default and a site that looks deliberately designed. This iteration is the craft — budget more time here than on the first prompt.


    Step 5 — Fill It With Content That Actually Works

    A beautifully designed site with placeholder text or weak copy fails at its one job. Now replace every default with real content — and write that content to convert a visitor into an opportunity, not just to fill space.

    Section by section, what actually works:

  • Hero: your name, your one-line positioning (Step 2), and one clear action. This is the 3 seconds that decide whether someone stays. Specific beats clever — "Product designer who makes fintech feel human" outperforms "Welcome to my creative world."
  • About: short, human, and concrete. A few sentences: what you do, who you do it for, and one thing that makes you you. Skip the resume recitation; give them a reason to remember you and a reason to reach out.
  • Projects/work: this is what recruiters and clients actually scan. For each: a clear title, one sentence on the outcome or your role (not just "a website" — "redesigned the checkout, cut drop-off 20%"), and a link to see more. Three strong projects beat eight weak ones — curate ruthlessly.
  • Contact: make it effortless. A visible email, the one or two links that matter for your field (LinkedIn, GitHub, Dribbble, X), and a clear "here's how to reach me." Every extra click between an interested visitor and contacting you loses some of them.
  • Feed this content to v0 by telling it directly — "change the about text to: [your bio]" — or edit in place. Getting real content in is what turns a design demo into your actual website.


    Step 6 — Deploy to a Live URL

    Your site exists in v0; now make it real on the internet. This is where a lot of "someday" websites die — people design and never ship. Don't. Deploying takes one click.

    In v0, click Deploy (or Publish). It deploys to Vercel — Vercel's own hosting, which v0 is built on — and gives you a live URL like your-site.vercel.app. That's it: your site is now live on the internet, accessible to anyone, for free. You can share that URL immediately.

    Two things worth doing right after your first deploy:

  • Open the live URL on your phone. The site is responsive, but see it on a real phone screen — check that the hero reads well, text isn't cramped, and buttons are tappable. Most portfolio visits come from links opened on phones (a recruiter clicking from an email, someone from your bio); the mobile view is often the first impression, not an afterthought.
  • Redeploy freely. Every time you refine in v0, just deploy again — it updates the live site. Your site is never "done"; it's a living thing you improve. Ship first, polish continuously.

  • Step 7 — Connect Your Custom Domain

    A vercel.app URL is real and shareable, but yourname.com is what makes the site feel like yours — and for a personal brand, that credibility is worth the small cost and 15 minutes.

    The flow:

    1. Get a domain. If you don't have one, buy it — Vercel can register it directly (easiest, one dashboard), or use any registrar (often cheaper). Pick something clean: yourname.com if available, or yournamedesign.com, yourname.dev, etc.
    2. Add it in the Vercel dashboard. Open your deployed project → Settings → Domains → add your domain. Vercel walks you through it.
    3. Point the DNS. If you bought through Vercel, this is automatic. If you used another registrar, Vercel shows you the DNS records to add there — copy them into your registrar's DNS settings. It's copy-paste, not code.
    4. Wait for it to propagate. DNS changes take anywhere from a few minutes to a couple of hours. Then yourname.com serves your site, with HTTPS handled automatically.

    Set up both yourname.com and www.yourname.com — Vercel will redirect one to the other, so visitors who type either land on your site instead of an error.


    Common Mistakes to Avoid

    Three patterns turn a great tool into a mediocre result.

    Mistake #1: Prompting into a blank mind. Opening v0 and typing "make me a portfolio" with no plan produces a generic site every time — the tool builds what you brief, and a vague brief is a generic brief. The five minutes of Step 2 planning (purpose, sections, named design direction, real content) is what separates a distinctive site from a default one. Plan offline; then prompt.

    Mistake #2: Accepting the first output. The first generation is a foundation, not a finished site — and stopping there is why so many AI-built sites look AI-built. The intentional look comes from Step 4's five-to-ten small iterations, especially on typography and spacing. Budget your time for refinement, not just generation.

    Mistake #3: Never actually shipping. The most common failure isn't a bad site — it's a good site that never goes live because it's "almost ready." Deploy early (Step 6), share the URL, and keep improving the live version. A real site at a real URL, imperfect, beats a perfect draft nobody can see.

    Going Further

    Go deep with the Vibe Coding series. This tutorial is the fast, standalone version. If you want the full craft — using reference sites to polish design, building more complex pages, adding real backends and payments — the Vibe Coding series walks through building and shipping multiple real apps with v0 end to end. This got you a site tonight; the series makes you fluent.

    Add pages as you grow. A single-page site is the right start, but v0 makes it easy to add a blog, a detailed project case study, or a dedicated contact page later. Just describe the new page and connect it to your nav.

    Reuse the process for everything. The plan → prompt → iterate → deploy loop you just learned isn't portfolio-specific. Use it for a landing page for a side project, an event page, a link-in-bio replacement, a small business site. Once the process is muscle memory, any small site is an evening's work.

    Keep it alive. A personal site's worst enemy is staleness — a projects list two years out of date reads worse than no site. Because updating is just another chat with v0 and a redeploy, make it a quarterly habit: new project, updated bio, ship. A site that's current is a site that's working for you.

    Key Takeaways

    Here's what you learned in this guide:

  • v0 generates real, deployable websites from plain-English descriptions — direct it like a fast designer, not a search box.
  • Plan before you prompt. Purpose, sections, a named design direction, and real content — five offline minutes that decide whether the result is specific or generic.
  • The first prompt is a foundation; iteration is the craft. Five to ten small, one-thing-at-a-time edits — especially on typography and spacing — turn an AI default into an intentional site.
  • Content is the job. Outcome-focused project descriptions and a specific one-line positioning convert a visitor into an opportunity; placeholder text wastes a great design.
  • Ship it live, imperfect. Deploy to a vercel.app URL in one click, view it on your phone, and keep improving the live version — a real site beats a perfect draft.
  • Your own domain makes it yours. Connect yourname.com in 15 minutes, set up www too, then put the URL everywhere — distribution is half the value.
  • Your challenge, restated for the road: spend five minutes planning (purpose, sections, design direction, content), then open v0, write one specific first prompt, and don't stop iterating until it looks deliberately designed — and deploy it live tonight, even if it's not perfect. The moment you paste your real URL into a bio or an email is the moment "I should make a website" becomes "here's my site."

    Learn AI, after work

    Track your progress, earn XP, and unlock more free tutorials in the AfterWork Bytes app.

    Open this tutorial in the app

    More AI tutorials