01
Speed
Kilobytes instead of megabytes. No theme engine, no plugin queue, no render-blocking third party to ship.
How we build
A hand-coded website is one written directly in HTML, CSS and JavaScript, with no content management system, theme engine or page builder generating it. Every build here starts as an empty file, and nothing goes into that file the project hasn't earned. Sometimes that means five files and a contact form. Sometimes it climbs all the way to a real application. Either way we build it, and either way we run it for you.
The method
From an
empty file.
Line one
The normal way round is to start with everything. You pick a platform, and before a single word of your site exists you have inherited a theme, a plugin queue, a database, an admin panel and a build step — then you spend the project subtracting, disabling and overriding your way back toward what you actually wanted.
Starting empty inverts that. There is no default to fight, nothing arrives that nobody chose, and every kilobyte on the page is there because someone decided it should be. The case for the blank file is in the blog; this page is what happens after it.
The ladder
From that empty file there are five rungs, and a project climbs only as far as it has a reason to. Structure is HTML and CSS — a page that reads, ranks and loads instantly. Behaviour is JavaScript, written for this one site. Server is functions: forms, email, payments, with nothing to patch. Data is a real database behind the page. Application is accounts, admin tooling, the whole thing.
Most sites never leave the first rung, and that is the point. We build whatever rung the job actually needs — and we run it for you either way. You send a change, we make it. There is no dashboard to learn and no login to lose, and if you ever leave, your domain, your content and a copy of your files come with you.
The upside
01
Kilobytes instead of megabytes. No theme engine, no plugin queue, no render-blocking third party to ship.
02
No admin panel to brute-force, no plugin stack to patch, and on a static build no database to breach.
03
The markup is written, not generated, so a contrast or focus problem is one line to correct, not a theme to fight.
04
Real HTML, real URLs and real headings are what crawlers and answer engines read best. Nothing is in the way.
05
HTML, CSS and JavaScript don't reach end of life. Nothing breaks because a plugin author stopped maintaining it.
06
No per-plugin licences, no per-seat add-ons, no upgrade forced on you because a dependency moved on.
07
Nothing is bent to fit a template, because there isn't one. The layout follows the content instead of the reverse.
Benefit 1 of 7
The arrangement
We do. The studio builds your site, hosts it and maintains it, and you never log in to anything. You send a change — new copy, a new photo, a whole new page — and we make it. That is the trade: you don't get a dashboard, and in exchange you don't get a dashboard to learn, a password to lose, or a plugin update that took the site down at two in the morning.
The counterweight is that none of it locks you in. The domain is registered in your name. The content is yours. If you ever decide to go elsewhere you get a copy of your site files that any developer can host, plus a grace period to move hosting without the site going dark.
The other side
There are three, they are real, and none of them is a surprise once it is said out loud.
That the files are written by a person in HTML, CSS and JavaScript rather than generated by a CMS, theme or page builder. Nothing is on the page that somebody didn't put there. The full case is in the blog.
No, and that is the arrangement rather than a gap. We own the maintenance: you send a change and we make it, usually the same day. No dashboard, no login, no plugin updates waiting for you on a Monday.
Then the build climbs a rung. Serverless functions cover forms, email and payments; a real database goes in when the content is genuinely dynamic; a full application goes in when that's the job. We build it and we still run it for you.
Usually more to build and usually less to keep. There are no plugin licences, no per-seat add-ons, and no forced migration when a dependency is abandoned — the costs that quietly outgrow the build on a platform site.
You take a copy of your site files that any developer can host, and a grace period to move hosting without the site going dark. The domain was always registered in your name and the content was always yours.
Than picking a template, yes. Than bending a template into a design it was never meant to hold, rarely — that is where platform projects actually lose their weeks, and it is the part nobody estimates.
One empty file
Let's build
yours.
I don't think hand-coding is a moral position. It is just the only way I have found to hand somebody a site with nothing in it they didn't ask for — and the site you are reading is the evidence, so here is how it works and here is what it looks like. The blog is where I show the working, the FAQ covers the money and the maintenance, this is me, and the front door is open. Got a project that starts at rung one? Start a conversation.
Adam Hoidahl The Better Website
The Better Website is a one-person web design studio in Raleigh, NC, serving the Triangle and clients nationwide. Adam Hoidahl hand-codes every site in plain HTML, CSS and JavaScript — no WordPress, no page builders, no CMS.
© 2026 The Better Website · Privacy