AI Publisher helped SnoutScoop start moving again.
That solved one part of the problem, but it exposed another one almost immediately: once an article existed, it still had to be shared.
I do not enjoy posting on social networks by hand. It is not just the time. It is the tiny stress of choosing the text, checking the image, opening another interface, remembering what was posted where, copying the link, adjusting the hashtags, and trying not to feel ridiculous while doing all of it.
For a site like SnoutScoop, that kind of friction matters. The site can publish one article a day, but if every article also creates a little pile of social tasks, the workflow becomes heavy again.
So Social Publisher started from a very ordinary irritation: I wanted WordPress to remember the social work for me.
Draft first, again
The first rule was the same as AI Publisher: do not jump straight to autopilot.
Social Publisher does not have to publish immediately. It creates social drafts connected to a source article. Each channel can have its own text, hashtags, image, status, schedule, and publishing notes. The campaign becomes a review surface instead of a hidden background action.
That matters because social publishing is not only a technical action. It is an editorial action. The text that works for Facebook is not necessarily the same as the text that works for Instagram. A future LinkedIn post for a professional site will need a different tone again.
The plugin needed to make that difference visible.
The campaign became the workspace
The useful object was not a single post. It was the campaign.
A campaign starts from a WordPress article and gathers the social drafts around it. For SnoutScoop, that can mean Facebook and Instagram. For another Lubinik site, it might mean LinkedIn, a different image strategy, or a manual-only channel that exists only as a checklist.
The campaign screen became the place where I can see the source article, preview each draft, copy the text, review hashtags, check the image, mark a draft as approved, send it to automation, or schedule the whole campaign with a shared rhythm.
That sounds small, but it changes the feeling of the work. Instead of hunting through several platforms and trying to remember what happened, the state lives in WordPress.
Make instead of fighting every API
I started looking at the social APIs, and the answer was immediately clear: this was not the battle I wanted Social Publisher to fight first.
Facebook, Instagram, X, TikTok, and LinkedIn all have their own rules, permissions, formats, media requirements, and developer-console rituals. Building every integration directly inside a WordPress plugin would have turned a workflow tool into a social API maintenance project.
So the first real publishing bridge uses Make.
The plugin sends a structured webhook payload when a social draft is ready. Make handles the platform-specific module. Then Make can call back to WordPress with the result, so the draft can be marked as published with an external ID, URL, note, and timestamp.
That keeps the plugin focused on what it owns: preparing, reviewing, scheduling, and tracking social work from inside WordPress.
Scheduling without pretending WordPress is a server cron
The scheduling layer was another useful reminder that WordPress is WordPress.
Social Publisher can store scheduled times and process due drafts through WP-Cron. That is enough for many sites, especially when the site has normal traffic. But it is not the same thing as a guaranteed server cron running every minute. If a hosting plan only gives hourly cron, or if WP-Cron depends on visits, the system has to be honest about that.
For now, that is acceptable. The plugin supports scheduled drafts and batch processing, while the site can decide whether WP-Cron, an external ping, Make, or a real server cron should wake WordPress reliably.
Again, the reusable plugin owns the engine. The site owns the operational choice.
AI belongs in the draft, not in the way
Social Publisher can also use AI to rewrite social drafts, but only where it helps.
That was an important distinction. For SnoutScoop, Facebook and Instagram are useful right now. X is not worth paying for, and TikTok needs a different content strategy because video, captions, and carousel-style posts are not the same job. If a channel is not actually being used, rewriting copy for it is just wasted tokens.
So the child theme configuration decides which channels exist. If SnoutScoop only wants Facebook and Instagram today, the plugin should not care. If a professional site later wants LinkedIn, the same engine can support a different channel with a different tone.
The lesson
Social Publisher is not glamorous infrastructure.
It is the kind of tool that exists because a repeated task was annoying enough to deserve a system. That is exactly the kind of tool Lubinik tends to grow.
AI Publisher made it easier to create articles. Social Publisher makes it easier to keep those articles moving after publication. Together, they turn a blog from a place where content gets stuck into a workflow that can keep going.
Not because everything is automatic. Because the boring parts finally have somewhere to live.
