Added Framework Integration section, djiiif entry

[rogerhoward]

Per issue #172 I created a new section, Framework Integration, and added a djiiif entry

I would rather use an existing section but none seemed relevant.

[saracarl]

So the Django integration is awesome, but the guidelines say we should have 2 items to introduce a new category. A lot of the equivalent libraries are in the "Image Server Shims" category, not particularly appropriately.

What if we created a section called "libraries" or maybe "language support" and put djiiif as well as these two in it?: Djatoka Ruby gem convert IIIF URLs into the URLs that Djatoka requires. Flask-IIIF Flask extension to support IIIF in Python/Flask applications. See Flask-IIIF previewer demo and Flask-IIIF RESTful demo.

Thoughts? From anyone, but @jronallo @glenrobson in particular?

[saracarl]

Upon further reflection, this is almost exactly the same as the Djakota Ruby gem, so maybe we should just put it under "Image Server Shims" (what djiiif is acting like in this instance) and be done with it?

[jronallo]

Yes, for now we can add this to an existing section. One of the tasks we'll talk about in DC in May is this kind of categorization question. I'll make an issue for this.

If for now the pull request could be updated to add to the end of the same list as includes the djatoka gem, I'd merge.

[saracarl]

@rogerhoward could you move this to the "image server shims" section? Thanks!

[julsraemy]

Ping @rogerhoward :)