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 ;-)