"It's 1981. Roy Richardson is a manager at a Los Angeles computer company. A devout Mormon, he has a two-year-old son, with two daughters yet to be born. He has a little over ten years to live.

I was that two-year-old and Roy was my father. I grew up without him, knowing the outlines of his life but not the details. In 2006, at my mother's house, I found three boxes of details." Leonard never fails to surprise and amaze. This is wonderful.

"JavaScript Garden is a growing collection of documentation about the most quirky parts of the JavaScript programming language. It gives advice to avoid common mistakes, subtle bugs, as well as performance issues and bad practices that non-expert JavaScript programmers may encounter on their endeavours into the depths of the language." This looks really, really good. Alas, unlike Phil, I'm still not quite fully up-to-speed on Prototypes, but it's a great piece of documentation nontheless.

"Consider the process of writing the Readme for your project as the true act of creation. This is where all your brilliant ideas should be expressed. This document should stand on its own as a testament to your creativity and expressiveness. The Readme should be the single most important document in your codebase; writing it first is the proper thing to do." I like this: after all, a README is basically the story you tell about your software. Why not write it before the software exists?

Great round-up of all the stuff out there about Rails 3. If you're as behind as I am on preparing for this, there's some really good stuff here; nice to have it all in one place.

"convert man pages into PDF documents and save them to a specified directory; (batch) print or view PDF man pages from the command line". Which is, you know, clever.

"Merb’s routing shiznits needs some serious documentation love. Whilst I have a shot at getting some proper docpatches together here’s an overview of how to use routing in Merb 0.5." Thank god for that - was finding Merb's docs a little patchy in places.

"APIdock is a web app that provides a rich and usable interface for searching, perusing and improving the documentation of projects that are included in the app." Handy.

"I think the role of the architecture diagram, user flow, and wireframe belongs very much after the fact, after we’ve sketched and prototyped an experience. Those are tools to document what has been agreed through sketching and prototyping. They are not the best means for solving challenging design problems." That seems like a good way of putting it.

"ScreenSteps brings simplicity to the labor intensive process of software documentation." Focusing on the screengrab, rather than video, as instruction tool. Could be a nice approach, especially if export is any good.

CHM files - compiled HTML - are basically Windows Help files. You need something like this to view them on a Mac.

Prototype finally has its own website. About bloody time - but it's great to see it being supported so thoroughly.