Product Journal
Daily notes on building and improving djamespoer.com. Open the Buildometer project instruments.
The original automated Scrum Brief archive was replaced after review showed that reusable project-status metadata had been interpreted as day-by-day project activity. The corrected archive was reconstructed from dated project evidence so each entry reflects what was actually happening in its reporting period.
Executive Scrum Brief —
Recently shipped
The portfolio and Shady White Van now share a clearer measurement boundary. The embedded exhibit no longer starts its own Google Analytics or Cloudflare beacon. The portfolio records a qualified exposure only when the van slide is active and at least half visible in a foreground page, once per page lifetime. Hidden preloads no longer masquerade as standalone visits, while the persistent exhibit keeps its scene intact.
Both sites reached production through their existing release paths. A follow-up restored the prior regional exclusion for the manually loaded Cloudflare beacon, while retaining standalone Google Analytics consent behavior. A separate homepage-only release removed four carousel slides; it did not publish the broader homepage rewrite.
Validated / learned
The cookie warnings behind the portfolio’s Lighthouse Best Practices score of 96 came from Google Analytics running inside the cross-site exhibit. After the correction, Lighthouse 13.5 reported Best Practices 100 with no Inspector Issues. Five production browser profiles confirmed one parent page view, qualified exposure and native session in allowed desktop and mobile cases; internal and denied-consent profiles emitted no Google Analytics events. The iframe retained its document identity and produced no child collectors or GA cookies in those checks.
The child-site browser matrix passed 27 live scenarios, followed by ten targeted regional checks on the corrected release. The regional gate excludes the documented country set and fails closed when location cannot be read; it uses visitor country rather than proving exact equivalence to the former edge-location rule. Removing embedded loads also changes the meaning of Shady White Van’s traffic totals, so comparisons across the switch need that context.
A supplemental standalone-beacon check encountered interception and request-attribution errors. A diagnostic observed a real beacon POST, but the final supplemental fixture did not complete successfully. That unfinished check is not evidence of a confirmed product defect or a fully passed end-to-end collector test.
Current focus
The released analytics boundary is verified, while final record reconciliation and owner acceptance remain separate from deployment success. The broader homepage direction now emphasizes enterprise UX engineering, accessible front-end architecture and linked project evidence; it remains subject to local visual approval and is not part of this release.
Protected career-evidence work still has a documented distinction between stored proposals and owner-reviewed claims. The inspected registry does not establish a new completed correction of active versions or review states. Public résumé publication remains separate evidence from canonical reconciliation.
Next
Reconcile the final release records and outstanding collector-test limitation before closing the analytics work. Use processed reporting and the corrected exposure definition before judging whether content resonates; collection checks alone do not establish visitor response. Advance the homepage through owner visual review, and verify protected claim dispositions and active versions before propagating further career-source changes.