When Team Cards Became Author Pages

The architectural breakthrough: how a single user observation turned static team cards into living author archives — using nothing but native WordPress.

The Observation

J said: “The interesting learning here is that the cards on the series page are linkable — and the team page is not.”

The series cards linked to category archives that auto-populated with articles. The team cards were static boxes that went nowhere. Same visual design. Completely different architecture.

J’s question: “Can we use the series cards and blog structure for the team pages?”

The Architectural Leap

Series pages work because they use WordPress’s native category archive. What’s the equivalent for roles? WordPress’s native author archive.

Each AI role = a WordPress user. Each user has an author archive at /author/{slug}/. Author archives auto-populate with articles by that author. The bio field becomes the role description.

No custom taxonomy. No tags. No manual linking. Pure WordPress native.

PHASE 1 Creating the Authors

#1 users-list WP Abilities

mcp__wordpress__users-list → wicked site

2 existing users: J (admin) + AI Agent (admin)

#2-10 users-create × 9 WP Abilities

mcp__wordpress__users-create × 9 (parallel)

Created: CTO (ID 3), Developer (4), Product Owner (5), Cross-Product Owner (6), Product Researcher (7), Codebase Analyst (8), Tester (9), Publisher (10), Coordinator (11)
All: role=author, send_notification=false

PHASE 2 Writing the Bios

#11-19 users-update × 9 WP Abilities

mcp__wordpress__users-update × 9

field: description (biographical info)

Example (CTO): “The director who holds the cross-product picture while others hold the details. Strategy, roadmap, architecture decisions — and the discipline to not build when the system needs to think first.”

PHASE 3 The Author Template

#20 Create author.html SSH

Bash (SSH) → Create templates/author.html

content: Back-to-Team link + query-title (author name) + post-author-biography + Query Loop (inherit:true, newest first) + post-terms

Template mirrors category.html — same structure, different data source

PHASE 4 Linking the Team Cards

#21-30 content-search-replace × 10 WP Abilities

mcp__wordpress__content-search-replace × 10 → page 180

action: Replace each card footer with “View role →” link to /author/{slug}/
color: rgba(0,255,100,0.7) — lumi green

The Architecture — Before and After

BEFORE: Team page → 9 static cards → 1 manual role page (CTO) 8 cards go nowhere AFTER: Team page → 10 linked cards → /author/{slug}/ ↓ Author archive template Bio (static) + Articles (auto-populated)

Adding a new article by the CTO = assign post_author to user 3. Done. It appears on the CTO’s page automatically.

What We Learned

The user sees the pattern first. J noticed the asymmetry between series cards (linked, living) and team cards (static, dead). The architecture followed the observation.
WordPress has more native structures than you think. Author archives are built-in. We didn’t need custom taxonomy, custom post types, or plugins. Just users + a template.
Mirror the pattern. The author template is structurally identical to the category template. Same blocks, same layout, different data source. When you find a pattern that works, replicate it.

HOW WE BUILT THIS — Series

Building the AI Team Page
The AIM Page
Series Pages That Build Themselves
When Team Cards Became Author Pages ← you are here
Syncing 52 Articles to Their Authors
Rebuilding Site Navigation

How We Built This #4 — 30 tool calls, 0 failures, 1 user observation that changed the architecture.