wunderio / wunderhub

A central content repository for the WunderSites.
http://docs.wunderhub.apiary.io/
GNU General Public License v2.0
3 stars 3 forks source link

Adds WunderHub services module #29

Closed joesb closed 8 years ago

joesb commented 8 years ago

Includes

lewisnyman commented 8 years ago

What's the content strategy behind the heirachy of services and service areas? I don't see an example of this on wunder.uk or wunderkraut.com?

lewisnyman commented 8 years ago

/api/menutree/{menu_name} - menu tree of a specified menu, but menu needs to be 'allowed' in admin form at /admin/config/services/wunderhub

Why do we need a menu tree? Is that how we would pull all services for one service area?

joesb commented 8 years ago

On wunder.uk homepage, the Service Areas are those 6 things on the homepage

lewisnyman commented 8 years ago

Ah ok so a service area would be something like training and then you would have types of training as services within that?

joesb commented 8 years ago

The menutree API is so that a subscribing site wanted to construct a menu of content (not just the services stuff, but any content in and any menu made available for the API), they can pull one from the hub site

joesb commented 8 years ago

Re services/areas: Yes, exactly - 'Drupal & Agile Training' service area encapsulates services Drupal training, agile training, agile coaching, etc, etc.

(Some services fit more than one area, of course)

lewisnyman commented 8 years ago

Which url would I hit to get all services in the "consulting" service area?

joesb commented 8 years ago

So with that last update :wink: I've add a query filter so you can filter like so:

/api/services?servicearea={some_term}

… where {some_term} is a 'contains' filter, so

/api/services?servicearea=consulting

… would retrieve any services in service areas called e.g. Drupal Consulting OR Agile Consulting

joesb commented 8 years ago

Yay!