> For some reason I'm having a hard time wrapping my head around how to
> use the above classes...
> So, is the concept/practice to use .h1 on an h3, that is if you want
> that h3 to have the h1 look/feel?
> Or, better example, would I use a .h3 class on an nested <h1> (in a
> nested html5 <section>) if I want that <h1> to look/feel like a <h3>?
> What's the rule of thumb here?
> Sorry for my ignorance. :(
> Thanks!
> M
> --
> You received this message because you are subscribed to the Google Groups
> "Object Oriented CSS" group.
> To post to this group, send email to object-oriented-css@googlegroups.com.
> To unsubscribe from this group, send email to
> object-oriented-css+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/object-oriented-css?hl=en.
>> For some reason I'm having a hard time wrapping my head around how to
>> use the above classes...
>> So, is the concept/practice to use .h1 on an h3, that is if you want
>> that h3 to have the h1 look/feel?
>> Or, better example, would I use a .h3 class on an nested <h1> (in a
>> nested html5 <section>) if I want that <h1> to look/feel like a <h3>?
>> What's the rule of thumb here?
>> Sorry for my ignorance. :(
>> Thanks!
>> M
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Object Oriented CSS" group.
>> To post to this group, send email to object-oriented-css@googlegroups.com
>> .
>> To unsubscribe from this group, send email to
>> object-oriented-css+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/object-oriented-css?hl=en.
> --
> You received this message because you are subscribed to the Google Groups
> "Object Oriented CSS" group.
> To post to this group, send email to object-oriented-css@googlegroups.com.
> To unsubscribe from this group, send email to
> object-oriented-css+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/object-oriented-css?hl=en.
But, at least from what I have experienced so far, the major drawback
to the above naming system/convention is that it is hard to remember.
:(
> In which case you can use it like this:
> ... <snip> ...
> I find this method a tiny bit easier to conceptualize.
Definitely! Thank you so much for the clarification, I really appreciate it. :)
Based on the little testing I've done so far, I think I might go with
the .h1, .h2, .h3, .h4, .h5, .h6 classes, just because I feel like
that's something that I can remember.
Would you think it was crazy to have .h7, .h8, .h9 classes? Or, would
it make sense to just "extend" existing classes and call the new
headings something like ".category" (I think that was what Nicole's
article was hinting at)?
On Thu, Sep 27, 2012 at 3:59 PM, Jamund Ferguson <jam...@gmail.com> wrote:
> That's how we use it at odesk. Slightly larger example:
Awesome! Thanks Jamund and Nicole for the examples! I really appreciate it.
So, Jamund, does your CSS have .h7, .h8 (and above) named heading classes?
I think the major thing that threw me off before asking you folks is
that the class names appear to be tied to the HTML element names...
But I don't see why I could not do .h7 and above for names (or, does
that sound kinda wacky?).
Sorry if I sound like a lunatic... I tend to over-think these types of
things. :D
On Thu, Sep 27, 2012 at 5:09 PM, Micky Hulse <rgmi...@gmail.com> wrote:
> On Thu, Sep 27, 2012 at 3:59 PM, Jamund Ferguson <jam...@gmail.com> wrote:
> > That's how we use it at odesk. Slightly larger example:
> Awesome! Thanks Jamund and Nicole for the examples! I really appreciate it.
> So, Jamund, does your CSS have .h7, .h8 (and above) named heading classes?
> I think the major thing that threw me off before asking you folks is
> that the class names appear to be tied to the HTML element names...
> But I don't see why I could not do .h7 and above for names (or, does
> that sound kinda wacky?).
> Sorry if I sound like a lunatic... I tend to over-think these types of
> things. :D
> Cheers,
> Micky
> --
> You received this message because you are subscribed to the Google Groups
> "Object Oriented CSS" group.
> To post to this group, send email to object-oriented-css@googlegroups.com.
> To unsubscribe from this group, send email to
> object-oriented-css+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/object-oriented-css?hl=en.
On Thu, Sep 27, 2012 at 4:16 PM, Jamund Ferguson <jam...@gmail.com> wrote:
> We have about 10 headers, but they're all variations of h1 through h5.
> I don't think there's a right and wrong about this, but you'll see things
> like this
Ooh, that's cool! Great tips and very inspirational. :)
Thanks for sharing!
Thanks to OOCSS, you and Nicole, I'm feeling better about the
direction I'm heading in... Thanks again!!!!
Cheers,
Micky
P.S.
I'd still be interested in seeing other folks CSS variations on this
topic... I find this kind of stuff fascinating. Btw, Nicole, that
http://csswizardry.com article was a great read, thanks for the
linkage!
I like to take my cues from the W3C and HTML itself... ie they decided a
long time ago not to do:
<h-primary>
<h-secondary>
or
<h-alpha>
<h-beta>
They did something much simpler, more performant (smaller) and universally
easier to understand and remember:
<h1>
<h2>
FWIW, I tend to do it like this:
h1, .heading-1 {}
h2, .heading-2 {}
h1 = something that is semantically the most important heading on the page
.heading-1 = something that just needs to look like the most important
heading on the page
On Thu, Sep 27, 2012 at 5:06 PM, Micky Hulse <rgmi...@gmail.com> wrote:
> Hi Nicole! Thanks so much for your quick and helpful reply, I really
> appreciate it. :)
> On Thu, Sep 27, 2012 at 3:23 PM, Nicole Chung <nicole.ch...@gmail.com>
> wrote:
> > I'm taking it right from this article
> Oh, nice! I had not seen this article before. Thank you for the
> linkage, reading now.
> But, at least from what I have experienced so far, the major drawback
> to the above naming system/convention is that it is hard to remember.
> :(
> > In which case you can use it like this:
> > ... <snip> ...
> > I find this method a tiny bit easier to conceptualize.
> Definitely! Thank you so much for the clarification, I really appreciate
> it. :)
> Based on the little testing I've done so far, I think I might go with
> the .h1, .h2, .h3, .h4, .h5, .h6 classes, just because I feel like
> that's something that I can remember.
> Would you think it was crazy to have .h7, .h8, .h9 classes? Or, would
> it make sense to just "extend" existing classes and call the new
> headings something like ".category" (I think that was what Nicole's
> article was hinting at)?
> Thanks again! Much appreciated.
> Cheers,
> Micky
> --
> You received this message because you are subscribed to the Google Groups
> "Object Oriented CSS" group.
> To post to this group, send email to object-oriented-css@googlegroups.com.
> To unsubscribe from this group, send email to
> object-oriented-css+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/object-oriented-css?hl=en.
> On Thu, Sep 27, 2012 at 3:59 PM, Jamund Ferguson <jam...@gmail.com> wrote:
>> That's how we use it at odesk. Slightly larger example:
> Awesome! Thanks Jamund and Nicole for the examples! I really appreciate it.
> So, Jamund, does your CSS have .h7, .h8 (and above) named heading classes?
> I think the major thing that threw me off before asking you folks is
> that the class names appear to be tied to the HTML element names...
> But I don't see why I could not do .h7 and above for names (or, does
> that sound kinda wacky?).
> Sorry if I sound like a lunatic... I tend to over-think these types of
> things. :D
> Cheers,
> Micky
> --
> You received this message because you are subscribed to the Google Groups "Object Oriented CSS" group.
> To post to this group, send email to object-oriented-css@googlegroups.com.
> To unsubscribe from this group, send email to object-oriented-css+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/object-oriented-css?hl=en.