About Keryx¶
Why Keryx¶
The blog phpboyscout.uk produces strong writing but leans on organic traffic. The policy is a reel per post — pushed to the platforms where a cold account can still earn algorithmic reach. Keryx turns the ad-hoc Python media scripts that proved that workflow into one self-contained, repeatable tool, and adds the posting layer.
The name¶
κῆρυξ (kēryx) is Greek for herald — the one who announces and proclaims; exactly what the tool does, carrying your words out into the world. The mark is a stylised kerykeion, the herald's winged staff.
Day to day we use the anglicised pronunciation — “KEH-riks” (or “KEH-ruhks”; /ˈkɛrɪks/, /ˈkɛrəks/), two syllables, stress on the first — as English speakers and historians say it, e.g. when discussing the Kerykes, the Athenian herald-clan. It's an English adaptation of a Greek word, though, so the living and historical traditions deserve a nod — all equally acceptable:
- Modern Greek (the living language) — “KEE-riks”: η and υ have both come to sound ee.
- Biblical / Strong's Greek — “KAY-roox” (kay'-roox): the seminary convention for reading the New Testament, where a κῆρυξ is a preacher and publisher of divine truth.
- Classical Attic (5th c. BCE) — /kɛ̂ːryks/: eta is a long “eh” (the vowel in “air”) on a falling pitch accent, and upsilon a fronted vowel like German ü / French u.
However you say it, the herald still rides. 🪽
Status¶
Design complete, build not started. The product is specified across four specs; implementation begins at Phase 1 (themes + provider seams + porting the Python generation to Go).
Roadmap¶
- Phase 1 — themes, provider seams, port reel-gen to Go (parity with the scripts).
- Phase 1.5 — the authoring loop: workspaces, takes/select, silent draft, social.
- Phase 2 — posting adapters: Instagram → YouTube → TikTok → LinkedIn.
- Phase 3 — auth, token refresh, scheduled pipelines (
post due). - Phase 4 (stretch) — the web studio (manage reels, author, publish).
- Phase 5 (deferred) — video panels (0003).
- Phase 6 (future) — longer-form pieces + in-browser capture (0004).
→ Full roadmap in the design spec §9.
Built on¶
go-tool-base — the framework for phpboyscout's Go CLI tools (config, keychain, chat client, service lifecycle, the cicd components, releaser-pleaser releases).