Hi Robin, On 3/27/06, Robin Haswell <[EMAIL PROTECTED]> wrote: > I think work has to be done on documenting all the new lubblies in 0.9, > as well as all the great work in previous build. I think the Trac wiki > is great for this - we can add our own examples, add links to recipes, > cross-link related functions (major PHP manual selling point), etc. The > problem is, I have no idea where to even start, and I realise that > although I have experience in TG, I couldn't remember a list of > functions if I tried (I only know what comes in to my head as I'm > writing code - funny). > > Anyway, I was thinking, could some of the devs who know the codebase > pretty well put up a skeleton documentation tree on the Wiki, then we > can start filling it in? That leaves all the hard work for us (good), > but provides leadership and direction (essential) - what do you think?
This is certainly a good time to bring up docs. The docs are the #1 defect in 0.9 at this time. It's definitely time to get stuff moved off of the wiki and into the XHTML files (in the newdocs directory of an svn checkout). There are also other docs to be written, and I can certainly help with the direction there. I'd be happy to put together some skeleton/outline docs with pointers on how to fill them in. Documentation patches will be gratefully accepted. I'm really happy to see the progress being made in Docudo. I suspect that Docudo.org will come online before we know it. Once that's matured a bit, we can set it loose on tg.org. In the meantime, though, we need to edit the XHTML docs we have as is. Kevin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
