Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
We see malformed posts here on a daily basis, very often from newcomers who haven't yet learned about <code> tags. The editors spend a fair amount of time cleaning up malformed posts, but still the posts come.

I wonder if there isn't a simple way to avoid many malformed posts. All we would need to do would be to apply some proactive education in the right place.

What if, below each <TEXTAREA> for entering and updating nodes, there appeared a brief summary of tag and entity conventions. It could appear based on a user setting that could be turned off once someone knew there way around (and was past the point of not knowing about posting conventions).

The summary might read:

Please read _______ before making your first post.

Use <p> to separate paragraphs, or <br> to force a line break.
Use <code> .. </code> tags around code fragments. These work like <pre> tags, which you should not use.

Use <b>bold</b> for bold text, and <i>italic</i> for italic.

To link to a node, use [id://node_id] or [id://node_id|optional words]
To link externally, use [http://www.example.com/|optional words]
Links are disabled within <code> tags.

Outside of <code> tags, use &#091; and &#093; for [ and ].

See _________ for additonal details. To disable this summary, uncheck _____ in your user settings.

Does this seem reasonable? If so, what kinds of things would you like to see in a such a summary?


In reply to Markup summary when posting/replying? by dws

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



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others scrutinizing the Monastery: (8)
As of 2024-04-23 12:48 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found