How This Book Is Maintained

Every page has a document type, maturity state, source-freshness class, and review date. Only reviewed material appears in the normal learning sidebar. Direct links to pending material remain available so reviewers can work without publishing it as finished.

Technical claims prefer standards and official platform/framework documentation. Stable subjects are reviewed annually, evolving subjects every six months, and fast-moving framework, privacy, browser, and AI material quarterly and before publication.

Core chapters require both subject-matter and learning/editorial approval. Exercises require an expected-answer outline, rubric, completed example, common weak answers, or reviewer checklist. Automated checks validate structure, links, sources, freshness, repeated prose, and the production build; they do not replace expert review.

Material changes are recorded in the Changelog. Corrections should identify the affected page, evidence, user risk, and whether a previously taught decision changed.