As part of the efforts to bring 3scale's CMS API up and running, we need to adjust the JSON response formats for the CMS endpoints, following these guidelines:

# GET /admin/api/cms/templates.json
{
  "collection": [
    { "id": 1, "type": "page", ... },
    { "id": 10, "type": "partial", ... }
  ],
  "metadata": {...}
} 

("collection" is a generic key that can be used by any endpoint that returns a collection of objects). 

# GET /admin/api/cms/templates/1.json
{ "id": 1, "type": "page", ... } 

(Instead of having different keys for each type of template object, we simply add a "type" attribute to the response).

# GET /admin/api/cms/files.json
{
  "collection": [
    { "id": 2, "title": "some title", ... },
    { "id": 3, "title": "some other title", ... }
  ],
  "metadata": {...}
} 

# GET /admin/api/cms/files/2.json
{ "id": 2, "title": "some title", ... } 

/admin/api/cms/sections and /admin/api/cms/sections/:id have a similar behaviour as /files.

Notes

The attributes currently returned by the CMS API should not change aside from the addition of the "type" key for the /templates endpoints;