I Built and Deployed My Whole Website in 3 Hours - With Zero Code
I am not a developer. I've never shipped a website by hand, I don't write HTML for a living, and until this week the domain you're reading this on had nothing but a fresh WordPress install sitting on it.
Three hours later, it was live. The design, the pages, the newsletter, a custom 404, structured data for AI search - all of it. And I didn't write a single line of code.
This is the story of how, because I think most marketers and creators are still massively underestimating what's now possible in an afternoon.
What I actually shipped
Let me be specific, because "I built a website with AI" can mean anything from a template drag-and-drop to a real thing. Here's the real thing:
- A fast, lightweight site with a distinct terminal / command-line aesthetic - dark theme, monospace, the works.
- Eight pages (home, about, blog, notes, projects, tools, work, newsletter) sharing one clean design system.
- A working newsletter with signup forms and source attribution built in.
- A custom 404 page, a light/dark toggle, and a mobile menu.
- Proper SEO and GEO foundations: meta tags, canonical URLs, a sitemap, an RSS feed, and JSON-LD structured data so search engines and AI engines understand who I am.
- The whole thing weighs under 100KB and is fully crawlable.
And the part I'm most excited about: I can now push changes to the live site straight from a chat - no logging into a dashboard, no dragging files around.
How the three hours actually went
It wasn't magic, and it wasn't one prompt. It was a conversation.
I started by showing Claude a website whose style I loved and saying, essentially, "make mine feel like this, but about me and my work in GEO and SEO." It built a working prototype I could look at in my browser. I reacted - bigger nav, add my photo, add social icons, make it responsive, give me a light mode - and it iterated each time. That back-and-forth is the whole trick. I wasn't specifying code; I was art-directing.
Then came the real decision: WordPress or a plain static site? We went back and forth on it honestly - I even hit a wall where one path (connecting WordPress directly) turned out to need something that doesn't exist yet for self-hosted sites. Instead of forcing it, we changed direction. Static site, hosted on Hostinger, uploaded as a simple set of files. Lighter, faster, and better for getting found by AI - which, given what I do, is the whole point.
Uploading was a zip file dropped into Hostinger's file manager. Minutes later, aashishkarki.com was live.
The last hour was the fun part: connecting the site to Claude Code so I can edit and deploy from a prompt. Now, when I want to publish a post or change a page, I don't touch a control panel - I describe the change and it happens.
What you actually need to do this
Here's the honest requirements list, because the tools matter and I want the next person to skip the guesswork. (I've written a full step-by-step setup guide covering every install and account - this is the overview.)
To ideate, design, and build
- A Claude plan and the Claude desktop app. This is where the whole design conversation happened.
- A clear reference or taste for what you want. You don't need design skills, but you need opinions.
To put it online
- A domain name and hosting. I use Hostinger; any basic plan serves a static site fine.
- A newsletter platform if you want one. I use beehiiv's free plan - it embeds in a few clicks.
To push changes from chat later (the fun part)
- Node.js installed on your computer. It's free, and it's what the tooling runs on.
- Claude Code - the command-line version of Claude - installed and logged in.
- An API token from your host, to connect the two.
A few things you'll notice are not on that list: you don't need to know how to code, you don't need a design background, and - despite what I assumed going in - you don't need Python or any heavy developer setup for this particular workflow. Node.js is the one genuine technical dependency, and installing it is a next-next-finish affair.
What surprised me
Three things.
First, how much of the value was in the decisions, not the typing. Should this be WordPress or static? How do you want empty pages to look before you have content? Do you need attribution tracking on the signup form? I was making product calls the whole time - the code just followed.
Second, how much it respected the goal. Because I care about being found in AI search, every choice bent toward that: static for speed, structured data for machines, clean crawlable HTML. The tool didn't just build a site; it built one aimed at my outcome.
Third, how fast "later" became "now." The gap between "I should have a website" and "I have a website" used to be measured in weeks and quotes from freelancers. For me it was an afternoon and no invoice.
The takeaway for marketers and creators
If you've been putting off your own site, your portfolio, your newsletter home - the excuse that you're "not technical" has quietly expired. The skill that matters now isn't coding. It's knowing what you want, having taste, and being willing to make decisions. Those are marketer skills. Creator skills. Your skills.
I went from a blank WordPress install to a live, fast, AI-optimized site with a working newsletter in about three hours. If you want the exact stack, I've broken down every install, every account, and every step so you can do the same without the trial and error.
And if you want the next guide the moment it's out, subscribe to the newsletter. If you're building something similar, tell me what you're stuck on - I'll probably write about it.
cd ~/blog