[ckan-dev] Packaging theme and model customisations

[Rufus Pollock]

On 10 February 2011 15:53, David Read <david.read at okfn.org> wrote:
> Seb,
>
> Rufus just called to say that what I said was wrong and he's done

Not so much wrong as that one can also do it in the extension :)
(sorry for all -- was afkb with only phone and it sounded like Seb was
coding!)

> things a better way in a couple of extensions - ckanext-stats and
> ckanext-dataapi. Something about hooks for config. There seems to be
> something related here:
> https://bitbucket.org/okfn/ckanext-stats/src/default/ckanext/stats/__init__.py

FWIW I think there are 2 approaches here:

1. Simple themes -- just use the config variable in the ini
2. Extension that need templates (and css/js) etc. Using the approach
shown in the stats extension. Also propose following convention there
that extensions store templates and 'public' (static stuff) in
extension at:

public/ckanext/{extension-name}
templates/ckanext/{extension-name}

(And mount the 'public' material at ckanext/{extension-name})

Rufus

PS: I (we) should document this on http://ckan.org/wiki/Extensions or
similar ...