Global typographic styles suck #4

Open
anthonyshort opened this Issue May 6, 2012 · 5 comments

Comments

Projects
None yet
4 participants
@anthonyshort
Owner

anthonyshort commented May 6, 2012

Comments for the post "Global typographic styles suck"

@kaelig

This comment has been minimized.

Show comment
Hide comment
@kaelig

kaelig May 6, 2012

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

kaelig commented May 6, 2012

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
@anthonyshort

This comment has been minimized.

Show comment
Hide comment
@anthonyshort

anthonyshort May 7, 2012

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.

Owner

anthonyshort commented May 7, 2012

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

This comment has been minimized.

Show comment
Hide comment
@kaelig

kaelig May 7, 2012

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.

kaelig commented May 7, 2012

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.

@gandhiShepard

This comment has been minimized.

Show comment
Hide comment
@gandhiShepard

gandhiShepard Sep 12, 2014

This makes so much sense.

This makes so much sense.

@kevinSuttle

This comment has been minimized.

Show comment
Hide comment
@kevinSuttle

kevinSuttle Dec 11, 2014

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…

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