Hi gang <br><br>Personally speaking <br><br>i agree there must be a [START HERE] document like and induction set.<br><br>Secondly I prefer a cook book approach to the second level USER documentation.<br><br>BOTH these would be backed by solid PROGRAMMER level documentation.
<br><br><br>Cook books and the [START HERE] model can both work on useful use cases.<br><br>For example :: I made a web page with html from a book, now I want to make a site based on my ideas -- How do I transfer my existing web to Nitro? Some of the suff oyx does :-)
<br><br>I trust you find that useful.<br><br><br><div><span class="gmail_quote">On 03/11/2007, <b class="gmail_sendername">s.ross</b> <<a href="mailto:cwdinfo@gmail.com">cwdinfo@gmail.com</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;">
<div style=""><span class="q"><div><div>On Nov 2, 2007, at 5:25 AM, Dan North wrote:</div><br><blockquote type="cite"><span style="border-collapse: separate; border-spacing: 0px; color: rgb(0, 0, 0); font-family: Verdana; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
- Documentation, documentation, documentation. It doesn't have to be clever or comprehensive. Just a solid walk-through of creating an application. The answers are mostly there amongst the original videos, the cheat sheets and the tutorials. It just needs shaking down and presenting in a clear and consistent way. I would choose some "typical" users and target them. Initially target an experienced ruby programmer writing their first web app in nitro. Then something like a "nitro for rails developers" track.
<span> </span><br></span></blockquote></div><br></span><div>The documentation is the common thread, and the cure is twofold:</div><div><br></div><div>- Yeah, write some cool new tutorial documentation. Something a person could do in a couple of hours that's more than stupid-simple.
</div><div>- Find all the outdated documentation and encourage everyone who owns it to update it to current tools/standards</div><div><br></div></div></blockquote></div><br>