Keryx¶
Turn a written post into a short narrated video and proclaim it across social platforms — on demand and on a schedule.
“KEH-riks” · /ˈkɛrɪks/ · from Greek κῆρυξ, “herald” · the content-marketing automation for phpboyscout.uk
Status — generation pipeline works; posting + studio landing
The CLI runs the full reel pipeline (storyboard → VO + music → cards/cover →
assembled mp4, or one-pass with reel make) and
composes per-platform social copy; the platform publishers and the web studio
are in active development. The design spec is the
source of truth; these docs grow with the build.
What Keryx does¶
It builds a 9:16 reel from a storyboard — text cards over generated or uploaded imagery, voice-clone narration, and a tone-matched music bed — then publishes it to Instagram, YouTube, TikTok and LinkedIn. It runs interactively from the CLI (and a future web studio), and unattended from GitLab scheduled pipelines. It's built on go-tool-base, ships as a single Go binary, and keeps no state of its own — your project's git repo owns the reels, config, and schedule.
-
The authoring loop, themes, pluggable providers, the social lifecycle, and git-first persistence.
-
The packages and CLI surface — landing as the build progresses.
-
Make a reel, compose social copy, post on demand, schedule unattended runs.
-
The four specs (design · contracts · video · future) and the requirement IDs that anchor the tests.
-
Why Keryx, the name, status and roadmap.
-
Ways of working, the UI mockup, and how the pieces fit.