As long as I've been on the Internet, whether as a Usenet reader, email recipient, or PerlMonk, I've seen what many here see regularly: Poorly composed node titles (or email subject lines, or Usenet subject lines). Such titles inhibit readers from finding the posts that interest them, and from filtering out those posts that are not of interest. If you want your post to be read by people who care what's written (don't we all?) choose an effective node title.

A node title should concisely convey the subject of the node. If the node is a question asking how to sort in reverse-numeric order, the title ought to make that clear. If the node is a meditation on the merits and pitfalls of using map in void context, the title should make that clear as well. And if the node is about betting on basketball games, its title should go a step further by prefixing the title with "OT: "... the abbreviation that many here in the monastery expect to see for Off-Topic posts.

Node titles should be crafted with care and thoughtfulness. A reader should be able to read the node title and already formulate an accurate opinion as to the node's content.

The following is an example list of bad node titles, along with a description as to what is bad about them. They're not intended to pick on anyone. But read them with a smirk, because I'm sure you've all seen them before and thought, "Argh!":

Why is it important to compose accurate, concise, and descriptive titles? Several reasons, some of which I'll enumerate below:

Now for a small proposal to all moderators (Friar - Level 6 and above):

When considering a node for title editing, be sure to do two important things: First, give a recommendation on what the new title should be. Second, send a courteous and brief /msg to the person whos node you're considering to explain why the node is being considered for editing. Obviously we can't /msg Anonymous Monk, but everyone else is fair game.

I personally appreciate it when people /msg me with heads-ups on my nodes. Many times, the node's authors will make the necessary changes themselves. Other times, at least they'll have the opportunity to learn where there is room for improvement next time. Be courteous; kindness is a virtue that PerlMonks espouse. And a gentle reminder is more likely to be heeded than a hostile rant.

Speaking of rants, this is the end of mine.

But for additional reading, please do see How do I post a question effectively? from About the PerlMonks FAQ. Therein you'll find all sorts of great tips on how to get along in the Monastery.

Thanks for reading. Hopefully you'll take it as a good natured commentary on how to improve the look and feel of the Monastery.

Cheers!

Update: Implemented a few suggestions from castaway. Thanks!


Dave


In reply to Composing effective node titles by davido

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.