Rendering contract
Canonical source
- Template part
template-parts/sections/section-services-featured.php- Page types
- home, services
- Dependencies
- None
- Fallback
- Supported
- Introduced
b839b57- Last changed
b839b57
services · featured
Flagship-led services: the FIRST service (menu_order) renders as a large feature (photo or icon panel + excerpt + CTA), the rest as compact rows. Pick when one service (wash & fold, pickup) leads the business.
Approved visual evidence
This intentionally does not reuse an old catalog screenshot. Start catalog.local, sync it to the source commit, capture all seven skins at 390px and 1440px, then approve the revision in Studio.
./suds catalog capture --changedRendering contract
template-parts/sections/section-services-featured.phpb839b57b839b57Operator guidance
The operator's service ORDER is the emphasis — reorder Services to change the flagship. Same claim-safe generic fallback as the other services variants.
No optional inputs are declared.
3 control groups are declared in the Engine manifest.
Supported skins
Effects support
Hero depth: none, bubbles, glow, bubbles_glow
Ambient: none, glow
Accessibility policy
Decorative animation is disabled for reduced-motion visitors; location video also respects Save-Data. Visual approvals include a reduced-motion smoke.