templates / apollo

apollo

SDK 0.4.28

Flagship single-step checkout with Apollo layout, product-style bundle cards, and optional checkout reveal.

Campaign Cart SDK 0.4.28 CampaignSpec v4.3
$ npx campaign-init
choose apollo in the template picker
PAGES

Four pages, one funnel.

The order is fixed by the contract. Apollo adds a richer checkout shell: product-style bundle cards, selector-area bump support, form-section bumps, and an optional reveal step.

apollo landing page
landing preview
apollo checkout page
checkout preview
apollo upsell page
upsell preview
apollo receipt page
receipt preview
plus a presell page and the bundle-stepper upsell layout shown here
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, line items, and checkout reveal state live in the SDK/runtime layer.
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.
bump slotsSelector-area and form-section bumps are separate SDK surfaces with separate frontmatter.
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, upsell product, bundle card style, and reveal copy — declared in CampaignSpec/frontmatter.
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 apollo.

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

Open Workspace All templates