Typography #205

jelbourn opened this Issue Mar 18, 2016 · 11 comments


None yet

7 participants



Combination of documentation and CSS.

@jelbourn jelbourn added the feature label Mar 18, 2016
@jelbourn jelbourn added this to the alpha.3 milestone Mar 18, 2016
@jelbourn jelbourn modified the milestone: alpha.8, alpha.3 Apr 21, 2016

can we add it per component or use typography.scss ?

@sendilkumarn sendilkumarn referenced this issue Jun 8, 2016

typography - added #656

3 of 3 tasks complete

if this is fine I will update the remaining components

jelbourn commented Jun 8, 2016

To clarify: this issue is about making typography styles available for users to have in their own applications. I'm going to mark it as blocked since this will be influenced by how we approach theming as well.

@jelbourn jelbourn added the blocked label Jun 8, 2016
@jelbourn jelbourn referenced this issue Jun 20, 2016

Change MD font #724


what's the implementation plan for typography? Are you guys planning on making this be a web component, or basically a stylesheet that will need to be imported/required into app components individually?

I've been debating the "proper" approach to typography and how best to componentize re-usable styles that generally are "global" in nature but dont really need a web component to be executed.

If you could outline some thoughts on your approach and the pros/cons thereof, that would be awesome!


Current thinking is to have an @angular2-material/typography package that includes a css file that you can drop into a <link> element in your index.html (or concat into other css files with your own build). We haven't finalized on this approach yet, though.


with shadomDOM coming, and native in angular2, will that approach work? I've done a little bit of testing and it seems that this approach wont work since styles in the parent page wont bleed into a shadowDOM component...


I stumbled across this today while looking for an answer to the following: For applications starting to use Angular Material 2 today, prior to the typography implementation, what is best interim short-term solution for styling application content that is not a angular-material Component? For example, is it best to grab one of the other Material implementations, and use it alongside, for styling other content? Any advice for which one fits in with the least trouble?

krigton commented Oct 12, 2016 edited

Does it makes sense using typography from material 1 (no shadowDOM usage), untill this at least started?

krigton commented Oct 17, 2016

Will typography support theming? Like using different font for md-display and body copy.


@jelbourn jelbourn modified the milestone: alpha.8 Nov 1, 2016

@krigton it's blocked cause of theming, so I would say it will.

@jelbourn jelbourn removed the blocked label Nov 14, 2016

We've started using a webpack loader to override styles, since CSS comes bundled in we can't actually change much, only colors.

We also had hard time changing the font.

This is the loader angular2-restyle-loader
It's fresh out of the oven.

We use it to re-compile SCSS so we can set the variables.
It can also do a lot more with higher maintenance risk.

For example, you can restyle the slide toggle

To this:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment