Teaching, rebuking, correcting & training in righteous web design.

Enough with the Bread and BReakfast markup already!

May 29th, 2007 Posted in Disruptive Innovation, Theology

B and BReakfast markup’ is a handy mnemonic mechanism to memorize not to semantically collude your online sermons and studies with misused < b > and < br > taggery.

At some point, those of us fielding sermons, Bible studies and other topical texts online are going to have to stop with the crufty, deprecated and semantic hostile use of sectional markup.

Here’s what I mean - based on what Tantek Çelik meant way back on 2002 when this topic of B&BR markup was first broached:

Bed
Stop using that old < b >old tag to identify titles, headings and sections of your online documents. Instead, use the tags as God and nature intended.
BReakfast
Sermons are long-winded enough, no need to add to the tedium with an single html paragraph demarked with double line break tags < br > < br >. Instead … and hang in there with me folks … use the < p > aragraph tag to encapsulate paragraphs.

Why you ask? Quite simply so your underlying (x)HTML markup better represents
the intended meaning and structure of your online document. For example,
semantically, which markup better represents the intended meaning of the author:

<b><font size="4">John 11:35</font></b>
<br /><br />
<b>Jesus wept.</b><br /><br />
Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Ut id felis. Fusce ut neque. Sed arcu arcu, iaculis sit amet, auctor posuere, blandit non, tellus. Suspendisse id urna. Curabitur sagittis.</p>

versus

<h2>John 11:35</h2>
<h3>Jesus wept.</h3>
<p>Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Ut id felis. Fusce ut neque. Sed arcu arcu, iaculis sit amet, auctor posuere, blandit non, tellus. Suspendisse id urna. Curabitur sagittis.</p></p>
 

I’d argue that the second example of markup better reflects what the meaning of the message. Then again, some of you ‘view source’ types might argue:

<dl>
<dt>John 11:35</dt>
<dd><h4>Jesus wept.</h4>
<p>Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Ut id felis. Fusce ut neque. Sed arcu arcu, iaculis sit amet, auctor posuere, blandit non, tellus. Suspendisse id urna. Curabitur sagittis.</p>
</dd>

</dl>

Point is - are you still using (x)HTML markup that leads various aggregators, readers and other mechanisms that would otherwise better and/or more correctly convey your messages?

Well then stop doing that!

There’s enough existing (x)HTML taggery out there to make your markup match the meaning of your message. Trust me, you’ll thank me for this when you eventually publish a book and/or study guide based on your blogged sermons.

Meanwhile, for those of you missing the point of this post and going directly to ‘view source’ … I left you some nifty markup gifties to talk about intentionally !-)

%DIGG%
Share This

Stumble it!

  1. 10 Responses to “Enough with the Bread and BReakfast markup already!”

  2. By mrben on May 29, 2007

    You’ve got an extra in the 2nd passage.

  3. By mrben on May 29, 2007

    Oops - that should be an extra < / p >

    Hope it works this time.

    I totally agree, BTW ;)

  4. By MeanDean on May 29, 2007

    Yeah, I left a coupla nifty gifties out there for the view source cynics!-)

  5. By mrben on May 30, 2007

    Erm - not in the view source view - in the actual page view….

  6. By JackWolfgang on Jun 2, 2007

    Shouldn’t that definition list have a dt node in it as well?

  1. 5 Trackback(s)

  2. Jun 19, 2007: Blogos - God’s Word | our words | meaning, communication, & technology | following Jesus, the Word made flesh » Bibleref: Going Public
  3. Dec 26, 2007: 12 Days of Jesus Junk - Day 12 - Santa with Baby Jesus Nativity(ies) » Heal Your Church WebSite
  4. Mar 11, 2008: Inaccessible, that’s what you are » Heal Your Church WebSite
  5. Jun 23, 2008: If the Olympics are going mobile, then why not your Church Website? » Heal Your Church WebSite
  6. Jul 10, 2008: Follow-up: bad church web design inspired by bad theology » Heal Your Church WebSite

You must be logged in to post a comment.