Skip to content
Brian Bautista — home
Back to work
Trusted Media Brands2026Live

Magazine Cover Pipeline

GCP-native automation that turns a dropped PDF into an approved, published magazine cover across 13 TMB brands.

EventarcCloud RunGCSTeams
Concept mockup of a pipeline run console headed "Magazine Cover Pipeline": six stage cards connected left to right reading PDF Drop, Eventarc Trigger, Cloud Run Processing, Teams Approval, GCS Publish and Jira Cache Purge. The first three carry grey "Done" chips, the Teams Approval card glows orange with an "Awaiting approval" chip, and the last two are marked "Queued". A detail strip below shows Run, Started and Duration with em-dash placeholders.
Concept mockup — the run console: one cover in flight, held at the human approval step.

The Problem

Publishing a magazine cover across 13 brands meant a manual handoff between design, approval, and the CMS every single issue, repeated brand by brand.

What I Built

A GCP-native pipeline that starts the moment a cover PDF is dropped in. An Eventarc trigger kicks off Cloud Run processing, the approval step lands as a Teams Adaptive Card so a stakeholder can sign off without leaving chat, the approved cover publishes straight to GCS, and a Jira ticket fires automatically to purge the cache.

Selected Work

Concept mockup of an approval card in a chat thread, titled "Magazine Cover Approval" with the subtitle "Microsoft Teams Adaptive Card". A portrait cover-preview thumbnail is drawn as plain grey placeholder blocks with no readable title. Beside it, rows labelled Brand, Issue and Submitted all show em dashes. A solid orange Approve button and an outlined Reject button sit at the foot of the card.
Concept mockup — the approval step: an Adaptive Card carries the sign-off into Teams, so nobody leaves chat.
Concept mockup of a run-history table headed "Cover runs — all brands", with thirteen rows listed as anonymised placeholders from Brand 01 to Brand 13. Columns read Last run (all em dashes), Approval (mostly "Approved in Teams", one row "Pending") and Status (grey "Published" pills, with one orange "Awaiting approval" chip on the pending row).
Concept mockup — run history across all 13 brands; brand names and run times are placeholders.

How It Works

01PDF drop
02Eventarc trigger
03Cloud Run processing
04Teams Adaptive Card approval
05GCS publish
06Jira cache-purge ticket

Outcome

One pipeline now runs cover publishing for every TMB brand instead of thirteen manual processes.

13TMB brands running through one pipeline

My role

Creative Technologist at TMB — designed the pipeline, built it, and shipped it to production.

Stack

Google Cloud PlatformEventarcCloud RunGoogle Cloud StorageMicrosoft Teams Adaptive CardsJira
Next

StockPull

Trusted Media Brands · 2026

Back to all work