Re: Proposal to manage documentation similar to (or along with) core software.
Israel Saeta Pérez <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.documentation |
|---|---|
| Message-ID | <[email protected]> |
Dylan Jay-4 wrote: > > The #1 problem with plone is developer documentation rather than user > manual documentation. We have Mikko which has put a huge amount of > effort into a new developer manual which I think is now more useful > than the current developer manual. He did it in sphinx because it has > a documentation process more familiar to developers. Lots of others > have expressed their desire to document Plone this way. Yet there has > been continued resistance to making the collective developer manual > official. So we're stuck with a documentation process that isn't > attracting anyone new and telling a whole bunch of developers they > can't document unless they do that using that old way. > That's quite untrue. Mikko has been granted access to publish the manual pulled from the sphinx docs at plone.org whenever they're ready to do so (e.g. no spurious "_static", "index", etc. pages and all). -- israel ----- Israel Saeta Pérez -- View this message in context: http://plone.293351.n2.nabble.com/Proposal-to-manage-documentation-similar-to-or-along-with-core-software-tp4899546p5075101.html Sent from the Documentation Team mailing list archive at Nabble.com. ------------------------------------------------------------------------------ _______________________________________________ Plone-docs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/plone-docs