Quote:
Originally Posted by icallaci
I edit CSS to satisfy my OCD, lol. Unlike JSWolf, I want things spelled out, so I add class="whatever" to bare tags so that I know exactly what each one is supposed to do without traipsing back and forth in the CSS to find the parent class. If I run across a problem while I'm reading (and in some books, there are LOTS of problems--different font sizes, paragraph indents, header spacing--you name it), I want to be able to go directly to ONE class, edit it, and be done. Also, even though most ereaders handle errors by ignoring them, I like my books to be as error free as possible, even if the problems are not visible. I don't want to run into problems in the future if at some point a particular error causes problems. I really don’t care how a book is formatted, as long as it is consistent: I don’t want to “notice” anything while I am reading. It is amazing to me how inconsistent the formatting in some books is, almost as if different people have worked on different parts of it without adhering to any particular standard. And, of course, once I notice something like this, my brain is looking for it, so I can’t concentrate on what the book is actually saying. It sounds like a lot of work, but most of the time it’s not, especially after you develop a routine.
|
I know what the bare tags do. I know what <p>, <hr/>, and <h2> do. I know what a <p> does after an <h2>. I know what a <p> does after <hr/>. I don't need classes to tell me what these do. I know what my own CSS does. You'd get used to it. You don't need classes to satisfy your OCD. You just need to know what the CSS does when there is no class.
If you decide to change <p>, you just go to the CSS and edit p. It's as simple as editing your one class.
I find less classes makes the code look better. I go by the rule that hardly ever gets followed because the rule gets broken. Keep it simple.