Re: Developer manual stub now available
Martin Aspeli <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.documentation |
|---|---|
| Message-ID | <[email protected]> |
Israel Saeta Pérez wrote: > I agree with others on this would better be generated from code, ideally > from interfaces. This way we wouldn't have to revisit the API reference > everytime a developer adds/removes a method but it would be her/him who > updates the interfaces code and regenerates the API reference. Can we please not re-open this discussion? It took enough time as it was last time. It's not going to work. Don't get me wrong - having generated documentation from interfaces and a single browsable repository ala api.plone.org is a great idea. But it's not sufficient. You can't see the woods from the trees, and you don't know where to look for the things you need. We need something like this manual that is organised around the things people want to achieve, rather than the historical names and locations of various bits of Plone's internal code. Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book ------------------------------------------------------------------------------