On Tuesday, June 4, 2002, at 05:37 AM, Stefano Mazzocchi wrote: > >> I'm approaching this very granularly. For new stuff, consider writing >> at >> least a few FAQS (it will save you time on Cocoon users). Also, >> consider >> writing a few snippets. If you have time, write a How-To. With this >> basic information, others can come along and extend your work: write >> more FAQs, snippets, and how-tos, even more complicated How-Tos (which >> link to less complicated How-Tos). Later, those with the "big picture" >> can combine some of this material into a Tutorial or Guide. Providing >> small granular ways to contribute should help users participate. > > Sounds great. > > What about recipes?
Oops. I didn't *intend* to leave it out... it's just so new, not permanently fixed in my mental model yet. Don't worry. I love it. I also neglected to mention dynamic examples found in distribution. I'd also like to develop dynamic how-tos and tutorials, learning tools with hooks to webapp functionality (only in distro). My idea is that a dynamic howtos/tutorials would use resources like slash-edit to check the work of people walking through a learning process. Resulting files could be written to directories, governed by sub sitemaps e.g., where learners could incrementally build up the desired result of their howto/tutorial. It wouldn't work for all topics, but it might prove useful for others. Diana --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
