Private Pro category · 15 compositions
Testimonials
Layouts for verified customer evidence; all bundled copy is explicitly fictional. These records are manifest-derived and source-free; an implemented status does not imply manual verification, release readiness, entitlement protection, or availability for purchase.
Manifest items
All 15 records currently carry implemented status. A dedicated detail becomes internally discoverable only after release readiness and a reviewed public preview.
Customer evidence grid
Outcome story
Role-specific voices
Industry perspectives
Video evidence shell
Long-form case quote
Compact quote rail
Metrics with attribution
Review source cards
Before-and-after account
Implementation story
Support experience
Team adoption story
Evidence carousel
Category contract
- Purpose
- Layouts for verified customer evidence; all bundled copy is explicitly fictional.
- Declared dependencies
- gummy-avatar, gummy-card, gummy-carousel
- Required review
- light, dark, responsive, keyboard-reviewed, rtl-reviewed, reduced-motion
How to evaluate Testimonials blocks
Use a testimonial layout only when the exact quotation, speaker identity, organisation, and permission have been verified. Select the composition for the evidence available rather than adding a logo, metric, or portrait that the customer did not authorize.
Store approved wording and attribution in a maintained record so corrections or withdrawal propagate consistently. Mark fictional demonstration copy unmistakably, provide alternatives for informative portraits or logos, and avoid auto-advancing carousels that make evidence difficult to read or control.
Retain a record of consent, source, approval scope, and removal process. Check quotation accuracy, title changes, links, imagery rights, keyboard controls, pause behavior, narrow layouts, and long translations. Bundled examples remain fictional and must never be presented as real customer endorsement.
Each approved testimonial should arrive with the exact quotation, speaker display name, role, organisation, media rights, destination, consent scope, approval date, and owner of the relationship. Define expiry or revalidation where appropriate. If any element cannot be substantiated later, remove it cleanly instead of preserving the layout with an unattributed or rewritten claim.
Boundary
Public pages contain only approved names, purposes, dependency aliases, requirements, status, and any future reviewed image preview. Editable paid source, test paths, release locations, and entitlement details remain private.