It sounds like a good idea for tutorials, but the one issue that is utmost in my mind is the constant state of change in the Stardock 'point' programs (e.g., WindowBlinds, IconPackager, etc.). This constant state of change makes it harder for anyone outside of the Stardock crew to know exactly what will and will not be accurate information.
One example:
I installed WindowBlinds 5.5 - both the stand-alone and via Stardock Central - released this year after the aforementioned article and found that the included "documentation" is a previous version modified by placing an image over some text and that some of the images are inaccurate for the current version (e.g., user overrides). Unfortunately, this did not strike me as a professional document.
I don't want to be an ass, but it seems like the current documentation is not being addressed properly (perhaps being dismissed in favor of the upcoming releases such as WB 6?).
As I have mentioned before, I design and produce documentation for a local manufacturer in the Seattle, Washington area and therefore know that it can be a significant undertaking. Unfortunately, if you do not start to design and produce it accurately, the first to suffer are the customers who want to use it without having to contact support or go to a web site to find the latest information.
Corky steps off his soapbox......
On a positive note, I do know that the issues can be overcome if effort is put forward now instead of later, and that the overall impression of the products can be improved greatly by simply adding accurate and thorough documentation illustrating how to use all of the functions of said products.
A 'Wiki' would be great step for the community in any case, assuming the product changes are not so large that the volunteers become overburdened with catching up.
To answer the primary question of this post, I would be willing to update (or re-create) my mini tutorials once the main product I focused on (ObjectDock Plus) is finalized (waiting for the 'ObjectDock library' issues to be resolved in the next maintenance release). I do not know if these are considered a part of the 'Wiki' (perhaps not), but I can at least help with that much of the issue. 