How to Build a Writer Website Without Code: Full Guide
A writer website without code is one description away: your name, what you write, where to buy it, and how readers stay in touch. Zugo builds the site from that text, boots it in a sandbox to check it opens, and publishes it to a live address. A simple build takes about a minute.
The site is not the work and it should not consume the week. What it must do is stop a reader who liked one thing you wrote from disappearing before they can find the next one.
What is a writer's website actually for?
Converting a stranger into a subscriber. Everything else on the page is in service of that, including the books. A reader who buys once and leaves no address is a reader you meet again only by luck; a reader on your list is one you can reach on publication day.
That reframes the layout. The newsletter signup is not a footer element, it is the second most important thing on the page after the answer to "what does this person write". Put it where someone who has just finished reading your sample will see it.
The second job is credibility, and it is quieter than writers expect. Publications, awards, and representation belong on the page in a plain list, not in a paragraph of self-description. An editor scanning for whether to commission you wants a list.
The third job is availability. Journalists, ghostwriters, copywriters, and speakers get hired from their sites, and the single most common gap is not saying what you are open to. One line stating what work you take costs nothing and changes the enquiries you get.
What kind of writer are you building for?
The structure differs meaningfully by trade, and choosing before you prompt saves several rounds of editing.
| Writer | Page leads with | Money comes from |
|---|---|---|
| Novelist | Current book, buy links | Retail sales, list for launches |
| Nonfiction author | Idea and credibility | Books, speaking, consulting |
| Freelance journalist | Clips and beats | Commissions |
| Copywriter | Results and services | Clients hiring directly |
| Newsletter writer | The newsletter itself | Subscriptions, sponsors |
| Poet or essayist | The work, read on the page | Books, readings, teaching |
A novelist and a copywriter want opposite pages. One is a shop window for a finished object, the other is a proposal document. Building "a writer site" without picking a row is how you end up with something generic that serves neither reader.
What should the prompt say?
Name the trade, the current work, and the one action you want. Specific input produces something you edit rather than argue with.
Build a website for [name], a [novelist / journalist /
copywriter] who writes [subject or genre].
Sections:
1. Hero: my name, one line on what I write,
and a newsletter signup with one field.
2. Books: [N] titles with cover, one-paragraph description,
and buy links to [retailers].
3. Selected writing: [N] pieces with publication and year,
linked out.
4. About: two paragraphs, one photo, and what I am
currently working on.
5. Work with me: what commissions or projects I take,
and how to enquire.
6. Contact: email and social links.
Design: text-first, one serif for body copy, wide margins,
nothing that competes with the writing.
The design line does the most work in that prompt. A default template adds gradients, cards, and animation, all of which fight prose. Asking for restraint explicitly is the difference between a writer's site and a startup landing page with a book on it.
If starting from a blank prompt feels harder than editing, Zugo ships 25 templates and a portfolio template is a reasonable base. The blog guide covers the structure if you intend to publish on the site rather than link out.
How do readers actually join the list?
Connect the form to something that stores addresses. A form that appears to work and saves nothing is the most expensive bug on a writer's site, because you only discover it when you go to announce a book.
| Route | What you get | Trade-off |
|---|---|---|
| Supabase table | Subscribers as rows in a database you own | You export to your email tool |
| Resend notification | An email per signup | Fine early, noisy later |
| Existing newsletter provider | Sending, templates, and unsubscribes handled | An external embed on the page |
If you already write a newsletter somewhere, keep sending from there and use the site as the front door. If you do not, store addresses in your own Supabase project so the list belongs to you from the first subscriber. The newsletter signup guide covers the mechanics and the confirmation email that stops people wondering whether it worked.
Say what the newsletter is next to the field. "Occasional notes on what I am reading, once a month" outperforms "Subscribe" by a wide margin, because it answers the only question a hesitant reader has.
Should you sell books directly from the site?
Sometimes, and the honest answer depends on what you are selling. Retail links are frictionless and take a cut; direct sales pay better and make you the shipping department.
| What you sell | Route | Reality |
|---|---|---|
| Print books | Links to retailers | They handle stock and returns |
| Signed copies | Stripe one-off payments | You pack and post them yourself |
| Ebooks or PDFs | Stripe plus a delivery link | Good margin, needs file delivery |
| Paid newsletter | Stripe subscriptions | The most durable writer income |
| Workshops or coaching | Stripe plus a booking form | Highest value per hour |
Signed copies are the case where direct selling genuinely wins, because nobody else can supply them. For everything else, start with retail links and add direct sales when the demand is proven. The digital downloads guide covers file delivery if you sell ebooks.
What does it cost in credits and time?
A writer site is a normal single build. It becomes a multi-page platform if each book gets its own page and you add an essays archive.
| Action | Credits |
|---|---|
| Edit in chat | 3 |
| Single-page build | 6 |
| Multi-page platform, first three pages | 12 |
| Each page beyond the first three | 3 |
| Hi-Fi edit | 6 |
| Hi-Fi build | 12 |
Free gives 5 credits, which is enough to look around and short of the 6 a build costs. A published site starts on Pro at $25 a month with 200 credits, and Business is $99 a month. Hosting is included.
A simple build takes about a minute and a multi-page platform takes several minutes. Adding a new book later is one edit at 3 credits, which is the number that matters most: the site should cost you a sentence, not an afternoon, every time you publish.
Where does an AI builder stop for writers?
Three limits worth knowing before you commit.
It is not a publishing platform. If you want subscriber-only posts with per-post paywalls, comment threads, and a discovery network, a newsletter platform does that better today. Zugo can build gated content with Supabase across repeated edits, and that is a real project rather than one prompt.
It does not write the work. The builder produces structure and functional copy for a page. Your voice on the page is the reason a reader stays, and no generated paragraph substitutes for it. This is the one section of any writer's site you should write yourself, in full.
It is not a development team. A site that grows into a serialised fiction platform with accounts and payments is software. GitHub export hands a developer the real repository when that happens, because the project belongs to you.
Inside those limits you get a quiet, fast, text-first site that captures addresses and points at the books, built in an evening. Describe what you write at zugo.dev and see the first build.