Creating content is straightforward; getting it onto WordPress, Dev.to, Substack and other sites with correct metadata, images and canonical URLs is messy. The author rejected the copy‑paste, reformat loop and built a Git‑driven, write‑once publishing pipeline that turns a Markdown file into safe, repeatable posts across platforms.

The core principle treats Markdown in Git as the single source of truth. A Jenkins CI job pulls the repo, computes a content hash, checks a PostgreSQL state table and, if needed, uploads featured images via the WordPress REST API before creating or updating the post. The process is idempotent and stateless at the CI level.

Because state lives in PostgreSQL, the system detects changes and avoids duplicate publishing, while new targets—Dev.to, Substack, Patreon—can be added without touching core code. Future plans include containerizing the publisher, running it on Kubernetes, exposing a UI and offering Publishing as a Service, turning the pipeline into a reusable backend.