{% extends "brickwork/shell/centred.html" %} {% comment %} Checkout flow: basket → delivery details → pay (icvoss/django-brickwork#423). Required Transactional journeys archetype (checkout or request; this page is checkout). COPY THIS FILE into your project and edit it. It is not on the template loader path, so you cannot extend it (ADR-056). Copy once per step, or vary the step content by template. What your view must supply: form this step's own form (delivery / payment fields) steps [{label, status}] where status is "complete" | "current" | "upcoming" order_summary [{label, value}] definition-table facts for the basket checkout_state "ready" | "empty" | "error" This page is the mid-flow checkout step (delivery details), not the separate review-before-submit archetype (auth/review.html) and not a marketing pricing page. Brickwork ships no payment provider, cart model, or URL. HOW THE FLOW WORKS, matching app/onboarding.html: each step is an ordinary Django page. POSTs go to the current URL; valid saves redirect to the next step; invalid re-renders with bw_form errors. "Back" is a plain link. States: checkout_state is the page's real branch. "ready": stepper, order summary, delivery form. "empty": basket has nothing to check out (_empty_state). "error": checkout could not load (bw_alert danger). Form valid/invalid: bw_form renders both. LOADING: not applicable for the default server-rendered path. Accessibility: inherits shell/centred.html; stepper uses a native
Step 2 of 3. Confirm where we send the invoice, then continue to pay.
{% include "brickwork/components/_stepper.html" with steps=steps %}