[Nitro] I, Nitro
Mark Van De Vyver
mvyver at gmail.com
Sat Nov 3 03:17:40 EDT 2007
On Nov 3, 2007 12:40 PM, * William <william.full.moon at gmail.com> wrote:
> Hi gang
> Personally speaking
> i agree there must be a [START HERE] document like and induction set.
agreed and at the risk of repeating myself ;) I think this
'introduction level information' is best done in the readme file,
which can be duplicated elsewhere, but the readme version should be
the reference point?
More extensive introductory material/howto can be refereed to.
> Secondly I prefer a cook book approach to the second level USER
> BOTH these would be backed by solid PROGRAMMER level documentation.
Agreed. In fact since I always have the pickaxe book and the Ruby
cookbook on my desk I'd say that, for me, the best documentation
(book) would be the Ruby cookbook with the pickaxe appendices.
Is this a longer term target/structure worth setting and aiming for?
It would kill the two birds with one document/book.
> Cook books and the [START HERE] model can both work on useful use cases.
> 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 :-)
> I trust you find that useful.
> On 03/11/2007, s.ross <cwdinfo at gmail.com> wrote:
> > On Nov 2, 2007, at 5:25 AM, Dan North wrote:
> > - 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.
> > The documentation is the common thread, and the cure is twofold:
> > - Yeah, write some cool new tutorial documentation. Something a person
> could do in a couple of hours that's more than stupid-simple.
> > - Find all the outdated documentation and encourage everyone who owns it
> to update it to current tools/standards
> Nitro-general mailing list
> Nitro-general at rubyforge.org
More information about the Nitro-general