<ramble> I think some of the problems with massimo's first stab at a wiki are overblown... the navigation bar is too prominent, etc... this is css .. css can develop and mature. As long as wrong choices are not made that block the development of the web2py wiki into everything that we want it to do, the door is left open for further features. It is so light-weight and simple right now. I like it as a starting point. As long as it is flexible enough to change, move or whatever. With a commercial solution will we get the kind of super-user, anything is possible access like we will with the custom app?
I still vote custom app unless anyone sees a compelling reason that it might block the future development of the docs or the mobility of the information (to different wiki-platforms and technologies in the future, etc). I think, to the contrary, if the information is safely databased we can port it too other solutions/technologies that might develop in the future. </ramble> Still, no one is using it and it is still a bit immature. But, *as long as we can be sure that the data can be moved elsewhere* why not devote some time to starting up some docs there? On Mar 5, 11:23 am, Yarko Tymciurak <[email protected]> wrote: > one advantage to a web2py wiki: we can dump (csv) contents in prep for > sphinx integration / work. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
