Webwright is an independent, vendor-neutral field guide to the craft and business of building for the web. It gathers the working knowledge a small team accumulates over years of shipping sites and software — how good design decisions get made, how the web actually runs under the hood, and how the freelance and outsourcing economy that powers so much of it fits together.
This guide grew out of a simple observation: the web has always been built at the edges. Not only in famous studios and platform companies, but in one-person shops, two-person teams, and small collectives — often working across borders, stitching together hosting, domains, design, and code for clients who just want something that works. Webwright documents that everyday craft in plain language.
What this guide covers
Every article here is evergreen and practical. The territory splits into a few natural neighbourhoods:
- The craft of web design — layout, typography, colour, and the discipline of accessible, responsive interfaces.
- Web development — how the front-end and back-end actually cooperate, from HTML to databases.
- Web hosting — shared, VPS, and cloud hosting demystified, including the old Linux-versus-Windows question.
- Domain names — registration, DNS, and the quiet infrastructure that makes addresses resolve.
- Content management systems — choosing the right editing platform for a project.
- Web promotion and SEO — earning visibility honestly and durably.
- Offshore software development and outsourcing web projects — how the global delivery model works, and how to buy it well.
- The freelance web career — the business behind the craft.
Why craft still matters
Tools change constantly; the fundamentals barely move. A page still has to load fast, read clearly, work on a phone, survive a flaky network, and remain usable for someone navigating with a keyboard or a screen reader. The W3C Web Accessibility Initiative has spent decades codifying that last point, and it remains one of the most reliably ignored — and most rewarding — parts of the discipline.
Underneath the fashions, the web platform itself is remarkably stable and well documented. The MDN Web Docs reference is the closest thing the field has to a shared textbook, and Google's web.dev collects the performance and quality guidance that separates a professional build from an amateur one. Webwright leans on those foundations rather than chasing whatever framework is trending this quarter.
Being found is part of the build
A site that nobody can reach is unfinished, however polished its pages look. People commissioning web work often discover that only after launch, when the thing exists but its audience does not arrive. Being found is part of the build because it begins with choices made during the build: a structure that can be followed, headings that name the subject, and pages that answer a real need plainly.
That makes web promotion and SEO less a separate trade performed at the end than a continuation of the same craft. Clear architecture helps machines interpret what people already understand; honest writing gives each page a reason to exist; technical health lets it load, render, and remain available. The Moz beginner's guide to SEO maps the larger discipline, but the foundation is ordinary workmanship. Visibility is not a coating applied by a specialist. It is evidence that the site was built to be reached.
Design, code, and delivery — one continuous craft
One of the recurring themes of this guide is that design, engineering, and delivery are not separate jobs handed between silos. In small teams they are the same conversation. The person choosing a colour palette is often the person writing the CSS, configuring the server, and explaining a hosting invoice to the client. Understanding the whole pipeline — from a domain registration to a deployed, indexed, maintainable site — is what turns a hobbyist into a professional.
That end-to-end view is also what made the offshore delivery model possible. A great deal of the world's routine web and software work is built by distributed teams, and India in particular became a hub for that craft. We treat offshore development as an industry to understand rather than a pitch to make: what it does well, where it goes wrong, and how a buyer keeps a remote engagement healthy.
How to use Webwright
Read it like a field guide, not a course. Each article stands alone and answers a real question a maker or buyer is likely to have. Start wherever your current problem lives — a slow site, a hosting decision, a first freelance contract — and follow the internal links outward. Everything here is written to be as useful in five years as it is today.
Ready to dig in? A good starting point is The Craft of Web Design, or if you are evaluating a build partner, Outsourcing Web Projects.
A note on longevity
Websites are unusual artefacts: they are simultaneously living services that need constant care and historical records that accrue value over time. A page that has answered a question well for a decade carries a weight no new page can buy. That is why so much of this guide returns to durability — choosing standards over trends, writing clearly, and maintaining what you ship. The web rewards patience more than novelty, and the makers who understand that build things that are still working, and still ranking, long after the fashionable rebuild would have been forgotten.