Spread CTA — where the question goes
Internal prototype · spread CTA v2 · nothing here is wired to a server
The question, added to the spread
The top-slot spread widget exactly as it ships — seeded with the article's two cards, real 78-card typeahead, real copy — with a box for the question they asked. The card mechanics are fixed and faithful; what changes between tabs is only how the question gets asked. The pane underneath shows what it is for: the chat opener with the question against the opener today, cards only.
Tarot · a pairing
Two of Swords and Two of Wands
Two cards, and both of them are standing still. The Two of Swords is blindfolded with a blade in each hand. The Two of Wands is on a parapet holding a small globe, looking out at a distance it hasn't walked yet.
Pulled together, they aren't a forecast. They're a description of a particular kind of stuckness — the refusal to see and the fixation on the horizon are the same move, made in two directions.
mid slot · two-tap stance widget (unchanged)
For a customized reading, tell me why you pulled these cards…
bottom slot · escrow CTA (unchanged)
What question were you holding when you pulled these cards?
What changes
What this is really trading
-
The question has to reach the opener, or none of this counts. Your own note at the time: "we need to pass the question info to the chat opener too." The cards already ride through as
card=/card2=; the question needs its own carry and a place to land. That is the build, and the copy is the easy half. - This block sits at the TOP of the page. It is the first thing a reader meets, before they have read a word — which is exactly why it earns its slot (they arrive already asking "I have five more cards, what do I do with them?"), and exactly why adding height to it is not free. Variant 3 exists to keep the top block the same size.
- The two lower CTAs already ask the question. Escrow at the bottom asks it verbatim. So this is not the only place it gets asked — it is the place where the reader is most engaged and least far along. Worth knowing what happens to escrow submissions if the top block starts collecting the same thing.
-
The submit is an
<a>, not a form. It navigates cross-domain with no JS at all, and its href is inspectable in a test. A question box does not change that — the text rides the URL — but it does put reader-written words in a query string, which is worth a look before it ships. - Nothing here predicts conversion. This is for feel. Instrumentation is already in place per slot, so whichever version you like can be measured against the current one properly.