DevelopEd
develop-ed.com
Delivery Handoff
Project Handoff — the iziwerk marketing site
What was built, what the second round changed, what is still open, and the short path from finished to live.
See it live
On a client build a private preview link sits here, so you can walk the whole thing on your own phone before signing anything off. This one is public and has been since launch: iziwerk.com — and the build behind it is written up at the case study.
// before → after
01
What Was Delivered
Where this began: a product with no name, no identity, and nothing to point anyone at. Where it stands now: a live, indexed, on-brand marketing site — the identity, the copy and the build — shipped in under a day, and serving from its own domain since.
Pages
9 indexed
The pitch, the how, pricing, legals and a branded error page — all crawlable static HTML
Identity
"Terminal, warmed"
Warm-dark canvas, signature amber, a cursor-bar mark — chosen, not defaulted into
First load
Under 50 requests
Zero third-party calls — fonts and everything else served from the site's own origin
Ownership
Entirely yours
Plain portable code — no page-builder, no licence, no subscription, hostable anywhere
// in the box
02
What's Included
An identity, decided rather than defaulted into
A named direction — "Terminal, warmed" — instead of a palette picked at random: a warm-dark canvas, one signature amber that does all the work, Space Grotesk over JetBrains Mono, and a cursor-bar mark that types itself. One decision the whole site can be checked against, which is what stops page four drifting away from page one.
A design system built for you, not picked off a shelf
Every page written by hand against that one visual language — no theme, no framework, no page-builder underneath it. It holds together from a 375-pixel phone to a widescreen monitor, and it stays yours to extend.
Zero third-party calls, by construction
Fonts self-hosted, scripts and styles served from the site's own origin, nothing fetched from anyone else at runtime. That is what keeps the first load under fifty requests — and it means no visitor's data reaches another company just because somebody read the page.
A build with no moving parts to rot
Hand-authored HTML, CSS and vanilla JavaScript. No framework, no build step, no dependencies to patch. Nothing between the files and the browser, so the site cannot break because something upstream shipped a new major version while you were not looking.
Accessibility built in, not bolted on
Every text colour checked against contrast standards, the whole site operable from a keyboard, and motion reduced automatically for visitors whose devices ask for that. Mobile-first from a 375-pixel baseline up, rather than a desktop layout squeezed down afterwards.
Search-engine foundations
A distinct title and description on every page, a real sitemap and robots file, and structured company data — all of it in static HTML, so a crawler reads the same page a visitor does. Nine pages indexed, none of them waiting on JavaScript to have content.
// the round after launch
03
Round Two, Implemented
On a client build this section lists your review sheet, item by item, with what changed for each one. Here it is the round that followed launch — because a site that goes live in a day is not a site that stops changing on day two.
The story widened to two sides
The launch site pitched freelancers. Once the hiring side of the product existed, the copy and the page structure had to carry both audiences without either one reading as an afterthought — so the pitch was reworked rather than a second page bolted on beside it.
Hardened with a strict Content-Security-Policy
A policy that only holds if the site really does call nobody. It does, so the header went on — the one inline behaviour that would have needed an exemption was rewritten instead of exempted. A CSP full of allowances is a CSP that is not doing anything.
Reviews left in an honest empty state
The section is designed and built, and it stays empty until genuine reviews exist. I do not publish invented ones — fabricated reviews are illegal in the UK and across the EU, and a plain two-line quote from a real customer outperforms a polished fake anyway. This is the same rule every site I build holds, including my own.
// short list
04
What's Still Open
Every handover ends with the honest list rather than a clean one. On your project this is the short set of things only you can supply; here it is what is genuinely still outstanding on mine. A handover with nothing in this section is a handover that is not telling you everything.
01
Real reviews, when they exist
The section is built and waiting. It switches on the day there are genuine customer words to put in it, with their permission — and not one day earlier.
02
A second language, if the audience asks for one
Not built, because it is not needed yet. The page structure is ready for it, so adding one is a content job rather than a rebuild. Worth saying out loud so it never turns up later as a surprise.
03
The claims stay checkable
Zero third-party calls, the request budget and the indexed page count are all things that quietly stop being true if nobody re-checks them. They are gated on every change rather than trusted — the point of writing a number down is that somebody can hold you to it.
// from here to live
05
Path to Launch
- ✓Identity, copy and build — done. What you are looking at is the current state, not a staging snapshot from last week.
- ✓Gated before deploy — every internal link resolved, the request budget measured, contrast checked, and each page rendered at 375, 768 and 1440 and actually looked at. A green checklist nobody read is not a check.
- ✓Live on its own domain — deployed, then verified against what is really serving rather than against what was uploaded. Those are not the same thing, and the difference is where sites break.
- ✓Handed over — this document, the source, and the deploy path. On a client project the last step is a click-through together on real phones before we call it done.