Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
I don't know about bone-headed, but it's definitely pointing in the right direction. In fact, I think it looks great so far. I don't find a designated CGI section especially necessary, however it would be great if the CGI help guide were added to the Troubleshooting section rather than bumbling along in the other stuff close to the bottom - I was about to suggest adding it when I spotted it, which was pure chance as I'd been there recently, causing the link to show up with visited link colour and thus standing out.

Makeshifts last the longest.


In reply to Re: Updating the Tutorials Node by Aristotle
in thread Updating the Tutorials Node by footpad

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.