With the initial version of the publishing pipeline in place, this release marks a small but important step forward.
## What’s new in v1.1.0
The pipeline now supports **publishing to Dev.to** in addition to WordPress.
Content is still written once, in Markdown, and then distributed automatically.
WordPress remains the **canonical source**. This means:
– A post is considered authoritative once it exists on WordPress
– Any downstream platform (Dev.to, X, LinkedIn, etc.) builds on that state
– Republishing only happens when the content actually changes
This avoids duplicate work and keeps all platforms consistent.
## Why this matters
So far, this setup already enables:
– Write-once publishing
– Deterministic re-runs in CI
– Platform-specific adapters without content duplication
– A single source of truth stored in PostgreSQL
This makes it easy to add new platforms without rewriting the pipeline.
## Roadmap: backlink graph and content relationships
The next planned step is to introduce a **backlink graph** between posts.
The idea is simple:
– Detect links between posts automatically
– Track relationships in the database
– Use this data to:
– Improve internal linking
– Strengthen SEO
– Keep related content connected over time
This only becomes meaningful once there is more than one post — which is now the case. And many more will come!
> And the real good part is: I finally get to learn Python. As a DevOPS engineer and *nix admin I have been dealing with Puppet, Ansible, Shell scripts and the likes for many years, but never got to come close to application programming. Simply because that kinda programming is much different. Well now here I am!
—
## Related posts
– [Building a Write-Once Publishing Pipeline](/publishing-pipeline/)
—
This release is intentionally small, but it lays the groundwork for more powerful features to come.
Did you find this post helpful? You can support me.
[](https://www.buymeacoffee.com/grizzly_coda)
Author Profile
