Skip to main content

Love the new Typography Variable release, but it falls short for our use case. Our goal is to use variable modes to switch styles between our 3 brands. 2 of those brands use all caps for headings, the other brand uses sentence case.


We need to be able to bind a variable to the case of a character style (As typed, Uppercase, Lowercase, Title case, Small caps).




  • Without this capability, when switching modes from brand 1 to brand 2 for example, we are getting the default case for the character style (sentence case coming from brand 1).




  • We would then have to go through our designs and manually type in all caps for all instances of headings in brands 2 and 3. Certainly not ideal and will lead to inconsistencies / places where manually typing in all caps are missed if we went this route.




Until binding a variable to the case of a character style is an option, using typography variables isn’t feasible for our use case.

I am also having the same issue. Type variables are unfortunately not suitable for a multi-brand library. Without type variables we’ve had to get creative on how we pass type styles to devs via REST API. Not only can we not pass off case and decoration variables, but sometimes our fonts’ “weight” also carry that font decoration which we cannot successfully separate from the numerical value. (i.e. bold italic). As a work around we are essentially pasting in the entire font CSS into a string variable to pass type styles to dev. However this is only useful for development since that’s not a usable variable for designers.


Love the potential for this feature but cannot use it at this time.

Running into the exact same issue. Without support for Case or for example text decoration. We seem to have hit a dead end and can’t use it for multiple brands.

I have the same issue, I mean at this point it’s a want that can make it easier for use of variable on Text.

Voted. This feature is essential for multi-brand systems

without out, variables are A LOT less powerful

Need this please for multi-brand Design Systems!

I love this suggestion ❤️. This feature would be super valuable for my org. If this feature was supported my team could cut down to one type style library vs many. Designers having to constantly swap typography libraries to get around this is a big point of friction in our design workflow.

Even single brand design systems need this to maintain parity with what’s in code and reduce the chance for human error and it’s definitely needed for multi-brand single design systems.

Hey! I’ve had a similar issue. I’m working in a multi-brand system where brand A had UPPERCASE enabled by default, and brand B did not. In my case (and since it’s only two brands), I solved it through documentation, where during development they activate the text-transform for all the labels in the components of brand A, but not in brand B.

I’m facing the same issue. we need this feature.

+1. My buttons have a title case text layer and an identical all caps text layer, each bound to a variable that turns it on/off depending on brand. It’s a messy, cumbersome and all around absurd workaround, not to mention the fact that it’s not 1:1 with dev.


Please add this feature. It’s literally just CSS text-transform. Please.

I wish the team would acknowledge this, im running into the same issue, we have 17 brands, some title case some full caps (for headings). Designers will have to look at best practices for each brand (And I will have to make that documentation). Even if implimented in a crappy way would help, also need line heights as % .

Reply


Terms & ConditionsCookie settings