I agree jhourcle, but just to make things more concrete:
And actually, there's a third kind of documentation that you might provide: A design doc. This can go in a separate design.pod file.
I think of it this way:
In reply to Re^2: Our documentation sucks
by j3
in thread Our documentation sucks
by jimt
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |