Okay, I read the W3C Schools CSS tutorial yesterday, I'm following you better. 'Course, I'm not a wizard. Yet.
Yeah, I posted above you with my current solution. I'll be adding a manifest, then I think I'm pretty complete with meta -- but of course, I'm still open to suggestions/improvements.
I don't want to clutter the markup with too many classes and pseudo-classes. At least for the meta-info, I'd pretty much like to keep it all in the head, and use it consistently so that it becomes easy for anyone to write new CSS, to extract data for conversion to other formats, etc.
And I think I disagree with you only because I don't want any of this stuff to appear in the book as one reads (except for some stuff in the verso) so there's no reason to add more code to obscure it or reveal it. It's just there for tools/utilities, and for reference when someone wants to look under the hood for any reason. Meta on the structure is just a polite thing: "Here's every element, class and relevant ID we're using in the document, and how we're using them -- no need to try to determine it all again by hand and eye."
Not home now, but I'm gonna keep going with this. I'll add the manifest next, then I think I'll move on to determining elements and classes and etc. for the various pieces of a book.
Your comments about <h> vs. <div>s are right on (and thanks for educating me regarding <div>s.) I'll definitely be doing that, or some variant of it.
m a r