SA Template System¶

Status: Active · v3.1 shipped, sitewide conversion complete, QA ongoing Project: Website

What this is¶

"SA" = Sam Aguiar. The SA Template is the standardized page layout used across nearly every content page on aguiarinjurylawyers.com — injury pages, practice area pages, location pages, and some landing pages. It's a Kadence-native block structure with strict brand rules baked in, built to be consistent, auditable, and machine-deployable via the WordPress REST API.

Template structure (v3.1)¶

Hero: wp:cover, city/topic-specific .webp, navy overlay, centered H1
Trust bar: Bigger Share Guarantee + Forbes + No Fee Unless We Win
Content body: structured content blocks (KRS citations, FAQ accordion with JSON-LD, insurance comparison tables)
Sidebar column: phone CTA (Louisville + Lexington), attorney cards, related pages
Schema: JSON-LD for FAQs, LegalService, LocalBusiness

The "protected pages rule" was added in v3.1 — pages marked as protected in the WP metadata are skipped by batch deploys, so manual tweaks survive.

v3.1 hardening¶

The v3.1 rebuild (April 3) introduced: - Protected pages rule - Batch subheader fix - Locations hero update - FAQ Layout Incident guardrails

SA Template Reference Skill¶

A companion Claude skill (sa-template-reference) was overhauled on April 3 to act as the canonical reference for agents generating new SA-compliant pages. Any agent writing new content pages is supposed to read this skill first before building anything.

Recurring QA issues¶

Wrongful Death page needed a manual fix (flagged in the 9-page batch audit) — template alone didn't produce the right structure for that topic
FAQ Layout Incident — a previous agent broke FAQ layouts sitewide; guardrails added after the fix
Florence post grid fix — post grid block didn't match the template spec
Car Accident page full rewrite — the master page got a complete rewrite and re-deploy with the new template on March 31

Sitewide conversion¶

The SA Template was rolled out to the final 3 non-compliant pages in a single session that also included sitewide schema cleanup. Every page is now on the template.