The main improvement that I want to develop is the use of PPI to automatically add POD inline with the Perl code. I'm only interested in Perl right now, since that's what I'm using. If there are other modules out there in Perl to parse Language X, then that could be worth adding. I'm not trying to replace Pod::HTML or create a non-POD format for Perl.

I have some free time coming up in a month or so, and I'm interested in making this into something that can add all the sections that documentation needs (name, synopsis, description, methods, see also, bugs, author).

In reply to Re^2: Using PPI to document existing modules by AK108
in thread Using PPI to document existing modules by AK108

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.