Last verified: August 29, 2026
What You Can Now Do
Context Memo now lets you set a CTA button color independently from your theme's accent color. Until this release, one accent value drove both the decorative layer (headings, links, dividers) and the functional layer (CTA buttons), which meant brands with a two-color system had to pick which one to honor inside published memos. The new optional cta_color field removes that tradeoff. The decision it changes: you no longer have to choose between keeping your authority color on typography and keeping your action color on the button that converts.
Where It Is in Context Memo
Memo theme settings. The CTA Color field sits directly below the primary accent color input, either in the theme settings panel for an individual memo or in the global brand theme if you want the change applied across every memo on your domain. Both inputs now appear on the same screen, accent first, CTA second.
How to Use It
- Open theme settings for the memo you want to change, or open the global brand theme to apply the color across every memo published on your domain.
- Find the CTA Color field below the primary accent input. Enter a hex value (for example,
#FF6B35) or pick the color from the swatch. - Save, then preview the memo. CTA buttons render in the new value while headings, links, and dividers continue to use your accent color.
- Check the preview at the button's actual size for legibility of the label against the fill. The field accepts any hex value you give it, so contrast is your call, not ours.
- If you want the old behavior on a specific memo, clear the field. A blank
cta_colorinherits the accent color, which is exactly how themes rendered before this release. - Repeat step 2 in the global brand theme once you have a value you like, so new memos pick it up without per-memo configuration.
Why We Built It
The request came in the same shape more than once: "Our navy is for type. Our orange is for buttons. Your editor makes me pick one." Brands running a deep neutral for structure and a warmer color for conversion moments were either flattening their visual hierarchy or dropping their action color entirely once a memo went live on their own domain. That matters more here than on a generic content platform, because memos publish on your domain and are meant to read as a native extension of your site. A button in the wrong color is the detail a buyer notices before they notice anything else, and it undercuts the credibility the memo is there to build.
What It Does Not Do Yet
- The accent color is still a single value governing all decorative elements together. You cannot set headings, links, and dividers to different colors from one another. Only the CTA button has been separated out.
- There is no contrast validation on the new field. If you enter a light hex on a light background, the preview will show it and nothing will stop you from saving it. Verify in preview before publishing.
- Setting the color per memo remains a per-memo action. If you want consistency across a domain, set the value once in the global brand theme rather than editing memos individually.
- Existing themes are untouched. Nothing re-renders and nothing needs migrating, because a blank field falls back to the prior behavior by design.
One practical note on scope: theme controls in Context Memo exist to make published memos match your brand system closely enough to be credible on your domain. They are not a replacement for your CMS or marketing site builder, and we are not trying to make them one. If you need page-level layout control, template logic, or form handling, that work belongs in the tools you already run. What we care about is that the memo looks like it belongs to you when an AI model cites it and a buyer clicks through.
