1.1 What Is a Digital Product Before designing or building anything, it's worth being precise about what category of thing is actually being made. Product Strategy 1.2 How the Internet Works A working mental model of packets, addresses, and routing — enough to reason clearly about everything built on top of it. Systems Architecture 1.3 Client–Server Architecture The foundational pattern underneath almost every digital product: one side asks, the other side answers. Software Architecture 1.4 Static vs. Dynamic Systems The single decision that most affects a product's cost, speed, and complexity — often made by accident. Software Architecture 1.5 Monoliths, Microservices & Event-Driven Systems Three ways to organize a backend's internal structure — each solving a different scale of problem. Software Architecture 1.6 Cloud & Edge Computing Where code actually runs — and why that location increasingly matters as much as the code itself. Cloud Infrastructure 1.7 DNS, Hosting & Domains The plumbing between a typed name and an actual running server — invisible when it works, catastrophic when it doesn't. Cloud Infrastructure 1.8 HTTP, HTTPS & the Request Lifecycle The actual conversation format every browser and server uses — and the encryption layer that keeps it private. Software Architecture / Security 2.1 Landing Pages A single page with exactly one job: move a specific visitor toward a specific action. Product / Marketing 2.2 Institutional & Organizational Websites Business, corporate, church, and school sites — different institutions, the same underlying informational job. Product / Design 2.3 E-Commerce Platforms Every screen is downstream of one non-negotiable requirement: correct, trustworthy transactions. Backend / Product 2.4 Blogs & Content Publishing Optimized for one repeated action: publishing new material without friction, indefinitely. Product / Content 2.5 News & Media Sites Content publishing under a much harder constraint: sudden, extreme, unpredictable traffic. Media / Editorial 2.6 Portfolios The work has to be the interface — everything else is scaffolding that should stay out of the way. Design / Product 2.7 Forums & Online Communities The technical build is the easy part — moderation and governance are the real product. Product / Trust & Safety 2.8 Social Networks Identity, graph, and feed — three hard problems that compound rather than add. Product / Infrastructure 2.9 SaaS Platforms Software rented, not owned — which changes almost everything about how it must be built. Product / Backend 2.10 Web Applications (General-Purpose) The broad middle category: interactive, stateful, but not yet specialized into any one business model. Software Architecture 2.11 Enterprise Applications Built for organizations, not individuals — which changes who the real user is at every step. Enterprise Architecture 2.12 CRM Systems A system of record for relationships — its entire value depends on data people actually keep updated. Business Systems 2.13 ERP Systems The system of record for the entire operational backbone of a business — inventory, finance, and people, unified. Business Systems 2.14 Dashboards & Internal Tools Built for an audience of one team — where speed of internal iteration matters more than external polish. Product / Data 2.15 AI Platforms & AI-Native Products A product category defined by a fundamentally probabilistic core component — which changes how reliability itself is defined. AI Engineering 2.16 Marketplaces Two customers, not one — and they usually want opposite things. Product / Trust & Safety 2.17 Booking & Reservation Systems Selling something that only exists once — a specific slot, seat, or room, at a specific time. Product / Backend 2.18 Learning Platforms (LMS) Success isn't measured by content delivered, but by knowledge actually retained. Education / Product 2.19 Streaming Platforms The product is continuous, uninterrupted delivery — any stutter is a direct, visible failure. Media / Infrastructure 2.20 FinTech Platforms Every design decision competes against the same constraint: regulatory obligation, not just user preference. Finance / Security 3.1 Navigation Systems The map a user builds of the whole product before they've used any of it. 3.2 Mega Menus A navigation escape hatch for products with too much structure for a normal dropdown. 3.3 Sidebars Persistent structure for products with enough depth that top navigation alone can't hold it. 3.4 Breadcrumbs A quiet but load-bearing answer to "where am I, and how do I get back up a level." 3.5 Hero Sections The first three seconds of a page's argument, compressed into one screen. 3.6 Footers Where the links that don't fit anywhere else quietly accumulate — for better or worse. 3.7 Buttons The smallest component in the library and the one users touch more than any other. 3.8 Forms & Input Validation Where the most user frustration per square inch of interface tends to concentrate. 3.9 Cards A self-contained unit for previewing something bigger — an article, a product, a record. 3.10 Accordions Progressive disclosure for content that's useful but shouldn't dominate the page by default. 3.11 Tabs Switching between mutually exclusive views without leaving the page. 3.12 Data Tables The densest, most information-critical component in most internal and admin products. 3.13 Charts & Graphs Turning numbers into a shape the eye can compare faster than a table of digits. 3.14 Dashboard Layout Patterns Composing many small components into one legible summary screen. 3.15 Calendars Compressing an abstract concept — time — into a scannable grid. 3.16 Timelines Sequence made visible — what happened, in what order, and what's next. 3.17 Pricing Sections Where a visitor decides, in seconds, whether the product is for them. 3.18 Testimonials Borrowed trust — someone else's word standing in for a track record the visitor hasn't seen yet. 3.19 FAQ Sections Pre-answering the objections that would otherwise become support tickets or lost conversions. 3.20 Carousels Popular, frequently misused, and worth thinking twice about before reaching for. 3.21 Search Often the fastest path through a product's structure — when it actually works. 3.22 Filters Letting the user narrow a large set down to exactly what matters to them. 3.23 Notifications & Toasts Brief, timely interruption — done right, it informs; done wrong, it becomes noise the user learns to ignore. 3.24 Skeleton Loaders & Loading States Managing the gap between "requested" and "ready" without it feeling like nothing is happening. 3.25 Progress Indicators Turning an unknown wait into a bounded, understandable one. 3.26 Floating Action Buttons A persistent shortcut to a product's single most common action. 3.27 Modals & Dialogs The most overused component in modern UI — powerful when it interrupts for a reason, damaging when it interrupts from habit. 3.28 Drawers A modal's gentler cousin — interrupting less while still focusing attention. 3.29 Image Galleries Letting visual content be the primary content, not a decorative afterthought. 3.30 Maps Spatial data deserves a spatial interface — but only when location is actually the point. 3.31 Chat Widgets A persistent, low-commitment channel to support or sales — if it doesn't get in the way. 3.32 Dark Mode More than an inverted color palette — a second, fully considered design system. 3.33 Accessibility Foundations Not a checklist bolted on at the end — a requirement that shapes every other chapter in this Part. 3.34 Responsive Design One layout, many screens — designed as a continuum rather than a fixed set of breakpoints. 3.35 Animations & Transitions Motion that explains a change in state — not motion for its own sake. 3.36 Micro-interactions The small, often unnoticed feedback loops that make an interface feel alive and responsive. 3.37 Design Systems The rulebook that keeps every component in this Part consistent across an entire product. 3.38 Component Libraries Where a design system's rules become actual, reusable code. 4.1 Typography Systems The single element present on every screen a product will ever show — and the one most often left to default settings. UI Design 4.2 Color Theory & Palettes Color is doing more communicative work than any other visual element — status, hierarchy, brand — often simultaneously. UI Design 4.3 Spacing, Grids & Layout The invisible structure that makes a page feel organized rather than merely arranged. UI Design 4.4 Iconography A visual shorthand that only works if every icon in a set speaks the same visual language. UI Design 4.5 Illustration & Photography The imagery style a product chooses says as much about its personality as any words on the page. Visual / Brand 4.6 Branding & Logo Design The identity layer that has to work at the size of a favicon and the size of a billboard. Brand / Marketing 4.7 Image Optimization & SVG The single most common, most fixable cause of a slow-feeling product. Frontend Engineering 4.8 Motion Graphics, Lottie & 3D Richer visual tools than a CSS transition — with a correspondingly higher cost if used carelessly. Frontend / Visual 4.9 Hero Imagery & Background Video The most performance-sensitive visual real estate on a page, precisely because it's the first thing that loads. Visual / Marketing 4.10 Accessibility in Visual Design Where the visual craft covered in this Part meets the non-negotiable requirement established in Chapter 3.33. Accessibility 5.1 Databases: SQL vs. NoSQL Every other decision in this Part rests on this one — how the product's data is structured, stored, and queried. Data Engineering 5.2 Authentication & Authorization Two words that sound similar and get confused constantly — and confusing them is how access-control bugs happen. Backend / Security 5.3 Sessions, Cookies & Tokens The mechanics behind how a server remembers you across an inherently stateless protocol. Backend / Security 5.4 REST API Design The contract between a backend and everything that consumes it — a website, a mobile app, or another service. Backend / API Design 5.5 GraphQL & WebSockets Two answers to two different limitations of plain REST — over-fetching, and the lack of a persistent connection. Backend / API Design 5.6 Webhooks & Event-Driven Notifications How two systems that don't share a database still keep each other informed in real time. Backend / Integrations 5.7 Payments & Billing Systems The single category of bug in a product where "mostly correct" is not an acceptable outcome. Finance / Backend 5.8 Email & Transactional Messaging The most reliable channel a product has for reaching users — and the easiest one to accidentally get marked as spam. Backend / Communications 5.9 Caching Strategies The single highest-leverage performance technique available to a backend — and the one Phil Karlton called one of the two hard problems in computer science. Backend / Performance 5.10 Queues & Background Jobs The pattern that keeps a user-facing request fast by moving the slow part somewhere else. Backend / Infrastructure 5.11 File Storage & Uploads Why almost no product stores uploaded files in its own database or on its own web server. Backend / Infrastructure 5.12 Search Infrastructure Why a plain database query stops being enough the moment a search box needs to feel fast and forgiving. Backend / Data 5.13 Logging & Monitoring The difference between finding out about an outage from a monitoring alert versus from an angry customer. Backend / Operations 5.14 Backend Security Fundamentals The failure modes that don't announce themselves until a breach has already happened. Backend / Security 5.15 Scaling Backend Systems The Part's closing chapter — what happens when a system that worked fine for a thousand users meets a hundred thousand. Backend / Infrastructure 6.1 Prompt Engineering The lowest-cost, highest-leverage lever available for improving what a language model produces. AI Engineering 6.2 Context Engineering A broader discipline than prompting alone — what information the model actually has access to, not just how it's asked. AI Engineering 6.3 Retrieval-Augmented Generation (RAG) How a language model answers questions about information it was never trained on. AI Engineering 6.4 Embeddings & Vector Search The mathematical trick that lets a computer judge whether two pieces of text mean similar things. AI Engineering 6.5 AI Agents & Tool Calling The shift from a model that only answers questions to one that can act on them. AI Engineering 6.6 Agent Orchestration & MCP What happens when a task needs more than one tool, one model, or one system to complete. AI Engineering 6.7 Memory in AI Systems Why an AI product that "remembers" the user is solving a harder problem than it looks like from the outside. AI Engineering 6.8 AI Evaluation & Hallucination Reduction "It seemed to work when I tried it" is not a testing strategy — this chapter is about what actually is. AI Engineering / QA 6.9 AI Safety & Governance The set of guardrails that separate a genuinely useful AI feature from a liability waiting to surface. AI Engineering / Governance 6.10 LLMOps & Model Selection The operational discipline of running AI features in production, closing out this Part. AI Engineering / Operations 7.1 Git & Version Control The foundational tool underneath every other practice in this Part. Software Engineering 7.2 GitHub Workflows & Collaboration The social and procedural layer on top of Git's technical foundation. Software Engineering 7.3 Documentation (README, CHANGELOG, LICENSE) The files that determine whether a stranger — or a future version of the same team — can actually use the codebase. Technical Writing 7.4 Testing Fundamentals The difference between "I think this works" and "I can prove this works, repeatedly, automatically." QA Engineering 7.5 CI/CD Pipelines The automated assembly line that turns a committed change into a live deployment. DevOps 7.6 Docker & Containerization The technology behind "it works on my machine" no longer being an acceptable excuse. DevOps / Infrastructure 7.7 Kubernetes & Orchestration What manages hundreds of containers when Docker alone only knows how to run one. DevOps / Infrastructure 7.8 Deployment Platforms Cloudflare, Vercel, Netlify, AWS, Azure, GCP — the decision that shapes almost every other infrastructure choice. DevOps / Infrastructure 7.9 Design Patterns Named, reusable solutions to problems every non-trivial codebase eventually encounters. Software Architecture 7.10 Architecture Patterns MVC, Clean Architecture, DDD, CQRS, Event Sourcing — the shape of an entire codebase, not just one piece of it. Software Architecture 7.11 Semantic Versioning & Release Management A version number that actually communicates something, rather than just incrementing arbitrarily. Software Engineering 7.12 Refactoring & Code Quality The closing chapter of this Part — how a codebase stays workable as it grows, rather than accumulating debt silently. Software Engineering 8.1 Requirements Gathering & Discovery The stage every failed project skipped, and every successful one spent real time on. Product Management 8.2 Roadmaps & Wireframes Two artifacts that translate discovery into something concrete enough to plan and build against. Product Management 8.3 User Stories & Backlogs The unit of work that keeps a team focused on user value rather than technical tasks in isolation. Product Management 8.4 Agile, Scrum & Kanban Three related but distinct terms that get used interchangeably far more often than they should. Product Management 8.5 Sprints & Milestones The rhythm that turns a backlog into actual, regularly-shipped progress. Product Management 8.6 Risk Management Identifying what could go wrong while there's still time to do something about it. Project Management 8.7 Quality Assurance Processes Quality as an organizational process, not just the automated tests covered in Part VII. QA / Project Management 8.8 Stakeholder Management The Part's closing chapter — a project can be technically excellent and still fail if the people who need to be aligned aren't. Product Management 9.1 Business Architecture The layer that describes an organization's actual structure — before any technology decision is made. Enterprise Architecture 9.2 Application Architecture Zooming out from a single system's internal architecture (7.10) to how many systems fit together across an enterprise. Enterprise Architecture 9.3 Technology Architecture The infrastructure and platform standards underneath every application in the enterprise's portfolio. Enterprise Architecture 9.4 Information Architecture Not to be confused with a single site's navigation structure — this is data ownership across an entire enterprise. Enterprise Architecture 9.5 Capability Mapping & Governance Knowing what the organization can do, independent of the specific system currently doing it. Enterprise Architecture 9.6 Architecture Decision Records (ADRs) A small, cheap habit that prevents an enormous, recurring waste of time: relitigating decisions nobody remembers the reasoning behind. Enterprise Architecture 9.7 Architecture Reviews & Governance The checkpoint where a proposed system is checked against enterprise standards before it's built, not after. Enterprise Architecture 9.8 Digital Transformation & Enterprise Integration The handbook's closing chapter — how everything covered across all nine Parts comes together at the scale of an entire organization. Enterprise Architecture