xp0
← Writing
xp0Building This Site in Four Hours:v0 as an Experience‑First ToolHow building experiencefirst.design with v0 validated every princip...22 May 2026experiencefirst.design

Building This Site in Four Hours: v0 as an Experience‑First Tool

How building experiencefirst.design with v0 validated every principle in the manifesto — and why that matters for personal brand sites.

This website took less than four hours to build.

Not four hours to get a basic landing page live. Four hours to ship a fully themed manifesto site with dark mode, accent colour switching, downloadable PDFs in multiple formats, blog posts with share-to-LinkedIn functionality, and logo export in SVG and PNG.

The tool was v0.

And the process was a live validation of every principle in the Experience‑First Manifesto.

The Problem with WordPress and Cursor

Let me be clear about the use case: a personal brand website.

Not a SaaS product. Not an enterprise application. A site that communicates ideas, establishes credibility, and provides a polished digital presence.

For this use case, the traditional options fail in predictable ways.

WordPress: Features Over Experience

WordPress gives you everything. Themes. Plugins. Customisation panels. Page builders. SEO tools.

But the experience of building with WordPress is fragmented. You're constantly context-switching between:

  • Theme settings
  • Plugin configurations
  • The block editor
  • Custom CSS panels
  • Database options

The cognitive load is immense. The mental model is "assemble features until it works."

This directly violates the first value: Experiences over Features.

WordPress ships features. It does not design the experience of using them together.

Cursor: Power Without Guardrails

Cursor, as an AI-augmented IDE, is powerful. It can generate code, refactor, and explain.

But for a personal brand site, Cursor presents a different problem: it assumes you want to be a developer.

You need to:

  • Set up a project structure
  • Choose a framework
  • Configure build tools
  • Manage dependencies
  • Handle deployment

Cursor gives you control. But control without clarity is just complexity.

This violates the third value: Clarity over Cleverness.

Cursor is clever. It can do remarkable things. But for someone who wants a personal site, not a coding project, that cleverness becomes a barrier.

v0: Experience as the Product

v0 approaches the problem differently.

It doesn't ask you to assemble features. It doesn't assume you want to manage infrastructure. It designs the experience of building a website.

Here's what that looked like in practice.

The First Hour: From Concept to Live Site

I described what I wanted: a manifesto site with values, principles, and a hero section.

v0 didn't give me a template. It gave me a working implementation.

Not wireframes. Not a style guide. A deployed, interactive site with proper typography, spacing, and semantic structure.

This is Principle 8: Prototype to learn, validate to decide.

Opinions do not scale. Evidence does. Within minutes, I had evidence — a real artifact I could evaluate, share, and iterate on.

The Second Hour: Theming Without Configuration Panels

I wanted dark mode. And accent colour options.

In WordPress, this would mean:

  • Finding a theme that supports dark mode
  • Installing a colour customisation plugin
  • Testing compatibility
  • Debugging CSS conflicts

In v0, I described the behaviour I wanted.

The implementation appeared. CSS variables. Theme provider. Toggle component. All wired together.

This is Principle 5: Application logic must not dictate organisational reality.

v0 didn't force me into its opinion about how theming should work. It adapted to what I needed.

The Third Hour: PDF Generation

I wanted visitors to download the manifesto as a PDF. In two formats:

  1. A 20-page LinkedIn carousel for social sharing
  2. A foldable A4 brochure for printing

In WordPress, this would require:

  • A PDF plugin
  • Custom template configuration
  • Probably a premium tier
  • Definitely compromises on formatting

In Cursor, this would require:

  • Researching PDF libraries
  • Understanding their APIs
  • Handling font embedding
  • Managing colour conversion between CSS and PDF colour spaces

In v0, I described the formats I wanted.

There were iterations. The first attempts had colour issues — the browser returns lab() colours from computed styles, not the oklch() values in the CSS source. v0 diagnosed the problem, added a colour converter, and fixed it.

This is Principle 7: Design for recovery, not perfection.

Errors happened. The system made them understandable, visible, and recoverable. I didn't need to debug PDF rendering internals. I described the problem, and v0 solved it.

The Fourth Hour: Blog Infrastructure

I wanted:

  • Markdown-based blog posts
  • PDF download for each post
  • Share to LinkedIn functionality
  • A logo download option on the homepage

Each feature appeared as I described it.

The blog posts render from markdown files with frontmatter. The PDF generator respects the current theme. The LinkedIn share button constructs the proper URL. The logo exports in both SVG and PNG, using current theme colours.

This is Principle 10: Friction anywhere degrades trust everywhere.

Setup, configuration, and integration are as important as core functionality. v0 treats them as first-class concerns, not afterthoughts.

Mapping the Experience to the Manifesto

Let me be explicit about how this experience validated the manifesto's values.

Experiences over Features

v0 didn't give me a feature list to configure. It gave me a working experience to evaluate.

I never thought about "what plugins do I need." I thought about "what should this feel like."

Customer Control over Product Control

v0 adapted to my requirements. It didn't force me into a template or a prescribed workflow.

When I wanted unusual PDF formats, it built them. When I wanted theme-aware exports, it implemented them.

The product bent to my needs. I didn't bend to its assumptions.

Clarity over Cleverness

Every change was visible immediately. The preview updated in real-time. Errors appeared with context.

When the PDF colour conversion failed, the error message pointed directly to the issue. I didn't need to understand the internals of OKLCH to LAB conversion. I just needed to describe what I expected.

End-to-End Journeys over Isolated Interfaces

v0 didn't just build pages. It built the complete experience:

  • The site itself
  • The deployment
  • The theme switching
  • The PDF exports
  • The social sharing
  • The logo downloads

Every touchpoint was designed, not just the core interface.

Why This Matters

The Experience-First Manifesto argues that:

Experience is the product. A product is not complete when it works — it is complete when it earns trust and confidence through use.

v0 is not complete because it generates code. It's complete because using it feels like building something, not configuring something.

For personal brand sites — where the goal is to communicate ideas, not to master a technology stack — that distinction is everything.

WordPress gives you features and asks you to assemble an experience.

Cursor gives you power and asks you to manage complexity.

v0 gives you an experience and asks you to refine it.

The Real Test

Four hours.

A fully themed manifesto site. Blog infrastructure. Multiple PDF export formats. Social sharing. Logo downloads. Dark mode. Accent colours.

Not because the features were easy to configure.

Because the experience of building was designed.

That's the difference.

And that's why v0 isn't just a tool for building websites.

It's a proof that the Experience-First approach works — not just for the products we build, but for the tools we use to build them.