First off, intuitive is all in the eye of the beholder. Which is what I was saying about my perl project at work.

Second, when I first wanted to do the vote patch, it did take me a few days to figure my way around things. If there was a document like this to explain even just the PmDev Nodelet, it would have been nice to have:

#xxxxxx
Node number being used to display the current document.
= <node type>
Type of document the above node is see this to see an explanation of all the node types.
via <blah>
I'm not sure what this is... here is a document that explains the different types
Dump Fields
Dumps the fields - you can only dump all the data about the current node if you have certain authorities which are ...
...
...
Everything Bible
Mandatory reading - too bad it's too new for the level of Everything we're using here.
...
...
And, of course, there'd be an extra entry - "PmDev Help" - that would point to this doc. But, really, what I was referring to that I thought was not intuitive is just following around all the code. On one hand, it's great - it's hugely modular. On the other hand, a web browser is not the most conducive method for reading/writing code that is spread out all over the place ;-)

In reply to Re^5: Open sourcing perlmonks by Tanktalus
in thread Open sourcing perlmonks by BUU

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.