Tom McFarlin follows up on his previous post about documentation practices in WordPress projects by laying out some sample guidelines for how you can document your own work. Commented source code and a README manual are a bare minimum, but Tom comes to many of the same conclusions previously presented by Siobhan McKeown at WordCamp New York 2012: Not everyone learns the same way, so for larger projects screenshots, videos, and possibly even a stand-alone documentation site can be very useful.













