From: Martin A. <opt...@gm...> - 2010-01-24 02:34:32
|
Dylan Jay wrote: > Hi, > > The manual is now uploaded to the knowledgebase area[1]. I'm assuming > that the redesign will get rid of the authors attributions as that no > longer makes sense right? If not I'll get Mikko to reupload it as it's > mainly his work. > All the code for uploading will be in the buildout in > collective.developermanual shortly. Next step will be to setup regular > reuploads every night. Of course if anyone wants to contribute to the > manual just read [2] > > It's been transformed using transmogrifier blueprints from > pretaweb.funnelweb. There may be somethings not transformed right so > let me know and I'll fix them if I can. In particular PHC reference > manuals don't allow index pages so content from sphinx index pages is > currently missing. Also many of the styles aren't supported by this > plone theme so will need to be supported or transformed to something > that is. > > [1] http://plone.org/documentation/kb/collective.developermanual > [2] http://plone.org/documentation/kb/collective.developermanual/introduction/updating-this-document.html > > p.s. Thanks Raphael, the api snippets did help me and in the end most > of the calls were even xmlrpc. > Thanks Mikko for the awesome start to manual and the others that have > contributed. I think it's really great that this has made its way to plone.org where it belongs! ;-) I couple of suggestions: - As Alex said, it's probably better as a manual than a kb article. This really ought to be the basis for "the" manual for Plone development in general. - We shouldn't call it 'collective.developermanual'. That's the name of a Python package where we put some reST source code. It has no meaning to the intended audience and it's a terrible title. I'd just call it the "Plone Python Development Manual" or some such. Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book |