[ckan-dev] Experimenting with a minimal CKAN

[Steven De Costa]

Yep sounds interesting :) If done in a 3.0 manner then it also sounds like
a good way to build out a full CKAN 3.0 over time.

I submitted this for the Knight News Challenge last night:
https://www.newschallenge.org/challenge/data/entries/defensible-data-journalism-making-the-indefensible-irrelevant

Such a platform could be built on top of a light version of CKAN.

Cheers,
Steven

*STEVEN DE COSTA *|
*EXECUTIVE DIRECTOR*www.linkdigital.com.au



On 1 October 2015 at 04:30, Ross Jones <ross at servercode.co.uk> wrote:

> Hi all,
>
> As an experiment (for fun, or out of boredom - you decide), I decided to
> see what a smaller footprint CKAN might look like, one that only provides
> the usual CKAN API, support for action functions from plugins and no UI.
> The only use-case I can think of for this (what do you mean the use-case
> should come first?) is for someone perhaps wanting CKAN for a SPA (Single
> Page Application) without needing most of the functionality that comes out
> of the box with CKAN. It’s at https://github.com/rossjones/ckan-mini if
> anybody wants to take a look. It looks a lot like CKAN because it is for
> the most part, there’s just less of it*.
>
> I recall Rufus built a SPA a while back using the precursor to
> https://github.com/okfn/ckan.js but I wondered if anyone might be
> interested in working on a CKAN SPA as a fun side-project? You could of
> course do that with a full CKAN install, but I thought it might be fun to
> see how lightweight/easily-installable we could get it.
>
> Cheers
>
> Ross.
>
>
> * No UI, No static assets, No controllers (except for API), less
> middleware, eventually less dependencies.
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20151001/08b99a64/attachment-0003.html>