When:
to
Room:
Room 1 (133-134)
Tags:
leadership, management, & business, site building, content & marketing
Track:
users & editors

Over 15000 courses and almost 100 different providers - Developing and maintaining a custom Course Marketing system

Over 15000 courses and almost 100 different providers - Developing and maintaining a custom Course Marketing system

Alan Burke (alanburke), Siobhán Brennan

Everyone is special. No more so than the almost 1000 further education providers across Ireland who provide information for use on the National Further Education Portal.
We’ll show you how we streamlined the process for gathering, maintaining and distributing information on educational opportunities throughout the country, and how we used Drupal to deliver this.

Prerequisite
Some familiarity with standard Drupal Editorial flow
How hard change can be!

Outline
The sheer volume of content on this site means that the standard Drupal editorial flows were insufficient. Alongside that, there are some custom editorial flows, including bypassing of work in draft, and bulk updates of content based on arbitrary values.
We’ll show how we leveraged and extended Drupal’s Workflows and Search API modules to facilitate the editorial control required.
Furthermore, we can show how we allowed tight control of content contribution from external providers, as well as usage of Drupal’s JSONAPI to replace a limited custom export function that existed on the previous site.

Key Topics
The challenges faced when gathering information from providers with significantly varying sizes and editorial processes
The difficulty in providing a single specialised search experience for different audiences with their own requirements

Learning Objectives
Attendees will learn
That standard Drupal editorial flow can be limited, but still forms a sound basis for facilitating complex editorial requirements.
That JSONAPI forms the basis for very flexible distribution of data to 3rd party consumers
That SearchAPI and facets can significantly improve not just the front-end search experience, but the backend editorial flow
That some items proved beyond even SearchAPI [or the developer!]