ChicagoShining Studio
Pipeline administration
Connecting…

Chicago Shining

QA Multi-Platform Social Media Publishing

How do you want to start?

Two doors. Same pipeline underneath. Come back here anytime to start something new.

Overview

Pipeline dashboard

Click a card to show those records below. The cards stay on this page.

Recent platform outputs

Normalized states hide scenario implementation details while preserving actionable status.

Intake

Ideas

Write or pick a brief, then add photos. Promotion happens after the photos are in — not from the type list on the idea.

Production

Production

Open a draft, continue platform prep, or review promoted items.

Production request drafts

Saved creative requests waiting for approval/promotion. Opening a draft does not interrupt photo uploads.

Promoted content items

Items that have entered the existing production pipeline.

Execution + creative review

Platform pipeline

Click an output row to watch the render, see the photo package, and read the caption. Studio state refreshes automatically while this page is open.

Checking for updates…
Background audio

Music library

Browse the current Airtable background-music catalogue and preview available tracks before production.

Control

Operations

Per-profile daily ideas, library intake, publish queues, oversized compression, and render retries.

Daily ideas

When a profile toggle is on, the Worker runs I1 once per Chicago day around 1:00 a.m. for that profile only.

Loading profiles…

Library intake

Opening this tab checks Airtable for assets that need classification or compression. Process intake only when you want A2 to scan the Drive folder.

Ready to schedule

Approved outputs that still need a post date. Set the time here instead of waiting for a reminder email.

Ready to publish

Due packages. Auto-publish still runs from Pipeline review. Use this when you posted by hand and need to mark them published.

Oversized library videos

Files over 100 MB. Compress starts A1S for that Drive file instead of a daily folder scan.

Render repair

Use these when Remotion moved URL, asset selection failed, or a Make admin command is waiting. They do not run on a clock.

Help

Support

A full idea-to-publish walkthrough, then a guide for each Studio page.

Idea through publish on every platform

This is the photo-based path ChicagoShining Studio uses today: write or pick an idea, attach stills, let Studio plan the packages, review the renders, then approve. Instagram, Facebook, and YouTube publish publicly. TikTok is saved as a draft.

Home page with Start with Idea and Start with Content
Home is the fork. Same pipeline either way.
  1. Choose the working profile on Home. The city profile (Chicago, New York, Los Angeles) stamps branding, defaults, and which library the new work uses. You can change it later in the top bar.
  2. Start with Idea. On Home, choose Start with Idea. On Ideas, pick an unpromoted candidate from I1–I4, generate a batch, or type a title and optional summary. Do not promote from the type list yet — photos come first.
    Ideas page with start form and candidate table
    Ideas — select an existing candidate or enter one, then continue. Manage opens the drawer to add photos.
  3. Add photos from the idea drawer. Open the idea, then Add photos. That creates a Production request. Drop in the stills. Studio builds a multi-platform plan from the photo count, not from a content-type picker on the idea.
  4. Confirm platforms and crops in Production. Default multi-photo packages: Instagram Reel, Facebook Slideshow Reel, TikTok Video Draft, YouTube Short. Instagram and Facebook also keep silent 9:16 Story companions. Single-photo work plans feed/still packages instead. Reframe crops, write or AI-fill captions, leave Voiceover and Music on Yes unless you want a silent cut, then Save.
    Production start-with-content screen with photo drop zone
    Production — name the piece, choose single or multiple photos, drop stills, then set platforms and audio.
  5. Approve & Promote. Production hands the request to the existing pipeline (P3 and render). Companion Stories attach from the same 9:16 stills. YouTube 16:9 covers can finish in the background; 9:16 plan crops are enough to continue.
  6. Watch Pipeline until Ready for Review. Open Platform Pipeline. Rows move through package, asset selection, Remotion render, and review mail. Click a row to open the creative editor: preview, audio mix, per-photo titles, then Save & rerender preview if you change the mix.
    Platform pipeline table with Instagram Facebook TikTok and YouTube outputs
    Pipeline — one row per platform output. Open review when Ready for Review, then Approve for publishing or Approve All.
  7. Approve for publishing. When the preview is right, Approve for publishing (or Pipeline Approve All). Confirm the public/draft warning. Studio stages a public R2 URL (AP0) for video, then:
    • Instagram Reel — auto-publish to the professional account
    • Instagram Story companion — AP1 story webhook
    • Facebook Slideshow Reel — FBS3 / FBS4
    • Facebook Story companion — Graph binary upload
    • TikTok Video Draft — TTD0 (stays a draft in TikTok)
    • YouTube Short — YouTube orchestrator when the row is due
    Carousels, Facebook multi-image, and TikTok multi-photo use the native still packages instead of a Remotion reel. Those publish through their own carousel / photo paths after the same Approve.
  8. Confirm in Operations if you need a clock or a manual mark. Ready to schedule lists approved rows that still need a post time. Ready to publish lists due packages. Use mark published only when you posted by hand. Daily ideas, Drive intake, and render repair live on the same page (admin roles).
    Operations page with daily ideas, intake, and publish queues
    Operations — schedule a post time, mark a hand-posted URL, or pulse intake and render repair.

Other entry: Home Start with Content skips the Ideas table. You name the piece on Production, drop photos, and the rest of this walkthrough is the same from step 4.