Brochure
Brochure site you own
Last reviewed:
Get started
How to get started
Baseline
Time: About an hour for a first deploy if you already have accounts
Accounts before step 1: GitHub, v0 or Cursor, Vercel or Cloudflare Pages
Create a GitHub repository
Sign in to GitHub, create a new empty repository, and clone it to your machine. This repo is what you keep when the project is done.
Generate a Next.js brochure site
Open v0 or Cursor and prompt for a Next.js marketing site — home page, layout, and a few sections. Save the output into your cloned repo.
Iterate and commit
Fix copy, tighten layout, and commit as you go. You do not need a CMS on day one — add TinaCMS or Decap only when the client must edit copy without calling you.
Push and deploy
Push to GitHub and connect the repo to Vercel or Cloudflare Pages. Your site goes live from the branch you own.
Ownership
What you keep
You keep: One Git repository with your Next.js project
Cost shape: Free tiers available on v0, agents, and hosting; add a Git-based CMS only if the client must edit copy without you.
Named tools
Tools this path uses
- GitHub
- v0
- Cursor
- Next.js
- Vercel
- Cloudflare Pages
Not this one?
When to switch
Dynamic
Site with login, forms, or a CMS
For auth, member areas, forms, or editorial workflows that need a real database or CMS — not a plain brochure site.
Prototype
Visual preview first, then the repo
For people who want a visual preview first but refuse to rent the project forever — start in a hosted builder, then move to GitHub and Cursor.
WordPress
Stay on WordPress with EtchWP
For lifetime deal holders who still need WordPress — or teams not ready to leave PHP entirely. EtchWP on your host, Cursor via the Connector, data in core WordPress.
Quick answers
Frequently asked questions
- Can a beginner run this path?
- Yes, if you treat it as a loop: create a repo, prompt in v0 or Cursor, push, deploy. A Next.js brochure site is often the whole job. You do not need every tool on day one — follow the four steps end to end.
- Do I need a CMS on day one?
- No. Most brochure sites ship as static pages in the repo. Add TinaCMS or Decap only when the client must edit copy without you.
- Why Next.js instead of a static HTML export?
- Agents and hosted builders default to Next.js, and Vercel deploys it in one click. You can swap the framework later — the point is a repo you control, not a canvas subscription.