This looks like a great resource, thank you for sharing.

One trick I learned many moons ago from a tech writer was what he called the "SEE" method - statement, example, explanation. I've never found any references to it. I've found it effective for simple cases such as helping engineer's "just get started" to break writer's block. It's not a grand theory covering all doc types.