Lines Matching full:documentation
108 =head2 Documentation section in QUICK CHECKLIST
114 Write documentation in POD
126 Give examples of use in your documentation
477 Your module should include documentation aimed at Perl developers.
478 You should use Perl's "plain old documentation" (POD) for your general
479 technical documentation, though you may wish to write additional
480 documentation (white papers, tutorials, etc) in some other format.
512 The level of detail in Perl module documentation generally goes from
526 The recommended order of sections in Perl module documentation is:
565 Keep your documentation near the code it documents ("inline"
566 documentation). Include POD for a given method right above that
567 method's subroutine. This makes it easier to keep the documentation up
623 for changes which do not affect functionality, such as documentation
654 Never release anything (even a one-word documentation patch) without
655 incrementing the number. Even a one-word documentation patch should
697 Build.PL and with C<require 5.6.1> or similar. See the documentation on
755 =head2 Inappropriate documentation
762 Tutorials, end-user documentation, research papers, FAQs etc are not
763 appropriate in a module's main documentation. If you really want to
766 main documentation.
782 POD documentation