Since I was made a content editor about two months ago, I've looked at the raw texts of a great many writeups, either because the writer had fled and left errors that needed correction, or through requests made at Broken Nodes, and the one thing I've noticed most often is that almost everyone who's ever written something here has awfully funny ideas about how HTML works.

Despite how good or competent many writeups seem, the formatting code often looks totally illiterate, almost random in its use. I realize that not everybody can pick up HTML as easily as others can, but there are so few tags that can be used here that not learning how to use them properly is really inexcusable, and (I daresay) offensively lazy.

Additionally, many seem to be stuck on using broken HTML 1.0 syntax. Given that HTML 1.0 is over 10 years old, I'd ask that anyone who is able to check out XHTML (the future!) and to use it as pedantically as you use words in your writeups.

Here's a summary of the tags you can use here, and how they work. Please memorize and use these, as they make reading things much easier, especially if you have to go back and edit something. A big, unbroken block of source code and text can't be all that easy to peruse to look for errors when necessary. Anyway, the list:

  • <p> -- the "paragraph" tag. Put one at the beginning of a paragraph, and then a </p> tag at the end to format a paragraph. Do not use <br><br>, which is not only deprecated with the introduction of XHTML, but is also sloppy code, even though if performs mostly the same function (more on that below). You can add parameters to the <p> tag to change the paragraph's alignment. <p align="right"> will align your paragraph flush right, for example. The other options are "left" and "justify" (which evens out all the lines in the paragraph, like those I used above this list). The "center" option quite obviously centers the text inside the paragraph, which can be useful for single-lines of text that need to be centered, as E2 does not allow the use of <center>. This is the HTML tag you'll probably use the most often. Do not forget to close this tag, as some browsers will render unclosed paragraph tags as though they were nested, resulting in a page of successively right-shifting paragraphs. Another excellent reason to use this tag properly (which means closing it) is that it'll throw off E2's paragraph counter (which you can enable in your Writeup Settings) if you leave unclosed paragraphs. I'm not sure if any of the modern browsers do that (nesting paragraph tags) anymore, but I do remember it happening way back when, during the web's dark ages-like infancy, which was ruled over by Netscape 1.x and IE 2.x and the like. Of course, nobody uses those browsers anymore, but in the 11 years I've maintained my own websites, the very, very occasional oddity will show up in my Apache access logs. Sometime last year I got a hit from someone using AOL 2.0 on Windows 3.1. Truly, it boggles the mind. Frankly, I'm amazed that a browser that old (AOL 2.0 was ~1995-96) could even render anything at all on the web today, and if it could, it would probably take several minutes to do so, even if it's just tables and paragraphs.

  • <br /> -- the XHTMLized version of the old <br> tag. It should not be used for formatting unless you're double-spacing list tags, or citing sources individually (one per line) at the end of a writeup. It does not require a close tag, and because of this, XHTML dictates that it must contain a space and a slash before the end-bracket. (Alternately, you can close your <br> tags if you'd prefer, but it's kind of pointless to do so when syntax doesn't directly require it.)

  • <ul>, <ol>, and <li> -- list tags. You can use <ul> to create an unordered, bulleted list, like this:

    • Unordered list item 1
    • Unordered list item 2
    • etc.

    Or, you can use <ol> to create an ordered list, like this:

    1. Ordered list item 1
    2. Ordered list item 2
    3. etc.

    The <ol> tag has a "type" parameter, which is used to change the type of order the list is ordered by. An example of such use would be <ol type="1">, which creates the list type, ordered by single digits, as above. Other options for this parameter are 01, or other options with a specified number of leading zeroes, 5 (or any other number) which will start the list at the number you specify, I, which orders by Roman numerals, and A, which orders by letters.

    Inside either of those tags goes the <li> tag, which indicates a list item. You should wrap a set of <li> tags around each list item, so that it looks like this:

    <li>List item 1</li>
    <li>List item 2</li>

    The end of your list should be followed by the close-list tag, which will be either </ul> or </ol>, because all three of these tags will nest if they're left unclosed.

  • <abbr>, <big>, <em> or <i>, <s>, <small>, <strong> or <b>, and <tt> -- each of these are tags which will format the text style of individual words or entire paragraphs. (Note: Both <em> and <strong> behave exactly the same as <i> and <b>, but only on E2. Everywhere else on the web, the first two are laden with parameters defined by cascading stylesheets. Consider <em> and <strong> as "reserved for future use" on E2. Both may render differently in text-to-speech programs, but we're probably far enough away from such things being in regular use that you can pick which bold or italic tag you'd prefer to use.)

    <abbr> will allow you to abbreviate words while simultaneously putting a broken underline beneath it. For example, <abbr lang="en-US" title="">E2</abbr> is on the <abbr lang="en-US" title="World Wide Web">WWW</abbr> will render the following (with apologies to in10se's abbr writeup):

    E2 is on the WWW.

    <big> allows you to make words bigger. This tag can be nested (used more than once on the same word or words), and is closed with </big>, repeated however many times the tag is nested at its opening. (Generally, four or five nests are the most you'll need, as anything bigger is kind of obnoxious.)

    <em> is used to emphasise text. This tag is a CSS-specific tag, and thus it should be used here with the growth of CSS and how many of E2's themes may support user-defined tags in the future. You could realistically use <i> as an alternative to this, and some have suggested that <i> should be used for italicising small text instead of <em>. Up to you, really. Moreover, <cite> also has this effect on text.

    <small> is used to make words smaller. Much like its <big> counterpart, it can be nested. It is closed with a </small> tag, repeated as often as its nesting dictates.

    <s> is used to strike through words. Close it with the </s> tag. Generally there isn't much use for this tag, and it replaces the old <strike> tag. The <del> tag also does this.

    <strong> should be used to make words bold. Close it with a </strong> tag. This is also CSS-defined and should be used for the same reasons as <em> should be used. The <b> tag can be used as an alternative.

    <tt> is used for monospacing a word or group of words. Its primary use is for the display of code, like I'm using here to denote each HTML tag I'm using. Use this when a <pre> tag (see below) wouldn't be appropriate and close it with </tt>. Unlike the <pre> tag, it provides no auto-linebreaks, as you can see. <kbd> and <code> serve the same function.

    <u> is used for underlining text that isn't going to be a link. Doesn't really serve much of a purpose unless you like writing your section headers manually (i.e., without the use of the <h#> tags). <ins> also serves this function.

  • Heading tags aren't used too often anymore, but they are still supported on E2. They aren't used much anymore because different browsers render them differently -- use too big a heading and it'll overwhelm somebody's browser window. Basically they just make text bold and/or bigger, and provide a line break after the bolded text. Here's an example:

    <h1>This is text rendered in H1</h1>

    <h2>This is text rendered in H2</h2>

    <h3>This is text rendered in H3</h3>

    ...and so on all the way down to <h6>. Close these tags as shown in this example. The same alignment parameters that <p> uses are also applicable with these tags. (Incidentally, E2 uses an <h1> tag, modified with CSS, to display node titles.)

  • <blockquote> and <pre> are used for mass-formatting, always of whole paragraphs or even whole writeups (though it is inadvisable to use <pre> for anything other than displaying code, as it tends to stretch the page widthwise if used with long lines).

    The <blockquote> tag is quite simple:

    <blockquote>It just indents your paragraph or writeup about 40px on both the left and right sides. Some authors prefer to use this tag around their entire writeups, though most prefer to use it only to display a quote from something or someone that is more than a few sentences long.</blockquote>

    <pre> monospaces ("preformats") text, but only in blocks, so its use is best reserved for code, or ASCII art. HTML tags that format text will not work inside a <pre> tag, so there's no need to add line breaks to the end of each line when using one. Here's an example:

    |                              |
    |   this text is using <pre>   |
    |                              |

  • Finally, <hr /> can be used to create a horizontal rule (line), though the only parameters E2 allows are the width parameter, which is specified in percentages, and the align parameter. A half-page wide, centered horizontal rule will look like this:

    Thus, the code for the line above this would be <hr align="center" width="200" />, which is 200px wide. You could just use an unmodified <hr /> tag and not specify a width, which would simplify things. An option addition to any <hr /> tag is the noshadow modifier, which will force the line to render without a dropshadow. E2 doesn't currently support it, at least not in writeups, but it does use it in the lines separating multiple writeups in single nodes.


That about wraps up the tags that are allowed here on E2. Please use them frequently and with relish, safe in the knowledge that you're doing yourself a favor by making your work more easily editable for yourself, and for content editors should the need arise. Single unclosed <p> tags in between each paragraph may have sufficed back in 1995, but things are different now. Please keep this in mind as we move toward more advanced forms of how we see text. Clean code is easier on everyone, whether they realize it or not.

If you're serious about what you write here, please be serious about how you write it. This has been a public service announcement by the E2 Content Editors.

I am scattered this month. More than usual. I've been sitting in the catbox jawing and not much else. Greeted many, given some advice, talked and talked and talked. Several of the new blood seem quite taken with E2, and eager to explore and participate. Several seem rather less inclined to understand how we tick before experimenting. It's all "good," although some of it is more exhausting than others. All in all, everyone's been polite at least with the private msgs. There's been some heat in the catbox, but it's not one sided. Get a few newbies with opinions and some noders with set ways and it can become heated quickly. A little cantankerous, but largely civil.


I'll be using this entry for the whole year, assuming I last that long as an editor!

Funeral parlor: Jan: Hacettepe University by mtg (newbie effort, msged advice); full of fish? by seudoname (newbie effort, msged advice); false belief by Sebow; Manos, the Hands of Fate by seshperankh (newbie effort, explained why); US Highway 48 by jizz (superseded); Mucho by Mighterbump; clementine by Nailbunny (superseded). Feb: writeup by Ashoni Lamaj Ziva (newbie effort); Roikushu's first 7 wus (newbie); 4 by BjaOckX (nonsense); 1967 Astoria, Queens NY P.S. Fires by metylman (newbie); runcible spoon by Ignis (insufficient content) and masukomi (superseded); Thai girls by Naturelle (newbie). Mar: blazing7th first 2 wus (newbie); Yma Sumac by mrsumac (newbie); Prophet of Doom by Uri E Bakay (list); Trilby by dollyroux (newbie). April: Learning Teacher philosophy by ForOnePurposeOnly (newbie c&p); Joel of Moore by Joel of Moore (newbie). June: Car crash commercials by infi (newbie); Jat by neoanderson (newbie, cr-c&p); Why does everyone sue everyone else in the USA? by mat_catastrophe (per request); Is the world going to end, well I'm taking bets by Tyrantuser1208 (newbie). July: NaviServer by groks (newbie c&p); smurflings by darwinfish (newbie); MML_City_Information_Page by dsharber (newbie c&p). September: plonk by eddieb (unlinked, v. little content) quilt block by The Soup Nazi (newbie, content undeveloped, unlinked). Cuius Regio Eius Religio by starryknight (misposted to the wrong title), EOD by lola_crayola (newbie, lack of content). October: Words that are supposedly untranslatable by heya (newbie), Noise Performances Music by bentmonkeycage (newbie, content undeveloped, unlinked), The truth about SNL by rabryan (obdurate newbie), rank by bigmouth_strikes (superceded), Smack My Bitch Up by Killer_86 (newbie, gtky, undeveloped, unlinked), Serial Experiments Lain by pjn (newbie, redirection to url), reforestize by seekingwisdom (newbie, all the usual), Using Yerba Mate to get over a cold by jvlokt (newbie, undeveloped), book reviews by lilshortee (newbie, unlinked, mistitled), fried abortion by TRyP, Jägermeister by hojimoji, Mojo Nixon by ryano (superceded) and by mat catastrophe (accidental double posting from reparenting), Comedy Gods by student2 (trolling), unable to write and Nothing comes to mind. by stoOpiDgenIUs (newbie, gtky, response), Golden Rose Of Montreux by fire_24 (contentless, newbie), Feeling Blue by Express (GTKY, newbie). November: chamernugs, An irony of cosmic significance, Double D, Bitchs by OuT2FaR (obdurate newbie/troll), getting over him when hes already over you. by Silver826 (newbie), Stars by AaronStJ (copyright), October 9, 2004 June 4, 2005 November 29, 2005 Smoked salmon and Petoskey, Michigan by iamkaym (per noder request), Miles Davis by Dr. Mojo (newbie). December: Budda by Hephaestos (title typo, newbie, etc.), Life returns when death has a sole, XTC', XTC, Serenity by Sativarg (newbie, unlinked, unproofed, incomprehensible content etc.) Megadeth by both WrathS (fled, no links, little info) and neleanor (newbie-linkless, low content, many typos), Iron Maiden by vladkornea (blank), delusions of childhood by neleanor (newbie, grammar/spelling, etc.), bacon by Eldarie (newbie, linkless, low content, typos, wrong location), Peist by New User (newbie, contentless, linkless), Remembering Bain. by DegenerateAlias (newbie, unformatted, unlinked, typo/error-ridden, re-posted w/o improvement), Asset Forfeiture Laws by schizosax (newbie, linkless, low content, typos), my self by m19 (newbie, linkless, contentless, typos, etc.) RedDot by chalamah (contentless, etc. newbie), Living Like Weasels by adder (accidental duplicate, removed extra), B*Tree by sniazi (newbie, contentless), Sardinia and Ramessu by farcalled (very low in relevant content, linkless), thought-fu by Mr_Soul (newbie, low content).

Red pen: Tolkien's languages by cethiesus (added editor's note with correction); supertaster by HippieChick (corrected consistent misspelling, and msg user. Last seen 2.3m); William Powell by Auguste Maquet (fled, corrected typos); Chinese style dumpling (added editor's note with missing ingredient, I'd like to nuke the recipe, but it's the only one with a dough recipe listed); Food should not be luminous by Pyrogenic (last seen 4.2mos, fixed minor typo).

Typesetting: Games Workshop by Helmut (modified some tags do they display better, did not change actual appearance of wu).

Directing Traffic: Chinese style dumpling to jiaozi.

Freeze Framing: If Satan is the prince of darkness, then who is the king?, When you call a girl beautiful, what does it mean?.

I’ve been carrying a mop and bucket around the place for a while now, and have had time to formulate a few editorial credos (thought I was going to say “philosophies”, eh!). Here’s some of my thoughts …

Second Opinions: I believe wholeheartedly in second opinions – both here and IRL. Of course, I’m willing and able to put my foot down, make decisions, and stand by ‘em - something that never endeared me to IT management. However, I’m not perfect (yeah, it was news to me, too) and sometimes I like to test my thoughts against those of my fellow admins. Frequently this turns into a learning experience for both of us, and almost always the database wins.

Supersession: When I’ve encountered a writeup that seems to have been superseded by other writeups in the node, my first thought used to be whether that writeup should go, and sometimes go it did. However, another point of view (from a wiser but not presumably older head) opined that often such writeups can act as a quick summary of the subsequent writeups. Now, I consider whether the writeup in question does indeed provide such a summary – and if so, I leave it alone, or get a second opinion. Mostly, though, I leave the WU alone.

Signing Klaproths: From reading old editor logs, I got enough opinions on this one to last me for the rest of my life. In fact, I got plenty of opinions on everything and Everything. Therefore, I’m adding mine to the pile. Current policy appears to be that klaproths should almost always be signed, and I agree. In fact, I held that belief long before I became an editor. It’s one of my principles that things said and opinions expressed can’t mean much if a person’s not willing to “own up” to having said them. I mean what I say, and I approved this message.

Possible copyright violations: I’m not making the call – that’s what the Content Salvage Team does. I’ll refer any questions to that desk.

Cools: If a writeup is outstanding, I C! it because I think it needs to be seen by as many readers as possible, or it should be brought back to attention. I admit to being a bit reserved with C!s, because I want them to mean something: for example, to highlight exceptional quality, or to encourage more of the same.

Fixxin Tyops and Problums: As I mentioned, I’ve fixed many typos on the fly – minor ones, mind you – without messaging the noder. Grammar or formatting problems always get a message to the noder. After reading the various opinions, and thinking about it, I’ve decided:

  1. If the user hasn’t been seen for a while, I’ll go ahead and fix it. One can only see so many “it’s” before the urge to fix takes over.
  2. If the user is current, I’ll send a message, because I believe pointing the problem out may cause the noder to consider why there’s a problem. If not, I’m glad to explain and help.

In other news:

Happy New Year, everyone. Write well.

Log in or register to write something here or to contact authors.