BeatlesAnswers.org

Technical History

Build Log

13 entries · Updated 3 August 2026

How BeatlesAnswers.org is researched, engineered, verified, and shipped. Entries reconstructed from the project’s dated planning and release history; nothing is invented. The record now covers thirteen distinct decisions, newest first. New entries are weekly.

This blog is about the website itself. Subject-matter content — essays on Beatles recording history — lives in Articles. Here, the evidence is the technical process: static architecture, primary-source verification, integrity controls, publishing, and the standards that grew from the work.

Forty-Four Takes That Never Happened

Rock and Roll Music was a single take, not nineteen; The Night Before claimed forty-four takes when two were recorded; the enrichment campaign crossed from Beatles for Sale into Help! and the re-verify streak hit twenty-three.

Read the entry →

Nineteen Was Never the Answer

A recurring wrong take count ran through every Beatles for Sale page; a scope ruling on Releases sections clarified what enrichment is and is not; and the re-verify streak hit twenty.

Read the entry →

Measuring Before Doubling

A three-session controlled trial measured whether two enriched pages per session could match one-page quality; the data said yes, and the 1 June 1964 cluster was the proving ground.

Read the entry →

The Rhythm Is Weekly Now

Scheduled sessions carry the enrichment beat; take-counts and consoles corrected against the session record; and the deploy pipe gains an integrity gate that refuses to push a clipped file.

Read the entry →

Publish Was the Dangerous Part

A pre-mirror scan catches a silently clipped page; the push pipeline is automated and immediately earns its guards; and 999 pieces of placeholder ad code leave the site before review.

Read the entry →

Why the Second Source Matters

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.

Read the entry →

A Quality System Has to Tighten

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.

Read the entry →

When the Checks Lied

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.

Read the entry →

The Process Is the Product

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.

Read the entry →

Off by Exactly Four Pages

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.

Read the entry →

A Reference Site, Not a Referral Funnel

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.

Read the entry →

Boring Fixes That Matter

v9 brought photographic backgrounds, v10 an SEO pass; then three independent external audits fed a foundation-hygiene phase and a resumable project plan.

Read the entry →

Static HTML, On Purpose

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.

Read the entry →