I agree, many people don't read the text which is already in place, or they may choose to ignore it. I don't think there's anything we can do about that, I can't think of an incentive which will have a positive effect, without spending money ;) For people who are going to read and take this advice, then improving what information is displayed is a good thing. As the node states:

"RFC. First Draft of proposed, shortform, guide to posting SOPW"

As a short guide to posting I think the suggested text is an improvement on which currently exists (no offence intended), it's certainly shorter than asking people to read How do I post a question effectively?, How do I compose an effective node title? (and the rest) in that it the advice (if followed, see above) will help us to help them. Links to the other advice nodes (and PerlMonks for the Absolute Beginner) could be displayed elsewhere, perhaps after posting or in the preview page.

I think it's worth mentioning that (at time of writing) were looking at 15 lines of text, if people read and take onboard when posting the 7 (at present) lines on the check list, that in itself is a positive step.

In reply to Re^5: RFC - shortform posting guidance for newcomers by marto
in thread RFC - shortform posting guidance for newcomers by ww

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.