Simplest solution would be to support all of the bootswatch themes, which would just be a matter of swapping out the <link> tag in the <head> based on the site's theme setting.
Beyond that, it may be possible to think of themes as forks of JKAN that contain only the changes necessary to implement the theme. For example, a fork could contain a change of the <link> tag, adding a .css file, and a few markup changes. You could install it by creating a pull request of that repo against your JKAN repo and merging it. Where it gets tricky is if you've made any other modifications, or if future versions of JKAN make markup modifications that create merge conflicts.
Simplest solution would be to support all of the bootswatch themes, which would just be a matter of swapping out the
<link>tag in the<head>based on the site's theme setting.Beyond that, it may be possible to think of themes as forks of JKAN that contain only the changes necessary to implement the theme. For example, a fork could contain a change of the
<link>tag, adding a.cssfile, and a few markup changes. You could install it by creating a pull request of that repo against your JKAN repo and merging it. Where it gets tricky is if you've made any other modifications, or if future versions of JKAN make markup modifications that create merge conflicts.Any other ideas?