menu

Figma

Figma is the first collaborative UI design tool built in the browser. Join our growing community and kick off a conversation!

Channels
Team

Text Styles

August 4, 2017 at 8:10am

I know this has already been suggested on Twitter but I thought i'd make a formal note here (Considering how important it is)


August 4, 2017 at 2:12pm
Hey Amil! Thanks for making it "formal". I appreciate you making each feature request a unique thread too. Hopefully, this will make it easier for people to kick off conversations about why each of these features are important and some of the use cases they solve. That's MOST helpful for the team here.
  • reply
  • like
As for text styles, yes, this is definitely one of our most commonly requested features. For now, the model has been that we use Components and nested instances to manage "state" and text styles.....like this......
  • reply
  • like
  • reply
  • like
This doesn't fully solve the issue that *actual* text styles solves, but maybe it will help for now.
like-fill
1
  • reply
  • like
Ah got it, nest-ception. Not a problem, the first solution is rarely the best solution so I find conversation around all these topics not only interesting but vital for the product, and indeed all products. Apologies for the feature requests are coming in fast and frequent, but I guess part of me is so excited at the prospect of fully implementing Figma across our global company that I can't wait for it to be (even more) unbelievably great to work in!
like-fill
3
  • reply
  • like
We're excited that you're excited! Also, "nest-ception"! LOL! I think I may need to steal that from you.
like-fill
2
  • reply
  • like
I agree with Amil here, the usage of text styles is very helpful when working on projects relying heavily on typography. I think that glancing at how InDesign (I partly come from a book design background) handles this could be useful, here's a few things I think is done well there:
like-fill
5
  • reply
  • like
* Inheriting from other styles: For example, Heading 2 is based on everything set in Heading 1, but changes font size and line height. Heading 3 is based on everything set in Heading 1, but again change font size and line height, perhaps also changing font style from to Regular to Medium to offset the size change (if for example looking for a single-thickness look in headings). Heading 4 is based on Heading 3 and inherits everything from that (including change of font style) but changes size further. Then suddenly you decide to change the color and font used, so you do that in Heading 1 and it all trickles down. So it's nest-ception, but different ;)
  • reply
  • like
* Separating paragraph style and character style: This means that you can set every style by marking a box, but also over-ride some factors (i.e. commonly things such as underline, character color, font style, font options such as small caps, etc.) without changing any of the other factors. This helps when for example styling inline links, which would then retain character color and underline, but inherit a change in paragraph style from font, font size and line-hight. Could be seen as messy by some users I guess.
like-fill
3
  • reply
  • like
* Setting padding before and after paragraphs: Very useful when you want to fine-tune the typography but don't want the mess of separating text into blocks to space manual since the content is not yet finalised for the prototype and text length is unknown.
like-fill
4
  • reply
  • like

December 8, 2017 at 12:49am

Being able to apply styles to text would be amazing. I use components now but that's with my particular use case. It would be fantastic if we could have a set of global styles and and apply the to text on the page. Thanks!

  • reply
  • like

December 18, 2017 at 11:23pm

Oh yes - please please please do this. Not having styles is killing me. I'm also REALLY missing tabbing in the text. Being able to set tab would be really helpful.

like-fill
2
  • reply
  • like

January 3, 2018 at 4:41pm

I can +1 on this. Text styles would be a great addition to the current product.

  • reply
  • like

January 4, 2018 at 1:39am

+1 to tabs, as well as bullets and numbering would be super helpful!

  • reply
  • like

January 8, 2018 at 10:42pm

any news on this one Figma Team?

  • reply
  • like

January 18, 2018 at 3:31pm

Oh god yes, we really need this to manage our design system!

  • reply
  • like

January 28, 2018 at 5:47pm

I second this. It would be great. It's nice to be able to use Components for some of this, but it's not enough to handle (for instance) spaces between different blocks of text in a consistent way.

  • reply
  • like

February 1, 2018 at 9:14pm

Would love to have this. It's one of the only things I really miss having in Sketch. Would speed up my workflow quite a bit.

  • reply
  • like

Alternatively, if you could override width or auto resize properties on text instances that would be fine as well!

  • reply
  • like

February 2, 2018 at 12:13pm

Hey there, +1 from me, too. This would really help me convincing my design team (all on PCs, so Sketch is no option) to (finally!!) switch from Photoshop to something useful.

  • reply
  • like

February 15, 2018 at 3:48pm

+1 here too. Hard to keep track of styles even across a small project.

  • reply
  • like

February 20, 2018 at 7:07pm

Text styles would make component creation super duper

  • reply
  • like

+1 . Using components works if you simply need to change from one font style to another by changing the component but if you need to reset the component your copy reverts to the component copy.. Not fun

  • reply
  • like

March 6, 2018 at 9:46pm

+1! Right now I've been using text as components, but they end up getting a bit wonky after using them for awhile

  • reply
  • like
Show more messages
private
This channel has been archived