View Single Post
Old 08-08-2020, 03:12 PM   #13
phillipgessert
Addict
phillipgessert ought to be getting tired of karma fortunes by now.phillipgessert ought to be getting tired of karma fortunes by now.phillipgessert ought to be getting tired of karma fortunes by now.phillipgessert ought to be getting tired of karma fortunes by now.phillipgessert ought to be getting tired of karma fortunes by now.phillipgessert ought to be getting tired of karma fortunes by now.phillipgessert ought to be getting tired of karma fortunes by now.phillipgessert ought to be getting tired of karma fortunes by now.phillipgessert ought to be getting tired of karma fortunes by now.phillipgessert ought to be getting tired of karma fortunes by now.phillipgessert ought to be getting tired of karma fortunes by now.
 
phillipgessert's Avatar
 
Posts: 318
Karma: 3200000
Join Date: Oct 2015
Location: Madison, WI
Device: Kindle 5th Gen
Quote:
Originally Posted by hobnail View Post
I have things that are "blocks" but not really block quotes; letter, telegram, poem, notice (sign), etc. So I use, for example, <div class="block poem">. The common / shared stuff is in the css for block, then the specific stuff is in the others (div.letter, div.poem, etc.).

It seems to me that I could instead use
Code:
div.poem, div.letter, div.telegram, etc. {
    /* common block stuff here */
}
div.poem {
    /* poem specific stuff here */
}
I don't know if one is better than the other.
I think it’s ok to use blockquote for those things too, given that they are quotes from an outside source. Admittedly feels a little weird in conversation to “quote” a sign, but I think it does make some sense in a markup semantics context.
phillipgessert is offline   Reply With Quote