[ckan-discuss] Documentation!

[Tim McNamara]

One thing to start with might be a flow chart that shows the steps of
implementing CKAN.

We also need to make it easier to compare CKAN with other offerings. I don't
know if that means a feature matrix and tick boxes.

Tim McNamara  |  @timClicks <http://twitter.com/timClicks>  |
timmcnamara.co.nz


On 17 May 2011 05:39, Seb Bacon <seb.bacon at okfn.org> wrote:

> Hi all,
>
> In an attempt to kickstart the improvement of CKAN documentation,
> Rufus has (perhaps misguidedly) appointed me "Documentation Czar" (I
> prefer Grand Poobah of Description).  I think the idea is that I'm
> hereby given some authority to cajole or annoy people into writing
> some documentation and putting it in the right place, so watch out all
> ;)
>
> Rufus has suggested it leans towards the more enterprisey / business
> decision / non technical end of the spectrum, and I think I agree.
> Our developer-focussed documentation could always be better, but I
> think it's pretty good.
>
> Before I get started, does anyone have any opinions or ideas?  Which
> audiences should we prioritise?  What kind -- pretty pictures, howtos,
> topic guides, white papers, manuals?  Are there specific topics that
> should be tackled first?
>
> Thanks,
>
> Seb
>
> _______________________________________________
> ckan-discuss mailing list
> ckan-discuss at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-discuss/attachments/20110517/9c668de3/attachment.htm>