A new module tutorial section under Tutorials is certainly a possibility -- though if that get's implemented, I'd still like to see cross-links stuck in the module review section (see also these tutorials or something) so if I'm browsing through module reviews I could also easily hit tutorials.

As for CPAN search results pointing to reviews and tutorials, I didn't mean to imply that only PerlMonks would or should be linked to, but that would be a good first step -- if the search engine authors/maintainers can agree on a mechanism (and there are only two main CPAN search engines I can think of: search.cpan.org, and theoryx5.uwinnipeg.ca/CPAN/cpan-search.html), then any other site (perhaps perl monger group sites) could also export a summary (or whatever) so that their reviews get into the databases to as well.

At any rate, current replies suggest keeping reviews strictly reviews and putting any module tutorial type things under tutorials. So perhaps this is the better idea. I will submit a request, as suggested by footpad, to create such a section and to move my Getopt::Declare posting there. Thanks for the feedback.

In reply to Re: On module reviews by danger
in thread On module reviews by danger

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.