[ckan-discuss] publishing CKAN documentation?

Tim McNamara paperless at timmcnamara.co.nz
Wed Oct 6 23:11:09 BST 2010

On 6 October 2010 00:01, John Bywater
<john.bywater at appropriatesoftware.net>wrote:

> Hello,
> It's a perennial problem, the CKAN team is trying to work out how best to
> publish CKAN documentation. What's "broken" is that there is some amount of
> decoupling between particular versions of the CKAN software and particular
> version of the CKAN documentation that has arisen from wanting to put the
> documentation online.
> So far, we have one requirement:
> http://knowledgeforge.net/ckan/trac/ticket/676
> "The system shall support browsing to correct version of the CKAN
> documentation for a given service."
> Does that describe the problem we should try to solve, or is there anything
> else we need to consider?
> We'd like to automate this, so suggestions for how to do this very welcome!
> :-)

Hi John,

I think that CKAN should follow the path of the Python documentation. Have
the current release in the main namespace, with other versions given their
own subdirectories.

Is that the kind of feedback you were after?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-discuss/attachments/20101007/5dd99d8c/attachment.htm>

More information about the ckan-discuss mailing list