There is good news about this project and its progress: we are adding a new feature: Tweeting on X!
What’s new in v1.2.0
The pipeline now supports tweeting on X in addition to WordPress and Dev.to.
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
- downstream-publishing on
Dev.to
Additionally there are now backlink graphs
- 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
Now we can also tweet about it and thus amplifying reach.
I used to have external plugins for posting on X and showing related posts. External plugins are always a security risk and often enough stop working because the author had something else in mind. Moving the logic to the publisher and being able to delete those plugins was a good decision.
Did you find this post helpful? You can support me.
Related posts
- Building a Write-Once Publishing Pipeline
- Publishing Pipeline v1.1.0 – Dev.to Support and What Comes Next
- Publishing Pipeline – Refactoring
- Publishing Pipeline – inline Mermaid code
- Publishing Pipeline – LinkedIn Support
- Publishing Pipeline – Telegram
Author Profile
