documentation, links, project page

Currently I spent my rare time on coding, Writing documentation or updating the existing one is really time consuming.

well, this becomes a problem and a random knockout argument on this often.

I already asked some people to contribute documentation and tutorials but didn't receive much feedback.

I feel with you. Don't get me wrong please. I also have to do a lot of docs rework like this since I help out others here on thier modules. But the reason for what you sad is: Willing to write docs alone isn't enough since you need to know the features and how-to's before you can really write about it. But how can you know this all without hints? Even me who is working with PHP, JS, AS etc. is not sure how to use some of themekey features because UI always depends on the logic in the creators mind. And somebody who knows the module from inside out (the lead or co-maintainer) needs only a 10th of the time to show off some hidden features instead of somebody who tries around with it and tries to write doc's about it afterwards with try and error, and 50% fails. And he would only repeat the obvious parts anyway.

Maybe we should try to find an average work-around on this: Screenshots as docs should be excepted without text. (?!) Dunno. Example: I co- or in the moment rather main-maintain the link module, and only since then the module shows off all its features to me, I would never have realized as a user of the module. Then for me suddenly snapping a screenshot to somebody in the queue helped him to understand that his issue isn't a bug. Took me 20 seconds with a firefox plugin.

What we maintainers sometimes forget, the users of our modules also have no time but are willing to understand if there is ONLY a source. Some use more the 20 modules from the repo. How can they go thru' all the code to understand each of them fully? It would cost them less time to code them by theirself. And for us - putting a project open source here on Drupal.org is for many reasons, not only to make visitors happy. We want feetback. But the feedback is worthless if it is from the bottom to the top.

And finally it is also a misscalculation: We waste more time by answering issues in the queue based on missing knowledge about the module in the queue than by showing ONE example on each module option and setting the links on project page on the right place. Or we must motivate others by telling them more about the features clearly so thier feel able doing it for us.

Sorry for writing so much but I think I should find the right place to discuss that in general. Not sure how to solve this but I fully feel with you in questions of time. I've spent 4 nights to catch up with a 300 items issue queue on a project somebody asked me to help with when he became father while I have 3 hardcore audio-visual projects here on my table in need to get finished.

thanks for your fast reply!
greetings from Berlin

Just a short idea: do you think we can convince some of the slice makers of the themekey presentations giving us (you) some of their slices for the screenshot section of the project page?

Look at this example which took me 10 seconds to make a screenshot from cocomore presentation plus the red arrow and red text below (guess how many have asked me already if there is another equal sign in need):

EDIT: Hum ... wait ... now I see that it says on top that you were the speaker on this presentations ... so you did made that slices ?? Why not sharing some of them on Drupal.org?