Content Studio

In-house software — SwiftSoftware internal use only. There is no public sign-up; accounts are created on the server.

Privacy Policy · Terms of Service

Library

Every finished piece of marketing content. Click a card to play it, download the video or its captions, and move it through review. Cards appear on their own — nothing is uploaded here.

draft just made, not looked at yet review you're checking it approved good to use published already out there

Assets

Every finished marketing asset in one place — decks, videos, images, logos, GIFs, audio, copy and landing pages — filed under the business it belongs to. View opens the asset on its own page, so the same link works on a phone. A landing page is a record, not a file: it points at the live page on its own domain. Finished work from Muse lands here automatically.

House a new asset

A page's public address is the business's domain plus this name. Never a token.

Publish

engine…

The posting scheduler, in its own bucket. Walkthrough videos live in Library; posting lives here. Each business has its own workspace, so its pieces, channels and schedule stay apart. Only an approved piece can be queued — and P1 runs against the stub adapter, so no platform call is made yet.

Engine & Marketing Admin

checking…
Posting engine
…
Marketing Admin → Content Studio
…

The Marketing Admin sends its plan to /api/plan with its own key; the engine picks those posts up on its next tick. Nothing here is assumed — a connection that has never sent a plan says so.

Workspaces

Compose

P1 test hook

Calendar

queued waiting for the engine published out failed gave up after 3 attempts

Publish log

Accounts

Connect a platform account

The token is sealed with AES-256-GCM before it is written and is never shown again — not here, and not by any route. Connecting the same platform account id a second time replaces its token, which is how a refresh is applied; nothing is ever logged with the token in it.

The Accounts table above is what the engine will post as. Until an account is connected for a platform, a post for it runs through the stub adapter.

X (Twitter) — manual queue

Manual only. Nothing here is sent by Content Studio: X's API is a paid tier we do not buy, so there is no X adapter and no credential. David approves the piece in chat with Muse first; Muse hands the approved copy and its asset link into this queue; David copies it, opens the asset, posts it himself, and marks it posted. Pieces never enter this queue unapproved, because nothing but an approved hand-off is accepted.

How to use this

1 · Workspaces keep products apart

The list on the left groups content by product — one workspace per piece of software. Click a workspace to see only that product's videos; click All content to see everything.

Within a workspace a piece is either marketing (for selling) or tutorial (for teaching). Same library, kept apart.

2 · Finding a video

Open Library. Each card is one finished piece. The orange line under the title names the product. The tags show the kind, the formats (16:9 for the site and YouTube, 9:16 for TikTok, Reels and Shorts), the length, and where it is in review.

3 · Watching it

Click a card. It opens in a player — press play, scrub like any video. Below it is the shot list, so you know what happens without watching twice.

4 · Downloading the pieces

The buttons under the title download the MP4, the SRT captions in whichever languages exist, and the script with its timings. The captions and script are what keep a video and its words together months later.

5 · Moving it through review

The dropdown at the bottom moves it draft → review → approved → published. It saves immediately — use it to see at a glance what you've checked and what you haven't.

6 · Publishing — letting people watch without a login

Managing this library needs a login. Watching never does. Press Publish on a card and it creates a link anyone can open: the video plays, with captions, on a clean page with no dashboard around it.

Press Unpublish and that link stops working immediately. The old link never starts working again unless you publish that piece once more.

7 · Putting a tutorial inside your software

This is the point of the public link. Publish a tutorial, copy its link, and put that link behind a "Watch the tutorial" button or a help icon in the matching product. A customer clicks and lands on the video — no account on this system, no password to share.

Because each workspace is tied to one product, you always know which link belongs where. If you ever replace a video, keep the same published piece and the links already inside the product keep working.

8 · Where new videos come from

You don't upload here. A new piece is written into its own folder with a description file, and this page picks it up — immediately, or when you press Rescan. The library is built from the files themselves, so it can never show something that doesn't exist, or hide something that does.

9 · If something looks wrong

Card won't play? Try its download button — if the download works, it's a browser quirk, not a missing file.

A video is missing? Press Rescan. Still missing means its folder wasn't finished — ask me rather than guessing.

Caption in the wrong language? The language sits in the file name (.en, .es, .fr). Tell me which card and I'll fix it.

10 · Assets — the finished work, and landing pages

Assets is the shelf for work that did not come out of the video pipeline: decks, images, logos, GIFs, audio, written copy. Pick the business across the top, pick a category, or search a title or tag. Every card has a View link — it opens the file on its own page, no login, so the same link works in a text message or on a phone.

Landing Pages is a category, not a file. A record there holds the page's public name (its slug — e.g. /test-page), the domain serving it, the business, what the page is for, its tags and whether it is Draft or Live. The public address is always the domain plus that name: never a token, and never the record's internal /a/… link. A name is only confirmed once David has picked it; a name we proposed shows as such. A page reads Live only after the server itself fetched its address and got a 2xx — a record naming a domain is not proof the page serves.

Finished work from Muse is housed through the bus and appears here with its business and category already set — no upload needed.

11 · Your login

Sign in with [email protected]. Change it in System → Change password. That signs you out everywhere, which is deliberate.

12 · Publishing to the platforms (the Publish tab)

Library is for making and keeping the videos; Publish is for sending them out. They are deliberately separate buckets. In Publish every business has its own workspace — Giraudy Capital, Xride Drivers, SwiftSoftware, SwiftImpact Solutions, ZaarHub, Benu Ventures, GGC Capital, BV Premiere Products and ZaarArt — so one business's pieces, channels and schedule never mix with another's.

To schedule something: pick the workspace, pick a piece that is approved, tick the platforms, choose the time, and press Queue. Run pre-flight checks the file against that platform's real limits before anything is queued — a landscape file for Instagram Reels is refused there, with the reason, instead of failing after an upload.

The calendar is read-only: it shows what is queued, what went out and what failed. The log keeps every attempt with the platform's own error text and a Retry button. Failed posts retry twice on their own (2 then 4 minutes) before they are marked failed.

Today this runs against a stub adapter — the whole queue, pre-flight, backoff and log path is real, but no video leaves the server until the YouTube, Facebook, Instagram and TikTok credentials are connected. Connect a platform account under the Accounts box takes the token the platform issued, seals it with AES-256-GCM and stores it against the workspace; the table then shows what is connected, and each row can be turned off and back on without losing it. The token itself is never shown again by any screen.

13 · Your profile, the day/night switch, and who can get in

Profile holds your own account: the name shown here, and the password you sign in with. Changing the password asks for the current one first, then signs out every session — including the one you are on — so you come back in with the new one.

The day / night button at the bottom of the sidebar switches the whole console between dark and light. The choice is remembered on the browser you made it on.

This console is in-house software. There is no public sign-up and no customer-facing account screen: an account exists because it was created on the server, and the only thing anyone outside this company can open is a link you deliberately publish.

Profile

in-house account

Your own account. This is internal software: there is one account per person, created on the server — nobody signs themselves up.

Signed in as

…

Change password

Changing the password signs out every session, including this one, so you sign in again with the new one.

Appearance

Day or night. The choice is remembered on this browser.

System

Signed in as

Account

Your name, your password and the day/night setting live in Profile.

How assets get here

Each finished piece writes a manifest.json into its own folder under /opt/swift/media/. This page reads those manifests — nothing is typed in by hand, so the library and the files can never disagree.