Content Studio ยท MacEvery post rendered as it will look on its platform, so weeks of content can be read and judged as one body of work. It is where posts, ideas, carousels and email sequences are made and moved, for the studio's own brands and for client brands.
[Oto: why content needed its own studio, and how a week of it runs]
All platforms is a calendar: day columns from Monday, cards stacked in each day, weeks below each other. Each platform has a view that looks like that app: the blog as a blog, Base Notes as the notes list on this site, X as a timeline, YouTube as thumbnails, Instagram as a profile grid, LinkedIn and email as feeds. A card is dragged to another day to move it.
A card opens an immersive viewer: the post on the left with a slide strip for carousels, and on the right a panel for its text, status, caption and final files. Arrow keys move between posts.
The idea pipeline. Stage columns for ideas, drafting, designed and ready, then the next three weeks as days to drop items on. An item can be anything from a title to an article or a video, and can grow into an anchor or break into posts for each platform.
How the year is worked for a brand: the brief, audience, goal, pillars, platforms and their roles, cadence and voice, each edited on its own. An agent can draft it, and nothing is written until the draft is accepted.
A wall of every finished carousel, to page through, download, send to the phone's Posts shelf, or put on the calendar. Thumbnails holds video and product covers.
Email sequences shown as their emails in order, with when each is sent and each email drawn in the platform's own template. Each moves through draft, in review and approved. Approving sends nothing.
On a client brand, a post can be marked for review and sent to that client's portal. Their answers come back as a thread under the post and a note in Oto's queue. A hosted copy lets team members sign in and work on the brands they are given.
Content Studio owns no data. Every read and write goes through the dashboard's content routes.
OpenA carousel can be sent from the wall to the Posts shelf in Command, ready to share from the phone.
OpenA client's answer on a post lands as a note in the queue.
Posts marked for review go to the client's portal, and the answers come back to the post.
Agents feed in ideas, drafts and carousels; people edit, and an agent never overwrites a post a person changed last.
A small Node server on the Mac with no dependencies, serving one page. The posts are notes in the Obsidian vault, read and written through the dashboard. There is also a Mac app window for it. A hosted copy runs on Vercel with a Postgres database and image storage, so team members can sign in.
I'm starting a new brand called The Agentic Operator.
It's a space to share what I'm learning around AI and agentic workflows. Builds, software, design and the future of work.
Otoabasi Bassey