Rendering contract
Canonical source
- Template part
template-parts/services/service-body.php- Page types
- service
- Dependencies
- cpt:service
- Fallback
- No fallback
- Introduced
Historical version unknown- Last changed
Historical version unknown
service-single · body
Service page — body
The single-service main content (description, benefits, process steps, pricing) read from the CURRENT service post. Part of every service single by default.
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
Single-context section: reads the queried service post; composable per-type (suds_section_stack_service option) or per-post (suds_section_stack meta).
Optional inputs: service_benefits, service_steps, service_pricing.
3 control groups are declared in the Engine manifest.
Supported skins
ExpressPremiumFriendlyLocalModernValueBold