Build Log
A weekly technical blog on researching, engineering, verifying, and shipping BeatlesAnswers.org.
Dual-source everywhere — and this build log
The dual-source remediation queue drained through the Let It Be sessions' equipment story, release-history language corrected for the 2021 boxset era — and the build log goes live.
Structure remediation complete — and a quality flag
All 47 enriched pages on the locked structure, inherited take-counts corrected against Lewisohn, a content-hash sitemap, standing deploy authority — and the two-source rule hardened.
Footnotes, a hamburger, and one skin
Inline citations became book-level footnotes; a byte-level integrity scan caught 16 silently clipped pages; the mobile nav got a burger; and the CSS skin standard was codified.
A contract for every session
A ~92% correction rate proved in-session verification is provisional; a pre-commit footer check fixed it; and a thin-page incident produced a model-agnostic session contract.
The page-offset bug
The deep-enrichment campaign opened — and cross-session verification immediately caught 11 citations off by exactly 4 pages, a 60-page systemic error, and a source that had to die.
An entity layer, a link graph, and a citation policy
Person schema and sameAs entity links on 279 pages, a 6,420-edge internal link graph, extensionless canonicals — and a citation policy with zero outbound to competitors.
Three audits and a foundation pass
v9 brought photographic backgrounds, v10 an SEO pass — then three independent external audits fed a foundation-hygiene phase and a resumable project plan.
Eight versions in week one
How BeatlesAnswers.org went from an empty folder to a deployed static site in its first week — generator chain, versioned deployments, and a UK-canon mission.
This build log opened on 2 July 2026. Entries before that date were reconstructed the same week from the project’s session records and are dated to the weeks they document.