Version 1.1.0 of the publishing pipeline introduces publishing to Dev.to, working alongside WordPress. Content remains written once in Markdown for automatic distribution, keeping workflows simple. WordPress stays the canonical source, ensuring one authoritative version. Republishing only triggers when content actually changes, which prevents duplication and maintains consistency across every connected platform in the system.

This setup delivers write-once publishing, deterministic CI re-runs, and platform-specific adapters without content duplication. A single source of truth in PostgreSQL makes adding new destinations straightforward. For developers managing multiple channels, this approach reduces maintenance overhead and lets teams scale distribution without rewriting core logic or juggling conflicting versions across platforms.

Looking ahead, the roadmap targets a backlink graph to automatically detect and track links between posts. That data should improve internal linking, strengthen SEO, and keep related content connected as the archive grows. With enough posts in place, the graph becomes meaningful, setting the stage for smarter recommendations and stronger content discoverability. Expect more platforms and features soon.