← Back to selected work

Ripley’s Entertainment · Workflow automation

Editorial Workflow Automation

Automated recurring editorial steps across notifications, editing, approvals, scheduling, and publishing.

RoleSenior Web Developer / Team Lead
DatesJune 2022 – April 2025
Platform/scopeWordPress multisite editorial workflow
AudienceEditorial and publishing teams

Project imagery

From scattered tasks to a connected workflow.

Conceptual illustration of scattered documents and media flowing through editing, approval, scheduling, and publishing into multiple digital channels.
Conceptual illustration of editorial workflow automation; it does not depict the actual system or its integrations.

Reported outcomes

  • ~8 hrs manual work saved per week; approximate observed estimate

01 / Context

The work in context.

A custom workflow built for Ripley’s WordPress multisite to connect editorial notifications, review, approvals, scheduling, and publishing.

02 / Challenge

The problem to solve.

Teams relied on back-and-forth messages to signal when content was ready for review, request status changes or approvals, and coordinate publishing dates. Waiting for replies added delays and recurring manual work.

03 / Approach

How I approached it.

  • Automate the connected editorial process rather than one isolated step.
  • Define clear rules for what triggers each stage so teams could follow the workflow with minimal training.

04 / Implementation

What I delivered.

  • Planned and built a custom workflow alongside common WordPress multisite plugins.
  • Connected notifications, editing, approvals, scheduling, and publishing with rules that determined when each step was ready.
  • Introduced the workflow with minor training; its clear interface supported quick adoption.
  1. 01 Notifications
  2. 02 Editing
  3. 03 Approvals
  4. 04 Scheduling
  5. 05 Publishing

Stages shown reflect the documented workflow; implementation details are not inferred.

05 / Constraints & tradeoffs

What shaped the work.

  • The workflow needed to coordinate handoffs between editorial and other teams without removing the review and approval steps.

06 / Outcome

What changed.

The workflow was adopted quickly and saved an estimated eight hours of manual work per week, based on observation.

The weekly time saving is an estimate based on observation, not time-tracking data.

  • WordPress multisite
  • Custom workflow
  • WordPress plugins

07 / Reflection

What I take forward.

Automating the handoffs as well as the publishing steps reduced repeated coordination while keeping editorial review in the process.