In our system we use a medium weight of 500 which indicates Bold for our brand. Is there a way to control the new cmd+B style when applied to a text string and not use the currently assigned 700 (Bold)?
Thanks
In our system we use a medium weight of 500 which indicates Bold for our brand. Is there a way to control the new cmd+B style when applied to a text string and not use the currently assigned 700 (Bold)?
Thanks
Hey @AGuyCalledGary , welcome to the community and thanks for reaching out to us!
Unfortunately, it’s not possible to customize it. Still, I have passed it along to our team for consideration! In the meantime, I’ve switched your topic as ‘Share an idea’ so others in the community can share their feedback and vote up your idea
Edit: In the meantime, here’s a workaround shared by the Figma team that can help you: you can go into the font file and change the fonts metadata to use 500 for the bold style. Then upload it as a new shared font and switch to using that font instead.
Caveats: you need to own the font and you would need someone with experience working with font files.
I know you provided a ‘hack’ to resolve the issue, but that doesn’t make sense if this is moved into development. Then you have to explain every time that you had to do a hack to make things work in Figma. A bit of an odd suggestion.
It generally makes sense that there would be some fallback setting you could set up in your design file that managed these types of settings. For example, the same would be necessary if a font were italic and italic + bold. It should be a manageable addon to provide. Just some simple basic settings for your design file to manage such challenges.
Many designers today don’t really use bold as we would have some years ago. Now, it is mostly Medium or Semibold, so it makes sense to have this on your to-do list soon. I have had this issue in a few projects now, and it can only be fixed with your hack or by adding a regular and bold version for all typographies you make, which doesn’t make sense when the solution on your end could be much simpler and more efficient. It would optimise our workflows simultaneously in one go rather than what you suggest.
Best regards,
Morten.