Skip to main content
Skip to content
Start a project
Hutchison Drei / Earlier work / Drupal campaign integration

A name submitted online. A moment on the Riesenrad.

Drei invited people to put their names on the Wiener Riesenrad. SDEV built the Drupal workflow that connected online submissions with editorial review and the display queue, turning participation on the website into part of the campaign in Vienna.

SDEV contribution
Custom Drupal development, submission workflow, moderation integration and XML display feed
Platform foundation
Drupal · Webform · Views · Flag · XML feed
Engagement
Completed campaign project
Project timeline
July 2021
01 / The campaign challenge

Public participation.Reviewed before display.

For the July 2021 “Dreh auf mit Drei” campaign, participants could submit a first name or nickname online to appear on the Wiener Riesenrad.

The digital workflow needed to keep participation straightforward while giving editors control over what reached the public display. It also had to account for opening hours, demand and the time available each evening.

02 / What SDEV built

From the website.Into the display queue.

SDEV developed the custom Drupal module connecting submissions, moderation and the projection feed. Editors reviewed entries and approved or rejected them before they entered the display queue.

Approved entries were processed into that queue within seconds. Names could appear shortly afterwards when capacity allowed; during busy periods, participants waited for the entries ahead of them.

  1. Submit a name

    A participant entered a name through the campaign’s Drupal form. Clear participation limits kept submissions within the evening’s available capacity.

  2. Review before display

    Editors checked submissions and decided which names could enter the display queue.

  3. Queue the approved entry

    The XML feed supplied approved names in sequence, with configurable display intervals.

  4. Set expectations for the participant

    Queue length informed the estimated waiting time. If the remaining evening was fully booked, the website stopped accepting further entries.

03 / Platform architecture

Drupal managed participation.XML connected the display.

Drupal Webform held the submissions. Views and flags supported the moderation and display queue, while the custom module returned the next queued name through an XML endpoint.

Moderators could configure display intervals and fallback names for an empty queue. Submission and confirmation logic accounted for the 21:00–24:00 campaign window and estimated display time.

This gave editors control over public submissions while keeping the website and display queue connected.

Common questions

The detailsthat matter.

Campaign & delivery

What did SDEV build for the Riesenrad campaign?

SDEV developed the custom Drupal submission, moderation and display-feed workflow for Drei’s July 2021 Wiener Riesenrad campaign.

Were names displayed automatically after submission?

Editors reviewed submissions first. Approved names entered the display queue and were provided to the display system through an XML feed.

Queue & timing

How quickly were approved entries processed?

Approved entries were processed into the display queue within seconds. Actual projection timing depended on how many entries were waiting and the configured display interval.

How did the workflow handle a busy or empty queue?

Queue length informed estimated waiting times and the evening’s capacity cutoff. Configurable fallback names provided content when the queue was empty.

Let’s make the next step useful

Connect participation. Build the workflow behind it.

Planning a campaign that connects people, content and external systems? Let’s look at the experience and the integration it needs.

Start a project