[ckan-discuss] publishing CKAN documentation?
john.bywater at appropriatesoftware.net
Thu Oct 7 09:10:46 BST 2010
Tim McNamara wrote:
>> We'd like to automate this, so suggestions for how to do this very welcome!
> 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?
That's a great suggestion. Thanks a lot!
Any idea how they automate the publication? Probably with some software,
More information about the ckan-discuss