Beefy Boxes and Bandwidth Generously Provided by pair Networks
Just another Perl shrine
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
First off, this looks great, miles above what exists now! (I am not trying to dis whoever created the existing page at all, and I hope this is not read that way)

As for feed back, the only thing I really see is that the TOC block up top should be in a larger/different font as to distinguish those links from the rest of the page.

I also like the cross link idea above as some of the tutorials may span catagories. And in that case, I would also advocate a Win32 catagory as the site has had a lot of activity focused around Win32 lately and there are a couple Tutorials based on Win32.

Great job!

"Nothing is sure but death and taxes" I say combine the two and its death to all taxes!

In reply to Re: Updating the Tutorials Node by Rex(Wrecks)
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.