Bold / italic options greyed out on blog post / rich text modules (custom font)

Hello! :hand_with_fingers_splayed:

I’m wondering if anyone has come across this.

My client has a theme using a custom font and on their blog the bold and italic options are greyed out (I also notice this on rich text modules):

The font is loading correctly across the site, I have a fonts folder with the font files and a font.json file with the variations you see above based on this documentation.

For this particular client they didn’t have the right font files (the above is testing with demo files) so I’m using an Adobe Typekit link they sent (with all the variations).

However, I’ve noticed this is also an issue on another client’s site with custom fonts.

Does HubSpot not show bold/italic options with custom fonts? Are there workarounds?

:thinking:

I have the same issue. It’s a bug I believe however not sure of the specific cause. It seems that when you’re in a specific view (not expanded view), that it will default to a custom font even if one is NOT selected (aka, your theme sets the default font via CSS instead of on the specific text).

However, if you click on the module → edit module → expanded view, the custom font is not selected and you can bold and such as normal. Since my theme sets the font in the CSS, it will inherit the font correctly and bold/italics correctly. It’s weird.

I haven’t gone in depth in trying to figure out the exact cause (guessing it’s a default font set on the brand kit?).

Thank you for confirming it’s not just me! However, it looks like it may be a feature and not a bug based on Anton’s reply.

Hey @Stephanie-OG,

Please refer:

These previous community threads might help you.

Regards,

Hey @Stephanie-OG,

a quick designer insight and why this might be happening.

The bold and italic options in any text tool (Rich-Text, MS Word, Google Pages …) are just imitating a bold, italic version of a font.

As most people are not designers or simply don’t care about pixel-perfect font settings, the “bold”/“italic” button kinda solves the “problem”.

But once you really dive into typography, how fonts are getting designed and what an immense amount of work it is to put out a great font, you’ll quickly realize that these two options are not real bold/italic versions of the font.

Just a little comparison:

The same font (Roboto Medium),

the black one is “italic button” version, the red one is the real italic version of it

While those differences in this case might be somewhat neglectable, it’s exactly those differences that might change the whole appearance of a website, printed file… And this is why any designer is having a heart-attack when the customer tells him “Can’t you just click the “i” button to make it italic”?

And this is what I think is happening in this case.

Since you’ve uploaded proxima nova with Bold and Italic versions, HubSpot might deactivate those features in the RTE. I’m could imagine, because there might have been a designer involved who told the devs that it’s a big “no-no” to have a bold type and make it “bold” or having an italic font and making it “italic”.

I’ve tried Roboto in MacOS Pages (something I haven’t used in years).

If I click the italic button, it automatically changes the font style to the italic version of it. Same with bold… Might be different with MS Word, but since I don’t have it, I’m unfortunately not able to test it.

Besides this, Proxima nova is available as an Adobe Font.

I’m pretty sure that you have a few reasons why you’re implementing it as it’s stated in the docs - to be honest - I’ve never used it.

On one hand, I’m oldschool and I don’t want to over-engineer stuff.

On the otherhand I don’t want to put design desicions in clients hands :grinning_face_with_smiling_eyes:

The way I’m implementing custom fonts is a different one than the docs (the good oldschool way).

  1. If the font have some sort of embed code like something like Adobe Fonts, I’m putting it into the base.html or theme.css. If it doesn’t, I’m uploading the ttfs, otfs… to file-manager or design-manager.
  2. Adding @font-face rules to the CSS if they dont have an embed code.
  3. Adding CSS styles for bold, italics etc. so it’s easier for the client
  4. Providing custom RTE modules without font selection and depending on use-case a lot less options
  5. When a RTE is not required (Headlines, buttons …) im using simple text fields and - depending on use-case of it adding predefined styling options in the content or style tabs

I know it’s often an immense amount of work, but you might want to think about it :slightly_smiling_face:

best,

Anton

I love this answer, thanks!

I remember learning a bit about typography back in the day but it is indeed a fairly complicated (and kinda nerdy) subject.

In the past I’ve definitely added custom fonts the “old school” way, I suppose I tried the docs way becuase then it adds the font to the theme fields drop-down. Do you then remove the font option from their theme settings? I do give my clients design decisions most of the time :sweat_smile:

This particular client is actually using an Adobe Typekit link anyway but if I just remove the font.json file it no longer loads the font (at least in the editor). In their case, I’ll probably just re-jig the thing with the @font-face rules in main.css.

I’ll have to have a think about the best way forward the next time I come across a custom font.

Your welcome :slightly_smiling_face:

To be honest, I have created my own solution for not relying on the font field in themes. :slightly_smiling_face:

For custom themes, I don’t use the font field as long as the client doesn’t use Google Fonts.

Simple answer is: Because of UX. As the font is something that doesn’t get changed that frequently and is a major setting, sometimes less options are better to not let the design go down.

Something that I’m always providing tho, are all major font-sizes(h1-h6 for all breakpoints, buttons and other things that might be in the custom theme). Doing so the client/user can always fine-tune them. without messing to much.

Also I’m always deactivating the default rich-text and provide a custom one without font-family, font-colors and such. It’s way more work for sure, but personally I don’t want to see something like Arial/Verdana in combination with an actual font from Adobe, MyFonts etc. :slightly_smiling_face:

I posted about this BUG recently and was redirected here.
This is definitely a bug clients want a bold button I’ve installed a bold font for them, let them have the bold button!
It worked fine before I added it to the brandkit or as custom font to the theme (via the font.json)
First rule of UX design - Use the same buttons that every other tool out there uses.
This is the process my clients used to do:

  1. Click the Big Friendly Familar B

This is the process they now have to do:

  1. Click the B - Nothing Happens
  2. Click the font drop down
  3. Decide what the difference is between “BrandKit” and “Custom Font” - I removed the font.json so I assume Custom Font also appears when you add it to brandkit
  4. Second guess which is their main body font then click the font name
  5. Finally get a drop down of Light, Regular, Medium, Semi Bold, Bold as well as italic version
  6. Try and decide which variation to use and probably use something that our designers would prefer they didn’t use.

Please someone at HubSpot let them just press the big friendly B!!

My original post.
https://community.hubspot.com/t5/Blog-Website-Page-Publishing/Adding-Custom-Brand-kit-Fonts-breaks-bold-and-Disables-Bold-and/m-p/1251350

Hi @matt_scott and thanks so much for sharing these details and your experience with the HubSpot Community!
I can confirm that this is a known limitation, and I hear you, the bold button is a familiar and expected part of rich text editing, especially when clients rely on it for quick formatting.

I’ll make sure your feedback is shared with our product team, including the impact that changes to custom or Brand Kit fonts are having on editing workflows.

Thank you again for taking the time to outline this so clearly!
Bérangère