Last verified: September 19, 2026
What You Can Now Do
Context Memo now lets you display daily memos with a tall photo band hero section and poster-size uppercase titles, so a memo opens with a visually striking layout instead of a standard text header. The difference is immediate at the top of the page: a full-width image band holds the vertical space, and the title sits in large uppercase type across it. The decision this changes is a small one you make per memo: whether the daily memo leads with an image-forward hero or stays with your existing header treatment. If a daily memo is doing double duty as something you share in Slack, drop in a newsletter, or link from a campaign, the new hero gives the first screen more weight without you touching the body copy.
Where It Is in Context Memo
The new hero lives in the layout builder for daily memos. Open a daily memo, go into the layout builder, and the hero section now offers the tall photo band option alongside the existing hero styles. The change also runs through widget rendering and the memo specification logic, which means the hero you select in the builder is the hero that renders on the published page and in any widget that surfaces that memo. No separate template file to maintain.
How to Use It
- Open the daily memo you want to restyle and enter the layout builder. You'll see the hero section listed as an editable block at the top of the memo structure.
- Select the tall photo band hero option. The preview redraws with the taller image band and the uppercase title treatment applied to your existing title text.
- Set the hero image. Choose a photo with a clear focal area that survives being cropped to a wide band, since the band is taller than a standard header image and will fill the width of the memo.
- Check the title at its poster size. Uppercase display type is unforgiving with long titles, so shorten the title if it wraps past two lines in the preview. The body of the memo is unaffected.
- Publish or republish the memo. The hero renders on your own domain, and the memo specification carries the new hero through to widget rendering, so embedded placements pick up the same layout.
- Reopen the published page and confirm the hero above the fold on both desktop and a phone-width viewport before you share the link.
Why We Built It
Customers told us their daily memos read well but didn't look like anything. The content was doing the work of shaping how models describe their category, and the page itself was forgettable the moment a human landed on it from a Slack link or a campaign email. That cost them twice: internal stakeholders didn't treat memos as real published assets, and the memos that did get shared with buyers had a first screen that gave them no reason to keep reading. A bolder, more prominent hero makes the daily memo something a marketer is willing to put in front of an executive.
What It Does Not Do Yet
This is a presentation change, not a content change. A few limits worth knowing before you restyle a batch of memos:
- Image selection is manual. You choose and upload the hero photo yourself. There's no automatic image pull or generation tied to the memo topic.
- Title casing is applied at render. The uppercase treatment is visual. Your stored title stays as written, so anything depending on the title string is unchanged, but you can't mix casing within the display title.
- It applies to daily memos. The tall photo band is a hero option in the daily memo layout builder. Other memo types keep their existing hero styles.
- No bulk restyling. You apply the hero per memo in the builder. Reformatting an archive of past daily memos means opening each one.
One thing worth being clear about: a stronger hero affects how humans respond to the page, not how models parse it. Citation behavior is driven by the structure of the memo itself, the schema markup, the third-person neutral voice, and the external citations. A tall photo band doesn't make a memo more citation-grade. It makes an already citation-grade memo something you're proud to link to. If a memo isn't getting picked up across the models you're scanning, the fix is in the body and the source coverage, not the hero.