[ckan-dev] Extensions listing

[Sean Hammond]

> Sean's proposed reorganisation of the docs [1] also lists some extensions:
> 
> datastore, multilingual, resourceproxy, stats, previews (pdfpreview,
> reclinepreview, jsonpreview), harvest, spatial
> 
> One item is in common (spatial). Should these lists be the same?

I'll deal with this. My idea (for the medium term) is that we will have
"officially supported" extensions, each of these will have its own page
in the _Extensions_ section in the core docs, and these pages will
appear in the main table of contents. Then at the bottom of this
section, there will be a link to Toby's wiki page for "unsupported
extensions".

Currently the wiki page is listing both supported and unsupported ones,
that's fine because the docs aren't sorted yet.

> Should they be disjoint? The wiki page says 'this is a list of
> external CKAN extensions' - what does 'external' mean?

There are "core extensions" that come builtin with CKAN (and are in the
CKAN core git repo) and there are "external extensions" that you have to
install separately and that have their own github repos. All core
extensions are officially supported. _Some_ external extensions are also
officially supported.

I think this distinction of core vs external is a technical one and not
interesting to users. In the docs, eventually I hope it'll speak only of
supported and unsupported ones, but sometimes when you click to go to an
extension's page it'll say you have to download and install it first,
sometimes not.