feat(website): first-person /about prose, sourced and guarded - #828
Merged
Conversation
The page shipped in #826 as a factual skeleton: a name, a role, and a one-line bio, with the connective sentences written by an agent and flagged for replacement. Replace them with Brian's own account, in first person. Every biographical claim traces to brianflove.com/about-me (retrieved 2026-08-24), and two paragraphs are verbatim from it. The prose lives in `about-content.ts` rather than inline in the route for one reason: the module carries a provenance comment naming the source, and the spec can assert the page renders exactly those paragraphs and no others. That preserves what the original spec was built to do — this page is an E-E-A-T signal, so it is precisely the surface a fabricated credential would appear on, and structured data makes such a claim durable and machine-readable. The guard is mutation-tested: injecting an invented "twenty years of experience and a Google Developer Expert award" paragraph fails the suite. `bio` moves from "Angular consultant and open-source maintainer" to Brian's current self-description. It feeds every blog byline and the /about meta description, so the site now states one role rather than two that disagree. `knowsAbout` is deliberately unchanged. It renders as a schema.org expertise claim and its comment scopes it to subjects with docs and code in this repository. Brian's RAG and Azure AI Search work is real but not evidenced here, and structured data is the wrong place to assert what the site cannot show. Deliberately absent: any statement of how Threadplane relates to Hashbrown. Hashbrown is credited to Brian and Mike Ryan; the relationship between the projects is Brian's to characterise, not something to infer. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #826, which shipped
/aboutas a deliberate skeleton with the connective prose flagged for replacement.What changed
The page now carries Brian's own account in first person: the arc from Hamilton College → CTO at Webucator → LiveLoveApp → Polaris with Mike Ryan → Azure AI RAG work → Hashbrown → Threadplane, closing with two verbatim paragraphs from his site.
Every biographical claim traces to brianflove.com/about-me (retrieved 2026-08-24). Nothing was inferred or embellished — no years of experience, awards, talks, or clients beyond what he already publishes.
Why the prose lives in a module
about-content.tscarries a provenance comment naming the source, which lets the spec assert the page renders exactly those paragraphs and no others.That preserves what the original spec was built to do. Its comment says it plainly: this page is an E-E-A-T signal, so it's precisely the surface a fabricated credential would appear on — and structured data makes such a claim durable and machine-readable. The old test tied prose to the author record; since the biography is now sourced externally, the guard moves with it rather than being dropped.
The guard is mutation-tested. Injecting a fake paragraph — "I have twenty years of experience and hold a Google Developer Expert award" — fails the suite:
Two data decisions
bioupdated. From "Angular consultant and open-source maintainer" to his current self-description. It feeds every blog byline and the/aboutmeta description, so the site now states one role instead of two that disagree.knowsAboutdeliberately unchanged. It renders as a schema.org expertise claim, and its comment scopes it to subjects with docs and code in this repo. Brian's RAG and Azure AI Search work is real but isn't evidenced here — structured data is the wrong place to assert what the site can't demonstrate.No Hashbrown → Threadplane relationship claim. Hashbrown is credited to Brian and Mike Ryan; how the projects relate is Brian's to characterise, not mine to infer.
Verification
npx vitest run --config vite.config.mtsfromapps/website: 313 passed, 5 failed — the same pre-existing failures inthanks/page.spec.tsx,PostCard.spec.tsx,Differentiator.spec.tsx, none touched here (308 passed before; 5 added tests account for the delta)nx lint website: 0 errors, 29 warnings (unchanged)nx build website --configuration=production: succeedsPersonJSON-LDdescriptionmatches,knowsAboutunchanged, 0 images (no headshot exists)h1, threeh2, all seven paragraphs in order, no horizontal overflow🤖 Generated with Claude Code