Last verified: August 25, 2026
What You Can Now Do
Context Memo's landing page builder now gives you three page styles for the same memo: flip, standard, and in-line. The memo content does not change. What changes is how it's rendered, which means you now control whether a visitor reads the whole thing on one scroll, reveals it through a card interaction, or encounters it inside a route you already own. That matters for machine readers too. A crawler parses what the page renders, so the style you pick decides how much of a citation-grade memo is available in full, in order, on first load. The task this changes: picking a page style is now a publishing decision you make deliberately, not a default you inherit.
Where It Is in Context Memo
Open any memo in the landing page builder and look for the Page Style selector in the page settings panel. All three options live there. Flip is now the default on newly created pages, so existing pages keep whatever they were published with until you change them.
How to Use It
- Open the memo you want to publish in the landing page builder. The page settings panel appears alongside the content.
- Find the Page Style selector in that panel. You'll see three options: Flip, Standard, and In-Line.
- Pick the style that matches the job of the memo. Flip compresses a concept into a card interaction, which fits scannable, quiz-style, or comparison content where the reveal itself carries meaning. Standard renders a full-length reading experience with an H1, sections, and scroll depth, which is what most AI crawlers expect from long-form reference content. In-line strips the page chrome so the memo can sit inside an existing blog or docs route without a second set of navigation and brand framing wrapped around it.
- Preview before you publish. Spacing, navigation, and interaction differ across the three, so read the preview the way a first-time visitor would and check that nothing load-bearing is hidden behind a click.
- Save and publish. The style is stored per page, so a pillar reference memo can run as standard while an embedded explainer on the same domain runs in-line.
- Change it later if the page isn't performing. Switching styles does not require rewriting the memo.
Why We Built It
Customers kept telling us the same thing in different words: "the memo is right, the page is wrong." A reference memo written to be cited was rendering as a card interaction, which put half the substance behind a reveal. An explainer meant to live inside an existing docs section was arriving wrapped in duplicate navigation and a second brand header, competing with the page it was supposed to support. Both cases cost the same thing, which is extractable content. Content that only exists after an interaction, or that sits buried under redundant page chrome, is harder for a model to parse in the shape you intended, and harder for a reader to stay oriented in.
What It Does Not Do Yet
The style is set per page, not per brand. There is no brand-level default beyond flip on new pages, and no bulk apply, so if you want every pillar memo on standard you set each one. We think that's the right trade for now, because the correct style depends on what the individual memo is doing, but it does mean a large back catalog is manual work today.
In-line also assumes you already have a route to embed into. It removes the page chrome on the expectation that your site provides it. Context Memo is not a CMS and does not replace one, so if you don't yet have a blog or docs structure to host the memo, publish as standard on your own domain first and move to in-line once the surrounding route exists.
Finally, the selector does not recommend a style for you. It won't read the memo and tell you that a comparison table belongs on a flip card or that a long reference belongs on standard. Use the preview, and use your citation data: if a memo is getting crawled but not cited, the rendering is one of the first things worth changing before you touch the copy.