Lab Notes: Nexus – Publishing And Distribution Automation
Some links in this article are affiliate links to products I actually use. If you sign up through them, I may earn a small commission — at no extra cost to you.
I’ve been running experiments for years, but always hit the same wall: that gap between having ideas and sharing them. WordPress felt like the obvious foundation – familiar, flexible, and something I could build-on, especially for publishing and distribution automation since I need it to do more than just sit there waiting for manual posts.
What Nexus Actually Is
Nexus is Triple 8 Labs’ WordPress-based publishing hub. It’s a WordPress installation connected to n8n workflows that orchestrate AI tools and automation systems. The goal is to reduce the friction between experimenting with ideas and documenting and distributing the results.
The current stack includes WordPress for publishing, n8n for workflow orchestration, a variety of AI agents including Claude, Gemini and Mistral for multiple purposes including content generation and workflow development, Google Imagen 4 for image creation, Rank Math for SEO automation, Craft.do for tracking, Originality.ai for plagiarism and fact checking, and Slack for monitoring notifications.
This isn’t meant to replace human creativity or judgement. Instead, it’s a collection of connected systems that handle the repetitive tasks that would otherwise slow me down: with concrete goals of generating SEO-optimised document outlines to be fleshed out, reviewed and published, along with packaged artefacts for public distribution. This technical foundation was deliberately built to support the other Triple8Labs experiments as they develop, and documented using the same platform to test and improve the process.
The Publishing Pipeline in Practice
The content publishing pipeline starts with submitted briefs that get processed through AI agents to generate initial draft articles, with Google Imagen 4 for accompanying visuals, Rank Math for SEO optimisation, and Slack for monitoring notifications. WordPress is the publishing endpoint, with editorial control retained throughout. The system isn’t fully autonomous, and that’s intentional.
Future expansion could include video production workflows, multi-lingual support, and broader distribution channels. These are planned features, which will be prioritised and implemented incrementally.
Why Build A Solution For Publishing And Distribution Automation
The automation layer exists to lower the barrier to documenting my experiments. Publishing and distribution are time-consuming enough that the process itself can become an obstacle — Nexus removes that excuse. Sharing documentation publicly serves two purposes: it’s content in its own right, and the transparency is part of the research.
More practically, Nexus creates a reusable foundation for other experiments so I can delegate the publishing and distribution work for each new project rather than starting from scratch each time.
You can read more about the technical details and current status at the Nexus experiment page.
