If samples of each section remain on the first page, I think that in most cases, breaking automagically at the first <p> or the first <code> would work (for the long-winded, a maximum character limit might be needed). If someone can't describe what's going on in the first paragraph (with supporting evidence and examples to follow), what hope is there that the rest of the message will get to the point?

This applies more to questions and discussions than replies, of course, because a reply must first address what was said before getting--in the case of this post, in paragraph three--to the substance.

Examples of each section are wasted on the front page because it:

  1. creates the expectation in new users that that is the appropriate place to look for their posted question, and
  2. is not used to the extent that Newest Nodes is by regular users (see the source of unsubstantiated evidence). Does any frequent user actually look at the front page for anything other than quest announcements?

Given that the people most likely to view the front page are new users, it seems an ideal place to shove site how-to information. An example, freely stolen from Where should I post X?:

Seekers of Perl Wisdom
When you need an answer to an actual real life problem fast you're probably going to want to post your question here.

Categorized Questions and Answers
These are more general questions. If you post a question to Seekers of Perl Wisdom but think other people might benefit from the knowledge you might want to rephrase it in more general terms for this section. This is also a good place to look for answers before you post to Seekers of Perl Wisdom

And so on.

In reply to (kudra: break automatically, or (better) no posts on front page) RE: Frontpage/UI Improvements? by kudra
in thread Frontpage/UI Improvements? by vroom

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.