I'll add what I can towards a Windowblinds tutorial.

Sign me up for OBjectBar, DX application (not scripting) and general editor
Sounds like fun.

As stricky a user of the products here I would be willing to beta test tutorial's and provide feedback on compatiability issues.

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.

I don't know what I have to offer for something like this, but whatever I can, I'd be happy to.

Due to the limited amount of time I have,circumstances being what they are, online I can help in some fashion. Only problem...I don't know how I can help.

i'm ready to give out some good ideas for CursorXp!   

Ditto for me.

Willing to help in any way I can.

Great idea, if the wiki is diligently updated.   

I'm willing to try, from time to time, to help by contributing information or editing the work others have submitted. As all of us are learning here on the Internet, sometimes what is "heard" is not what was "said".

I must admit though that I am one of the "lost boys" when it comes to the Stardock products. I buy them (on and off) with the intent to be a creator but find, once again, that the lack of clear documentation and consistent, helpful support makes me abandon the effort. Mostly I have been a user.

I do have several sketches gathering dust of completely non-functional, but highly artistic (I hope) interface elements. Maybe if this effort succeeds I can put them together finally. (Note: These are "art for art's sake" skinning; not "functional for daily use" skinning.)

I would be glad to help any way I can!!

I think that two things are critical to the success of a Stardock application wiki to be THE source of documentation.

1. User verification
   Editors should be WC subscribers and should have to use their WC credentials to edit
   There should be a way to see history of user actions (approved, rejected articles
   
2. Certified editors
   All articles should be uncertified until a Certified editor approves them
   Certified editors should be promoted from the general pool after [x] number of certified articles submitted
   

These two things should prevent article vandalism and allow some accounting.

The wiki should have a setting to show beta (unapproved) articles or certified.
The Stardock devs need to be active in the authoring and approving of articles

Oh one mnore thing . . I should not have to worry about spelling.

Take a look at http://en.citizendium.org/wiki/Main_Page, they have the above features and it seems to be working ok.

This means for all skinnable apps right? Not just Stardock apps? If so I could help with a few non-stardock apps.

Is this also going to be a "History of Skinning" record? A catalog of all skinnable apps past and present? A record of "Trends in Skinning" through cooperation with other skin sites a display of the frequency of skin releases over time, as well as the frequency of "new skinners". etc...

Just trying to see where this thing might be going...

I think some things would be far too complicated, even for a wiki. It would turn into a monster very quickly. Imagine how big the DesktopX section would get when it comes to writing code....parsing HTML...etc etc

If you do create one it should be a very limited set of publishers to begin with.

^What he said, agreed.

Never mind, Island Dog has already written one.