Skip to content
GA George Andary
Menu
LIVE MATCH REPORT OCT 2026

Portfolio Rebuild Case Study

How georgeandary.com was rebuilt twice in 2026: a proof-led structure in March, then a two-day redesign with a two-agent AI team in October.

The October 2026 Projects page, listing every build with a status pill

The read

My portfolio had become a wall of text that buried the proof. It said the right things, but recruiters had to dig to find who I am and what I've delivered.

Game plan

  • Set the direction on a design canvas: seven layout options and six palettes, narrowed to one Home, Projects and project-page set.
  • Ran two AI assistants as a small team. Claude led and built the design system, Home, Projects, the project template and the versions archive. Codex built the nine secondary pages and reviewed the work independently.
  • Checked every public claim on the site against a proof inventory before launch.
  • Kept every earlier version visible instead of overwriting it.
  • Released in verified steps: a live backup first, every old URL re-tested, then speed and phone checks after launch.

First half, second half

The March 2026 homepage in its light editorial design
March 2026: a proof-led structure in a light editorial look.
The October 2026 homepage: "I'm a problem solver." beside George's photo on a dark navy background
October 2026: dark, recruiter-first, one line up top.

Final score

A dark, recruiter-first site that leads with "I'm a problem solver.", gives every build an honest status and its own page, and keeps every earlier version visible.

  • PageSpeed Insights, homepage: 92 for performance on mobile, 100 on desktop, and 100 for accessibility
  • All 27 pre-redesign URLs still resolve, with 0 broken internal links
  • The adversarial review found 10 issues: 9 were fixed before launch and 1 (video captions) was deferred
  • A 4,427-line hand-written stylesheet was replaced by Tailwind and a small component kit
  • Phone emulation (iPhone 13 and Pixel 7 profiles) across 9 pages showed no horizontal overflow, broken images or JavaScript errors

Chapter one: March 2026

The original georgeandary.com felt more like a personal homepage than a recruiter-ready portfolio. It had personality, but it was hard to understand the work quickly. The March rebuild fixed the structure:

  • Home, Projects, Experience, About, Resume and Contact became separate lanes
  • Current builds were separated from prior work experience
  • Outcome-backed proof moved closer to the top

That version is still online at v2.georgeandary.com.

Chapter two: October 2026

The structure was right, but the site had become a wall of text. In two days I rebuilt it around one line, “I’m a problem solver.”, and the evidence behind it.

  • Homepage: dark and recruiter-first, with the tagline, my photo and the proof underneath.
  • Projects: a sports-broadcast “Matchday” page where every build carries an honest status: LIVE, VERIFIED, IN PLAY, WARM-UP or SCOUTING.
  • Project pages: every build gets its own “match report” from a single template, including this one.
  • Archive: all three versions of the site stay visible, so the progress is easy to see.

How the two-agent team worked

I treated it like a small product launch. I picked the direction, then ran two AI assistants as a team: Claude led the core build, Codex built the remaining pages, and each reviewed the other’s work.

The independent review was the useful part. It found ten issues, including contrast problems, a keyboard regression, and copy that claimed more than the evidence supported. Nine were fixed before launch. One, captions for an endorsement video, was deferred on purpose because it needs my own corrections.

What went wrong after launch

A phone check after launch showed that returning visitors could see the old site for a while because of caching. I fixed it at the server level: pages now revalidate on every visit, and the site’s content-hashed files are cached for a year.

Why it matters

This site is a small, honest example of how I work:

  • set a clear direction, then build toward it in checked steps
  • use AI as a team inside a system, with independent review, not as a one-shot generator
  • don’t claim what hasn’t been verified
NEXT FIXTURE Agentic Learning Workflow →