Citations:divitis


 * 2003, Jeffrey Zeldman, Designing with Web Standards, New Riders.
 * 184: But you will still want to edit some of their output by hand to avoid classitis and divitis.
 * 184: [subheading] The Heartbreak of Divitis
 * 184: We have named this condition divitis:
 * 185: Classitis and divitis are like the unnecessary notes an amateur musician plays—the noodling of a high school guitarist when he's supposed to be providing backup to a singer or featured soloist. Classitis and divitis are like the needless adjectives with which bad writing is strewn.
 * 185: Avoid divitis and you will find yourself writing clean, compact, primarily structural markup that works as well in a text browser as it does in your favorite desktop browser.
 * 185: Like Smokey says, only you can prevent divitis.
 * 185: Divitis kicks in only when you use div to replace perfectly good (and more appropriate) elements.
 * 186: Another classic example of divitis kicks in when a designer catches the “tables are bad, CSS is good” virus (see Chapter 4, “XML Conquers the World [And Other Web Standards Success Stories”]) [punctuation sic] and righteously replaces 200 tons of table markup with 200 tons of nested.
 * 186: So if presentational HTML is out, and classitis and divitis are out, how would we apply separate design rules to our navigational area in a hybrid layout combining tables with CSS?
 * 187: No classitis. No divitis.  No need for obsolete   tags.
 * 195: To the discussion of classitis and divitis earlier, add its predecessor, which is even worse than classitis and divitis because it includes all CSS styles inline, thus entirely missing the point that CSS can save bandwidth and preserve meaning by applying global styles to structured markup across an entire site.
 * 2005, Christopher Schmitt, Mark Trammell, Ethan Marcotte, Dunstan Orchard, and Todd Dominey, Professional CSS: Cascading Style Sheets for Web Design, Wiley.
 * 40: Avoid Divitis and Classitis when abandoning tables for more lightweight markup, . . .
 * 41: Even worse, it's far too easy to succumb to divitis, taking otherwise sensible markup and turning it into soup loaded with div elements: &lt;div id="outer-table"> &lt;div id="inner-table"> &lt;div class="innerlink"> &lt;span class="link"> . . .
 * 2007, John Allsopp, Microformats: Empowering Your Markup for Web 2.0, Friends of ED, p 37.
 * . . . the excessive use of classes and divs, even where not necessary (referred to as classitis and divitis, respectively).
 * 2007, Cameron Adams, Mark Boulton, Andy Clarke, Simon Collison, Web Standards Creativity: Innovations in Web Design with XHTML, CSS, and DOM Scripting, Friends of ED, p 293.
 * In many cases, this will be fine, but you can end up with a case of divitis, where many nested divs impair the clean nature of the markup.