Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Global typographic styles suck #4

Open
anthonyshort opened this Issue · 5 comments

4 participants

Anthony Short Kaelig Benjamin Gandhi-Shepard Kevin Suttle
Anthony Short
Owner

Comments for the post "Global typographic styles suck"

Kaelig

I have used this approach on a few CMS that required .wysiwyg classes for copy blocks, but in the end it generated more clutter and specificity issues. But I see your point.

In most cases, think typography should be at the center of the design, thus becoming the global styles.

Both approaches aren't "bad" or "good", they just are two means to different ends:

  • building the UI around the content: global typographic styles
  • putting content in a UI: scoped typographic styles
Anthony Short
Owner

I've found that pulling it all out how made everything less messy and specific. But of course, it depends on the project. I don't really believe that the copy block styles are the centre of the design anymore. They are theorically but not in terms of CSS structure. In app layouts with lots of complex UI elements it's much more obvious.

Kaelig

Exactly, good developers should consider both approaches depending on the project. For a blog, global styles may be the best answer, whereas for a web app, scoped styles are more likely to be a better fit.

Benjamin Gandhi-Shepard

This makes so much sense.

Kevin Suttle

I feel like just defining copy styles in Sass %placeHolders and extending them in your selectors, vs classes in your HTML, is the most scalable and flexible approach. http://ianstormtaylor.com/oocss-plus-sass-is-t…

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.