templates / olympus

olympus

SDK 0.4.30

Classic single-step checkout with the original tiered card shape.

Campaign Cart SDK 0.4.30 CampaignSpec v4.3
$ npx campaign-init
choose olympus 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 landing page
landing preview
olympus checkout page
checkout preview
olympus upsell page
upsell preview
olympus receipt page
receipt preview
plus a presell page and three upsell layouts (stepper, tier cards, tier pills) — seven 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.
analyticsCanonical events, commerce payloads, campaign identity, and provider delivery stay in the SDK runtime.
page routingThe funnel order is fixed by the contract: landing → checkout → upsell → receipt.
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.
trackingConfigure provider IDs, external scripts, and blocked-event exceptions without replacing SDK-owned payloads.
edits are re-validated on every push — the contract is enforced, not trusted
NEXT STEP

Build with olympus.

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

Open Workspace All templates