Rob Dickens wrote: > Maybe good documentation starts with good documentation of the source > code itself. How many people really understand what even the > initialisation stuff does, I wonder; complicated and undocumented > enough for me to give up, anyway (which is saying something). Rob,
Do you mean the stuff in Boot or some other initialization code? Thanks, David > > 2008/8/30 Charles F. Munat <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> > > > Lift desperately needs better documentation prior to the release of > version 1.0. Despite the efforts of many to create documentation, > there > is still no clear path to Lift adoption for the majority of web > developers out there. At least, none that I can find. > > I am willing to write Lift documentation, but I don't understand Lift > well enough to do so. I am also unwilling to waste hours searching for > answers to questions -- that is simply not a worthwhile use of my > time. > > I am willing to devote an hour a day for the month of September to > getting a good start on a non-wiki documentation site. What I need is > permission to post questions to the mailing list. > > The reason I need permission is because when I have a question, I want > to be able to post it and get a rapid reply. I do not have several > hours > to spend on each question searching through the wiki, the mailing > list, > and the example code trying to figure out if it has been answered > before. That is not an efficient use of my time, and I have very > little > time. > > This may result in a lot of traffic to the list. I'll have a lot of > questions. So I suggest the creation of a separate "documentation" > mailing list. And if some of the best coders for Lift were on that > list > and agreed to try to respond quickly, then I can learn Lift quickly (a > benefit to me) and I can write the documentation quickly (a benefit to > the community and new users). Win-win. > > I am even willing to give my phone number to select members of the > community so that they can call me with answers to questions if that's > faster than writing an email. This is about getting documentation > done, > quickly and accurately. The "if you build it, documentation will come" > method does not work in real life. > > It would also be nice if folks on the list would read the > documentation > and send corrections, suggestions, comments, etc. to me (maybe via the > documentation mailing list). > > I've been out of the loop for a couple of months, so maybe some of > this > already exists. If so, please enlighten me. > > Does the Lift community think this would be valuable? I can tell > you now > that barring some sort of effort along these lines, it is not looking > like I will ever have the time to make Lift my primary development > method, and that would be a shame. And if I'm having that problem, I > suspect that many others are as well. Great documentation = rapid > adoption. Poor documentation = possibly, consignment to the great heap > of good ideas that failed. > > Feedback? > > Charles F. Munat > Seattle > > > -- > Rob, Lafros.com > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
