Blog, Instagram and LinkedIn: planned, produced and tracked in one place.
How it's built
One repository, scheduled jobs and a console. Built and run with Claude Code and GitHub Actions; people stay where judgement matters.
One source
A Git repository holds 24 system files (voice, product truth, messaging, positioning) and the 13 skills every piece is written with. Content conforms to the system, not the other way around.
Scheduled jobs
14 GitHub Actions workflows, 11 of them on a schedule, produce, check and ship: the monthly Blog run, the daily Framer check, the Instagram and LinkedIn batches, a content health check and the console sync.
Blog in eight steps
Topic, brief, draft, check, German, visual run unattended about a month ahead. A morning check puts both languages into Framer three weeks out; a person reads and publishes.
Social from the Blog
LinkedIn runs a company and a founder voice, scheduled in Buffer weeks ahead. Instagram publishes rows of three, twice a week, from a 21-row grid rotation held in code.
One console
A marketing console reads state from Buffer, Framer and GA4, so what is planned, scheduled and live is visible in one place, not inferred from files.
People where it matters
Approving the plan, publishing in Framer and the founder's posts stay with people. Everything between runs on its own.
Nothing staged
Every photograph is by its author, a moodcase ambassador, and is credited where it is published.
Every screen is the real product: the moodcase platform and the marketing console, captured live. A few counters were left out; nothing was added.
Every quote and line comes from the content system, written against its voice and product truth.