Re: Proposal to manage documentation similar to (or along with) core software.
Dylan Jay <dylan-Q+/Sk2sTzaxWk0Htik3J/[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.documentation |
|---|---|
| Message-ID | <[email protected]> |
On 17/05/2010, at 11:44 PM, David Hostetler wrote: >> unequivocally obvious what documentation you are reading (because >> of the URL of the documentation, e.g. /documentation/4.0. How >> much more clear can it get? ;-)) > > ... or, rather, what documentation you *would* be reading, if it were > there. It does no good to have a bunch of tidy version-specific URLs > if there isn't comprehensive documentation to go under them. > > Just being a little devil's advocate here, but isn't this notion of > formally versioning the docs putting the cart a bit before the horse? > > Or are you of the opinion that versioning is worthwhile even if the > docs continue to be piecemeal and prone to decay? probably you're referring to the developer documentation. The Plone user manual I think is pretty comprehensive. What we're really talking about versioning here is something like http://collective-docs.plone.org/ which still has holes but is far less piecemeal than the documentation knowledge base (http://plone.org/documentation/kb). ------------------------------------------------------------------------------