Nexus — technical foundation for publishing and automation
● Running
Nexus is the technical foundation of Triple8Labs — a WordPress-based publishing and automation hub designed to run with minimal manual effort. It connects the site to external AI and automation systems, starting with an n8n-powered content pipeline and expanding to cover video production, SEO, affiliate management, and distribution. The goal is a system that handles production overhead so the focus stays on ideas worth sharing.
What it does
Nexus provides the infrastructure layer that every other Triple8Labs project publishes through. At its core is a WordPress site configured as an intelligent content hub — connected to n8n workflows, AI generation tools, SEO automation, and affiliate link management.
Content enters as a brief and exits as a fully formatted draft; with the article written by Claude, featured image generated by Google Imagen, SEO metadata applied via Rank Math, tags created and attached, and a Slack notification sent for review. Future workflows will extend this to video production, social distribution, and translation.
Started
May 2026
Status
Foundation live with article publishing pipeline. Video and distribution workflows planned for future stages.
Tools
WordPress · n8n · Claude (Anthropic) · Google Imagen 4 · Rank Math · Slack
What’s been built
Publishing Pipeline
An n8n workflow that takes a prompt and produces a complete WordPress draft — including content, image, SEO fields, and tags — in under two minutes.
Site Infrastructure
WordPress configured with SEO, affiliate management, GDPR compliance, security, caching, and MCP access for AI-assisted management.
Automated Technical Foundation
Dev and production n8n instances connected to WordPress via REST API. Credential structure designed for portability and future workflow
expansion.
Asset Links
Honest assessment
The infrastructure took longer to set up than expected — mostly because decisions that look simple (which SEO plugin, which editor, how to handle authentication) have downstream consequences worth getting right once. The publishing pipeline works well in practice. Content quality is directly proportional to prompt quality; the workflow removes production friction, not editorial judgment. The foundation is solid enough to build on.
