First, there is the problem with getting permission from all revelent posts that you'd want to include.

But, given the way that PM nodes are created, I don't see the easy connection between taking a threaded discussion and converting into an article. I do agree that we should have some archive beyond Best Nodes that is on a daily/weekly/basis (see 'Best Nodes' on a {dailyweekly...} basis? for my comments on that), but that's up to vroom to create.

But I do think that some of the more advanced monks should consider writing more 'articles' for PM, whether it be module reviews, tutorials, or similar. For example, I'm going to try to put one together this weekend for something I've observed in my perl programming, and it would be nice to see more particular those higher level monks that know what they are doing. The only thing here is that it would also be nice to have a beta-node where one could post such an article and point selected people to it, before it is moved into public viewing, but I guess that editing the article after release isn't that bad either.

Dr. Michael K. Neylon - mneylon-pm@masemware.com || "You've left the lens cap of your mind on again, Pinky" - The Brain

In reply to Re: The Perl Journal's woes by Masem
in thread The Perl Journal's woes by cLive ;-)

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.