templates / olympus-mv-single-step

olympus-mv-single-step

SDK 0.4.25

Products with variants — color, size, flavor — kept to a single-step checkout.

Campaign Cart SDK 0.4.25 CampaignSpec v4.3
$ npx campaign-init
choose olympus-mv-single-step in the template picker
PAGES

Four pages, one funnel.

The order is fixed by the contract. Each page declares the slots it renders and the cart actions it may take.

olympus-mv-single-step landing page
landing preview
olympus-mv-single-step checkout page
checkout preview
olympus-mv-single-step upsell page
upsell preview
olympus-mv-single-step receipt page
receipt preview
plus a presell page and bundle upsell layouts — eight pages in the family
THE CONTRACT

What the SDK owns, and what you edit.

Templates are runtime contracts. The split below is what keeps an edited template launchable.

THE SDK OWNS
cart stateSelection, totals, and line items live in the SDK — never in your markup.
pricingPackage prices and discounts come from the CampaignSpec at render time.
order submitPayment capture and order creation, including failure retry.
hydrationEvery data-next-* attribute is wired on load. No JS required from you.
page routingThe funnel order is fixed by the contract: landing → checkout → upsell → receipt.
variantsColor, size, and flavor selection state with per-variant pricing — selector, cart, and totals stay in sync.
YOU EDIT
markupSections, layout, and styling — anything that keeps the attributes intact.
copyHeadlines, body, and offer language on every page.
imageryProduct photography, badges, and proof elements.
offerPackages, prices, and the upsell product — declared in the CampaignSpec.
trackingYour analytics tags, as long as they never touch cart state.
edits are re-validated on every push — the contract is enforced, not trusted
NEXT STEP

Build with olympus-mv-single-step.

Open the Workspace, choose olympus-mv-single-step as your shape, wire your products, and QA the campaign before launch.

Open Workspace All templates