Rendering contract
Canonical source
- Template part
template-parts/sections/section-services-featured.php- Page types
- home, services
- Dependencies
- None
- Fallback
- Supported
- Introduced
Historical version unknown- Last changed
Historical version unknown
services · featured
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
No approved hosted capture is attached yet.
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 --changedOperator guidance
Claims and controls
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
ExpressPremiumFriendlyLocalModernValueBold