Prerequisite: one of Lua tasks 10, 11, or 12.
Documentation is a much under-appreciated skill for a programmer. Creating good documentation has multiple benefits both for the end-user and for you and other programmers. When you return to your code months later to make updates, can you quickly find the right section of your code? Make your code readable and easy to understand by using relevant variable and function names and by adding brief annotations. Understanding where annotations are helpful, and where they are mere clutter is a difficult skill to master. When you have assembled a suite of test cases to ensure your code is working as intended, make the cases available to others by linking to them from the main program repository. Finally, write comprehensive instructions for the end-user, who may not have a technical background, give extensive examples and point out any limitations or pitfalls with your code.
Examine https://en.wikipedia.org/wiki/Module:Sandbox/RexxS - it automatically displays the documentation at https://en.wikipedia.org/wiki/Module:Sandbox/RexxS/doc
Note the use of sections, heading levels, and bulleted lists. Each of the functions is described and examples given.
1 Working on task 10, 11 or 12, create a doc subpage for your module. On that page, describe as simply and clearly as possible what your module does. Link to your test-cases, and give clear examples of normal use as well as unusual examples, and describe any potential problems with your code.