Quote:
Originally Posted by Hitch
Unasked-for-comment: if you plan to use your ePUB for Kindle-building, don't use the Blitz CSS. You need a lot more experience under your belt to understand what's happening with all the inheritance functionality in that, and a lot of it will not work for MOBI and it certainly won't for KF7.
Hitch
|
I do use the Blitz reset.css; I hope that doesn't cause problems. In my main css file I use @import to pull it in from the Styles directory. I've always wondered if it's safe pulling it in that way.
I'm also wondering about the best/safest way to set up what I think of as boxes/blocks that go between paragraphs. I was following the guidelines of standardebooks.org and using blockquotes for everything until tex2002ans pointed out the error of my ways. I couldn't think of a way to make a generic inter-paragraph block with a div since divs can be used in other ways as well so I didn't want to attach any css to a plain div. Then I saw a response on stackexchange about how you can attach several classes to an html tag so now in my css I have div.block for the generic block div, and for the other ones, div.letter (italics), div.notice (sans-serif), etc., and in my html I use 'div class="block letter"'. I think another way to set up the generic div would be to use something like 'div.letter, div.notice, etc. { generic div block stuff here }' and then, as before, div.notice would have stuff specific to it.
An important goal for me is to design the css so that I can use as few classes as possible in the html. So that means combinators, +, >, space, etc. Again, I'm not sure how portable that is.