Swyp and content throughput for build-in-public

Publishing consistently is mostly a systems problem.

Swyp exists because manually generating carousels was too slow and too easy to defer.

Stack fit

Cloudflare Workers + Hono + Satori/resvg made sense because this stack already powers other projects I run. I wanted one backend pattern, not fragmented tooling.

Practical result

The engine is in-house, fast to iterate, and directly tied to how I ship content.