A real content operating system, not another spreadsheet
This first pass is designed around content decisions: what to make next, which variant wins, what assets are missing, and what is ready to publish.
Why this shape works
Idea intake
Raw ideas flow in from Sheets, prompts, campaigns, and winning social posts. Tags and trade lenses keep backlog triage fast.
Variant generation
Hooks, scripts, stills, video prompts, and audio variants live together so the team can compare winners without tab chaos.
Asset ops
Every image, video, and audio file is linked to the originating idea, campaign, and publish target.
Publish handoff
Approved work moves cleanly into Mixpost while Studio stays the source of truth for planning and review.
Design principles in this preview
- Decision-first hierarchy: the top of each screen answers what needs attention right now.
- High-signal filtering: tables and queues win over pretty clutter for this workflow.
- Persistent context: idea, asset, variant, and publish state stay linked.
- Low-noise premium feel: clean cards, warm neutrals, and strong spacing instead of generic SaaS blue soup.
Initial screen set
Filter-heavy triage view with tags, status, and campaign grouping.
Compare hooks, scripts, image/video/audio variants, and approval state.
Preview-driven library with lineage back to the original idea and campaign.
Ready-to-post queue with approval gates and Mixpost handoff status.
Execution status
MVP entity map documented for ideas, variants, assets, approvals, and publish queue
Next.js app deployed at studio.builderpal.com with HTTPS + Docker
Backlog triage, tags, score, status, source
Hooks, scripts, media variants, approval flow
Metadata-rich asset library with lineage framing
Approval-aware handoff model for Mixpost