Session — Location page benefits-section mockups

Date: 2026-05-26

Importance: Medium

Status: Pending Sam's pick on the visual variant. No live changes made.

What was done

• Pulled the live Lexington flagship (/locations/lexington/), Bowling Green spoke (/locations/bowling-green/), and Locations index (/locations/) to confirm the current state of the benefits-style sections on both flagship and regional pages.
• Loaded the sail-design-foundation skill for canonical tokens (colors, type scale, radius, shadow, motion, breakpoints) so every mockup pulls from the same root variables.
• Built six visual variants of the benefits block in a single self-contained HTML review file. Copy is locked verbatim from the uploaded benefits-section.md. No eyebrows. No fluff. Each variant ships with a desktop and a mobile preview side-by-side.
  • A. Card grid, light bg, navy headline, orange accent corner. Drop-in replacement for the current "Our Commitments To You" cards on the Lexington flagship.
  • B. Dark Visible-Depth gradient cards, orange icon medallions. Strong as a contrast break between the hero and content body on spoke pages.
  • C. Editorial numerals (Fraunces 56px), single column, hairline dividers. Premium feel. Pairs with the Jon Hollan bio block on Lexington.
  • D. Zebra rows with a proof badge on the right that elevates the stat. Forces the proof line to do real work.
  • E. Compact 3-up icon row per the spec's "Compact LP" treatment. Quick scan, low real estate.
  • F. Stat-anchor cards (proof becomes the lead element). Risk: introduces short micro-labels under each stat that don't appear verbatim in benefits-section.md. Flagged for Sam.

Deliverable

Repos/sail-litify/workspaces/litify-spring-cleaning/Design/location-benefits-mockups-2026-05-26.html — single self-contained file, 1,044 lines, ~48KB, opens in any browser.

Decisions still pending

• Which variant (or combination) gets adopted for location pages.
• Whether Variant D's split proof (e.g., "24 hours / Most clients see calls stop within") counts as a messaging change. The words are identical to the source, just visually rearranged for stat hierarchy.
• Whether Variant F's short stat labels ("Calls stop within," "Standard fee · we charge less," etc.) are acceptable. These are NOT in the source attachment.
• Whether to add the Spanish-Speaking Team benefit to spokes that target bilingual audiences (deliberately left out of the current mockups to keep the variant count clean; it's the eighth canonical block in the source).

Recommended next actions

• Sam picks A, B, C, D, E, or F (or a hybrid like A on Lexington + B on Bowling Green).
• Build the chosen variant as a reusable WordPress block / pattern in the theme so every existing and future location page inherits it.
• Run the pre-publish-qa skill before any live push, then wp-content-deployer for staged backups, then playwright-visual-qa post-deploy at 1280px and 390px.
• Optional: build matching practice-area treatment using the same primitives so the benefits-section language is consistent everywhere.