• Feb 3, 2026
  • 4 min read

The First Websites I Built for Other People

Built in 2024, revisited now: what I made, and what I’d do differently today.

For years I’d only built websites for myself: a travel blog, then a technical blog. In 2024 that changed. People close to me kept mentioning their websites, and almost always with a complaint: too expensive, too slow, too hard to change, or not really theirs.

So I started building them. One at a time, each a little different.

The five

WhoWhat they hadWhat hurtWhat they got
A psychologista profile page on a booking marketplace$80 a month for one page, and the content wasn’t hersher own single-page Astro site
A real estate agent—competitors’ sites took about a second just to answera fast Astro site with a contact form and newsletter
A knitting cluba site on Firebase, domain at Google Domains (later Squarespace)an aging setup spread across providersthe site on Cloudflare Pages, same domain
A family craft shop—a place to show the worka photo-first Hugo gallery site
A local café—a menu people can open on their phonea small web menu

The sixth, a business site on hosted WordPress where one analytics script needed a paid plan, became its own post.

The process that kept repeating

By the third site, the steps were always the same:

  1. Inventory. What’s on the current site? Fetch the sitemap, run a link checker. The psychologist’s page had 53 links, 5 warnings and no errors: small enough to rebuild by hand, big enough to want a script.
  2. Get the content out. For hosted platforms that don’t export, a scraper that returns clean Markdown (I used Firecrawl) saved hours. Her page was in Turkish, so the content also went through a translation library before it went anywhere else.
  3. Pick a template that fits the content. A single page for a therapist, a listings layout for real estate, a gallery for craft work. Starting from a good open-source theme beat designing from scratch every time.
  4. Deploy a preview on a free pages.dev address and let them click around before anything changes on their real domain.
  5. Move the domain. Point the nameservers to Cloudflare (from Porkbun, Squarespace or Google Domains) and attach the custom domain to the site.
  6. Check before handing over. Sitemap and robots.txt answer, no broken links, HTTPS works, and search engines know the site exists.

Hosting cost after the move: zero. A static site on Cloudflare Pages, GitHub Pages or Firebase is free at this size. The only bill left is the domain.

What surprised me

People don’t know what to ask for. “I need a website” hides a dozen unknowns: what it’s for, who visits, what they should do next. For one person I made a short AI-generated presentation just to show options side by side. It was faster than any explanation.

The call to action matters more than the design. For the psychologist, the part worth getting right is how a visitor books: a booking link or a WhatsApp button. On the marketplace, they landed next to other therapists.

Editing is the real question. Sooner or later the question is “how do I change this?” With a static site the answer is “send it to me” or “edit this file”, and that’s fine for some people and a deal-breaker for others. (For the real estate site, I later built a small editor.)

What I’d do differently now

  • Write a one-page brief first: who it’s for, the one action a visitor should take, what success looks like. I did this in my head; it belongs on paper.
  • Agree who edits, and how, before choosing the stack. A Git-based CMS on top of the static site covers most “I just want to change the text” cases.
  • Add analytics and a contact path on day one, so after a month we can see whether the site does its job.
  • Make the repeatable part repeatable. Building sites one by one is slow. The inventory, link check, deploy and DNS steps are the same every time and should be a checklist, if not a script.

That last point is where this stopped being favours for friends. Once the same six steps work for very different people, it’s a process. And a process is something you can offer.

Takeaways

  • Ask what hurts (cost, speed, control) before talking about design.
  • Inventory and preview before you touch anyone’s domain.
  • Static hosting is free; the domain is the only bill.
  • The editing workflow decides whether the new site lasts.