<br><br><div><span class="gmail_quote">On 8/30/06, <b class="gmail_sendername">Steven Peck</b> <<a href="mailto:speck@blkmtn.org">speck@blkmtn.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The barrier to writing tutorials is less then screen casts. However, if<br>there are tutorials, they can be converted into screen casts by others.<br>Even if there are video's, a written tutorial that accompanied it would
<br>be valuable.<br><br>Either way... Whichever people choose to contrib is fine. As long as<br>something beyond conversation is produced.<br></blockquote></div><br>Yep. I've posited in the past that allowing an easy-to-create content type (
e.g. stories) with free tagging (and voting, and and all those extra modules we want on <a href="http://drupal.org">drupal.org</a> :P) would make it more likely that content would, um, show up.<br><br>In the end, it doesn't matter. Create tutorials, then submit them, and we'll find a home for them (and link nicely back to your domain as attribution).
<br><br>When I've had time in the past, I can plow through a half dozen pages on using contrib modules in an evening. If everyone on this doc list created one tutorial....<br><br>And tutorials are great fodder for newsletters and promotion on the front page, too (weekly review of new tutorials).
<br><br>Just like we have the heavily used snippets...think of tutorial snippets -- "How to configure the aggregator to pull in relevant content to your community". For that matter...make a forum post asking folks what they want tutorials on....look at the comments, and write up the tutorial.
<br><br clear="all">-- Boris