improve: testimonials - Redesign the page and display approved quotes #151

Improvement Summary

Rebuild /testimonials/ as a designed testimonial page. DEV page 45449; supplied slug testimonials-page.

Final plan (updated 2026-10-23)

Launch scope. In scope for the 27 October 2026 launch (milestone: Core Site Pages Complete). The page is in the DEV Work menu and is currently broken, so it needs a proper rebuild; there is no quick reset for it.

Approach. The theme has no testimonial pattern (checked), so a new testimonial card/grid pattern in ls-theme is justified: a repository change (PR). Hero and CTA reuse existing patterns. The page content (quotes and client names from LIVE, after approval) is a WordPress page content edit. Re-add pattern names in the block metadata after any MCP write. This supersedes "no dedicated file justified" in the Branch instructions below.

Linked Stories/Tasks/PRs/Epic

Parent: LSA-166, hierarchy only; no epic PR association. Historical LSA-79 checklist is not current completion evidence; LSA-3 broad design work is not an exact implementation duplicate. No extra native relationships.

Milestones & Timeline

Launch scope for the 27 October 2026 launch, linked in DEV Work menu. Milestone: Core Site Pages Complete.

Is your improvement related to a problem? Please describe

Reported large blank white cards show only cyan client-name links; quotes/images absent. LIVE has about 3,000 words of testimonials. Missing content alone does not prove a code fault.

Describe the improvement you'd like

Source actual quotes/client names from LIVE and confirm approval/permissions. Present approved selection using theme cards/layout. Resolve logos/images by linking DEV media, not downloading to assets/images. Preserve URL/Work-menu journey; no invented endorsements.

Designs / Mockups

Approved testimonial treatment, quote selection and exact DEV media mapping remain implementation dependencies.

Accessibility Considerations

Readable quotes, semantic attribution, appropriate image alternatives, contrast and responsive cards.

Acceptance Criteria

• /testimonials/ remains unchanged and Work-menu route works.
• Approved LIVE quotes/correct client names are displayed without fabrication.
• Blank-card presentation is resolved and content is legible.
• Logo/image permissions/sources are resolved; DEV media is linked, not copied into theme assets.
• Quote selection and presentation receive review before publication.
• All acceptance criteria met
• Documentation/changelog updated
• Tests added/updated
• PR uses correct branch prefix (feat/)
• PR description updated with relevant details
• Changelog entry prepared for PR (if applicable)
• Labels/types match org standards

Testing Requirements

Compare selected quotes/names to verified source; check media, navigation, long-text/cards, mobile, keyboard and contrast. No live scrape/permissions check executed here.

Describe alternatives you've considered

Reuse cards/grids before a new pattern. Historical consolidation requires an explicit decision, not silent URL retirement.

Additional Context

LIVE https://lightspeedwp.agency/testimonials/; DEV https://ls-agency.lightspeedwp.dev/testimonials/. Exact DEV media and quote rights remain to resolve.

Branch instructions

Apply shared packet. Provisional WordPress page 45449 edit using cards/grids/page-no-title; no dedicated file or downloaded assets justified. Exact branch/base withheld; develop integration verified. Stop for revised bounded plan if shared card code changes needed. Source-template wording retained unchanged; branch/PR requirements apply only to repository changes; database-only edits need no branch. Improvement feat/ wording is not branch selection. Verify owning-repository rules and resolve documented PR-template conflict before implementation. Do not mark contradictory requirements satisfied, auto-close on merge, automatically delete branches or close the parent epic.

Definition of Ready (DoR)

• Problem/opportunity defined
• Acceptance criteria written
• Designs attached (if relevant)
• Dependencies mapped
• Estimate added (if relevant)

Definition of Done (DoD)

• All AC met and demonstrated
• Documentation and changelog updated
• Tests added/updated
• Correct labels/types applied
• PR uses correct branch prefix (feat/)
• Branch deleted after merge
• Linked issue(s) updated with latest status and closed after merge,
• The related epic should not be closed, instead updated with a comment to reflect the closed issue