Bolding in new email editor | Community
Skip to main content
Level 2
March 3, 2026
Question

Bolding in new email editor

  • March 3, 2026
  • 2 replies
  • 74 views

Hi everyone! I’m playing around with the new email editor and trying to create a test template. It’s not letting me bold (or italicize, etc) specific words...it just bolds the entire text block. It’s the same in paragraph, h1, h2, etc stylings. Is this intentional or a bug? Or is that something you can only do at an email asset level?

Thanks!

2 replies

Level 1
March 3, 2026

Hi Rachel! Sounds like it might be a bug since you should be able to control the text styling both in the template and in an email.

Can you check the source code and make sure the bolded text styling is applying to the specific word and not to the whole section?
 

  1. Click the </> icon to see the source code
  1. Make sure the styling is applying correctly. In this example, the H1 text is bold by default, but you can see I unbolded the “- Test Copy” part 

     

Regardless of how it shows up in the template, when you create an email, that should be an editable text section where you can customize the bolding/italicizing, as well as the font size, colour, etc. If you still aren’t able to edit the text styling in an actual email, there may be some CSS somewhere that’s overriding your styling.

rachelkayAuthor
Level 2
March 3, 2026

Hi ​@gnw_garrison202 ! Thanks for the response 😊

 

I just did a test at both the template level and email asset level. The same thing happens in both. It looks like it’s just changing the font-weight for the entire p tag to bold...not adding a strong tag to those specific words. (I was trying to just bold the words “fermentum bibendum” in the first sentence).

 

Here’s the before HTML:

 

Here’s the after HTML:

 

Seems like a bug I believe, right?

 

Edit: I haven’t added any custom CSS to the template yet as I’ve just started and am only playing around to learn how to use it.

Level 1
March 3, 2026

Can you try changing the Theme settings so that the paragraph text is normal by default? Then once you save that change, can you try bolding just the “fermentum bibendum” text?
 

 

Dave_Roberts
Level 10
March 4, 2026

@rachelkay -- I’m able to both see it work AND not work, depending upon the approach you use to bold the text. In the image above, I’ve highlighted the words “your text” and used the black pop-up bar to edit that specific text to be bold. That seems to work for me. The dropdown control modifies the selected text by adding a span around the text. 
However, when I highlight the text and then use the “B” icon in the Text Styles panel, the entire paragraph changes to bold. This control modifies the selected (parent) element (in this case <p>) rather than the selected text.

The problem here is that the UI is disconnected and one way of bolding text works differently than the other which creates a poor UX. Both are units of the Adobe Spectrum design system so there’s really no reason that they can’t be setup to function the same. This might just be an oversight by the developers or a bug.

 

I’d certainly prefer a unified editing experience -- it seems weird to me that there are the same tools in the popup and sidebar that do different things and that there are buttons in the toolbar which aren’t in the sidebar.

 

I’ve seen you’ve submitted some ideas recently (kudos on hammering thru the new editor and making all these suggestions) -- this might be another one to add to the list. If you do, drop a link here and I’ll vote it up for sure.

rachelkayAuthor
Level 2
March 4, 2026

@Dave_Roberts - YES!! That worked...thank you for the explanation! I noticed the same thing with changing text color in the side bar vs the black bar. I don’t know why I didn’t think to check the same for copy styling. It’s definitely not the most intuitive UX. I’ll be sure to make another Idea post in the community for this one and drop the link here once I do. Thanks again 😊

@gnw_garrison202 - copying you here as well so you can see that Dave let me know what the issue was! Still not sure if it’s a bug or an oversight, but I’m glad at least now I know how to do it. Thank you for your help too!