Service Detail Split
A single service explained in depth with two paragraphs and a six-row deliverables table beside a sticky Placeholder visual.
A single service explained in depth with two paragraphs and a six-row deliverables table beside a sticky Placeholder visual.
The Portfolio Collection unlocks the source for every Portfolio block. All Access unlocks every Collection.
Already purchased? Log in
Service Detail Split gives one service the full treatment, a heading for Product design, two paragraphs covering scope and working style including I work best when brought in early, before the scope is locked, and a six-row ruled deliverables table on the left, beside a sticky Placeholder visual on the right. Each deliverable row names the stage and what it produces, from stakeholder interviews and a written problem frame in Discovery through to annotated specs and a 30-day async QA window in Handoff package.
Deliverables are one array with label and detail. The sticky Placeholder and the deliverables table together balance the columns per the split-layout rule, and the sticky behaviour keeps the visual alongside the full writeup as it scrolls.
Reach for this block as the deep-dive section on a services page or a dedicated service landing page. The installer swaps the heading, the two paragraphs, and the deliverables rows for whichever service they want to explain in full.
A natural flow around it on a Portfolio Pro page:
Before
After
One strong use is the product design deep-dive with a full deliverables table. Other detail splits:
Tip: write the deliverable detail as a concrete output the client receives, annotated specs, asset exports beats the phase name alone.