Designing with Web Standards
Source: https://www.informit.com/store/designing-with-web-standards-9780321616951 ↗
The book that won the web standards war.
In the early 2000s, Microsoft and Netscape were fragmenting the web with proprietary extensions, and Zeldman led the campaign — through the Web Standards Project and this book — to convince designers and developers that building to W3C standards was both ethically right and commercially sensible.
Its political importance exceeds its technical content: it demonstrated that an industry could be redirected not by regulation but by persuading practitioners to adopt shared conventions.
The separation of structure (HTML), presentation (CSS), and behaviour (JavaScript) that Zeldman evangelised became the foundation on which every subsequent web practice was built.
A historical document as much as a technical manual.
Central argument
Zeldman argues that building websites to W3C standards — separating structure (HTML), presentation (CSS), and behaviour (JavaScript) — is not merely a technical best practice but a professional and ethical obligation. His core thesis is that proprietary browser extensions from Microsoft and Netscape were fracturing the web into incompatible silos, and that collective adoption of shared conventions by practitioners could reverse this without waiting for regulatory intervention. The book treats standards compliance as a coordination problem solvable through persuasion: if enough designers and developers defected from proprietary hacks, browser vendors would be forced to follow.
Critique
The book's central tension is that it conflates technical standardisation with ethical progress, which made it effective as advocacy but obscures genuine trade-offs. Zeldman's argument rested on the assumption that W3C standards would remain a stable, neutral common ground — a premise that has been tested by the subsequent fragmentation of CSS implementations, the slow death of XHTML, and the degree to which Google has since exerted influence over web standards comparable to the Microsoft dominance he opposed. The political model — redirect an industry through practitioner conscience — also worked partly because the web was small enough for a charismatic minority to move; it is not obviously transferable to later coordination problems at greater scale.
Why it matters for product
For a CPO, the book's most transferable insight is its demonstration that platform-level architectural decisions — how structure, presentation, and behaviour are separated — are not engineering trivia but strategic constraints that determine how teams can be organised, how fast they can move, and how much technical debt accumulates. The standards war is also a case study in how shared conventions reduce coordination costs across an entire ecosystem, which maps directly onto decisions about design systems, API contracts, and component libraries: these are not efficiency tools but political agreements that need the same kind of active evangelism Zeldman deployed. A product leader who leaves those conventions implicit rather than argued and codified will find them quietly eroded by short-term delivery pressure.