Last verified: September 30, 2026
What You Can Now Do
Context Memo now lets you place a wordmark underneath body copy when building landing page widgets, giving you more layout flexibility for your page designs. Before this, the wordmark rendered above the copy block and that was the only order available. Position is now a setting you pick. The decision it changes is small but real: whether a visitor meets your name first or your claim first. On a page where the argument carries more weight than the logo, you can lead with the copy and sign it with the mark at the bottom. Nothing about existing pages changes until you change them.
Where It Is in Context Memo
This lives in the landing page builder. Open a landing page, select the widget that holds your wordmark and body copy, and the wordmark position control sits in that widget's settings next to the existing content fields. The value is stored in the widget specification, so the preview and the published page render from the same source.
How to Use It
- Open the landing page you want to change in the landing page builder. The canvas loads with each widget selectable.
- Select the widget containing the wordmark and body copy. The settings panel for that widget opens, including the wordmark position control.
- Set wordmark position to below body copy. The preview re-renders with the mark under the copy block.
- Check the layout at a narrow viewport width before you commit. Vertical spacing shifts when the mark moves, and this is where you will see it.
- Publish the page. The live version renders in the order you set, and because the position is part of the widget spec, duplicating that widget or cloning the page carries the layout with it.
- Repeat per widget if a page holds more than one wordmark block. Position is set at the widget level, not the page level.
Why We Built It
The request came in plainly: "I need more control over where my wordmark appears relative to other content on my landing pages." Until now the answer was to accept the fixed order, which meant your page design bent to the widget instead of the other way around. For teams running memo landing pages as a real publishing surface, that kind of constraint adds up across every page they build.
What It Does Not Do Yet
Two positions, above or below body copy. This is not free placement, so you cannot set the wordmark beside the copy, inline with it, or at an arbitrary offset. Position is also per widget rather than a global default, which means a page with several wordmark blocks needs each one set individually.
More broadly, the landing page builder is built for publishing citation-grade memos and their landing pages on your own domain. It is not a replacement for HubSpot or a full CMS, and it is not trying to be. Keep complex templating, form logic, and multi-step campaign pages in the system you already use for them, and use Context Memo for the pages that need to be structured, schema-marked, and read by AI models.
