Free — no signup required
The Learning Hub
Think of this as a digital textbook on how websites actually get built — one continuous story in eighteen chapters, from "what is a website?" all the way to launch, security, and keeping a live site healthy for years to come. Every chapter pairs a beginner explanation with real business examples, common mistakes, tools, and a hands-on exercise.
18 chapters
Chapters
Built to be worked through in order — each chapter quietly assumes the ones before it — but every chapter also stands on its own if you already know the basics.
- Chapter 1What is a Website?Before writing a line of code, every builder needs to understand what actually happens when a website appears on a screen — domains, hosting, browsers, servers, and the request-response cycle that ties them all together.
- Chapter 2HTML — The StructureHTML (HyperText Markup Language) describes what each piece of content is — headings, paragraphs, images, links, buttons, forms — without touching how anything looks or behaves. Every other phase builds on top of this structure.
- Chapter 3CSS — The Visual DesignCSS (Cascading Style Sheets) controls every visual and layout decision on a website — colours, fonts, spacing, positioning, and how a page reflows across different screen sizes.
- Chapter 4Tailwind CSS — Faster StylingTailwind CSS is a "utility-first" framework that lets you style elements with small, single-purpose classes directly in your HTML instead of writing custom CSS rules — faster to write, and more consistent because every class pulls from a fixed design system.
- Chapter 5JavaScript — InteractivityWithout JavaScript, a website can be read but can’t respond. JavaScript listens for events — clicks, key presses, form submissions — and changes the page in response, which is the fundamental mechanism behind almost all interactivity on the web.
- Chapter 6React — ComponentsOnce a site grows past a handful of pages, copying the same navigation bar or pricing card into every file becomes unmanageable. React lets you build a website out of components — small, self-contained, reusable pieces of interface defined once and reused anywhere.
- Chapter 7Website PagesOnce you can build, style, and add interactivity, the next question becomes strategic rather than technical: what pages does a real website actually need, and what job does each one do?
- Chapter 8Forms and User InputA beautifully designed website that never asks anything of its visitors will rarely generate business on its own. This phase is about designing forms that people actually finish, not just forms that technically function.
- Chapter 9Backend BasicsEverything covered so far happens in the browser, on the visitor’s own device — the frontend. The backend is everything that happens elsewhere: on a server, out of the visitor’s sight, handling the logic, storage, and processes a website needs but never directly shows.
- Chapter 10DatabasesA website without a database can only ever show the same fixed content to everyone. A website with a database can remember: a customer’s booking, a user’s saved preferences, or thousands of product listings that update independently of the website’s code.
- Chapter 11APIsNo website exists in total isolation. APIs (Application Programming Interfaces) are the standardized way software systems communicate with each other, letting a website tap into powerful, specialized capabilities without building them from scratch.
- Chapter 12SEO — Getting FoundSEO (Search Engine Optimization) is the practice of structuring and writing a website so search engines can understand it, trust it, and rank it well. It’s a combination of technical correctness, content quality, and user experience working together.
- Chapter 13Performance — SpeedSlow websites lose visitors before they ever see the content, rank worse in search results, and quietly erode trust. Performance is the discipline of making sure a website loads and responds as fast as technically possible.
- Chapter 14AccessibilityAccessibility is the practice of building websites that people with a wide range of abilities and circumstances can actually use — and it routinely makes a site better for everyone, not just people with disabilities.
- Chapter 15SecurityA website that looks professional but isn’t secure is a liability, not an asset. Security is the practice of protecting a website, the data it collects, and the people who use it, from being compromised, stolen, or abused.
- Chapter 16TestingNo website should go live without being deliberately tested first — not casually clicked through once, but methodically checked against a real list of what could go wrong.
- Chapter 17DeploymentDeployment is the moment a website stops being a private project on a local computer and becomes a real, public, permanently-accessible destination on the internet — the practical bridge between "development" and "the website is live."
- Chapter 18MaintenanceA website is not a once-off project — it is a living business asset. A website left completely untouched after going live doesn’t stay perfectly still: it slowly degrades, content goes stale, and small broken details accumulate unnoticed.
What's inside every chapter
A consistent, hands-on structure
Beginner explanation
Real business examples
Visual diagrams
Common mistakes
Tools to use
Practical exercises
Next chapter & related topics
Ready to put this into practice?
If reading about it has you thinking about your own business's website, we build exactly this — fast, mobile-first sites for South African local businesses.