Extensions registry section

[rufuspollock]

We want to create an extensions registry - see ckan/ideas#22

User stories

As a CKAN User I want to know what extensions exist and their status so that I can find ones I can use and know they are production ready (or not)

As a CKAN Developer I want to publish my extension so that others know it exists and can use it

Implementation

• Automatically collect information
  • Migrate the code and work at https://github.com/ckan/extensions.ckan.org
• Create a page to display and allow searching
• Have a process for submitting new information (and correcting old)

[rufuspollock]

@loleg has started work on this at https://github.com/loleg/ckan.github.io/tree/extensions

I've reviewed this and is working at the moment. Various suggestions (@loleg - let me know what you think):

• What about writing the extensions into the page on load and then hiding them (as per okfnlabs.org) - this would mean stuff was findable by search engines
• should display the whole list by default (on page load) rather than having to do an empty search
• Wondering whether we want to run off the google spreadsheet for the present since we'll be doing a lot of tweaking I think (e.g. to remove items, add items etc) - note I'm aware this contradicts the first point

[loleg]

• Good point. It's quick and easy on the bandwidth to embed the JSON
  into the page, rather than being all fancy and semantic, but I don't want
  to start any flame wars :)
• Full list slows down my iPads web browser to a crawl. The Labs
  projects page solves this with "features". Can we shortlist a dozen odd
  plugins?
• JSON is just as editable via GitHub. But, as you prefer.

[rufuspollock]

@loleg

• I guess we will have to worry about pagination when the list gets really big - i'm not sure about pagination in jekyll. For now we could just have all in one page ...
• I'd agree that we have some as featured and only display those initially
• We could migrate to json later but i am thinking the spreadsheet will be a lot easily initially (and a lot harder to screw up)

[loleg]

@rgrp

• I'm okay with one page...
• so will add a featured flag
• CSV is quite hard to screw up

[rufuspollock]

@loleg great - shall we run off local CSV for the time being then? We can always pull this regularly from a gdoc version if need be?

[rufuspollock]

OK, I think we do need to move this over to https://github.com/ckan/extensions.ckan.org since it is not clear atm whether we will switch ckan.org to github pages (at least not near-term) and this is something we'd really like to do.