Lubinik AI Publisher did not start as a grand AI feature.
It started because SnoutScoop had stopped moving.
The site had content, a voice, a niche, an archive, and plenty of possible future topics. The problem was not that there was nothing to write about. The problem was that publishing had become too heavy.
A new post was not just a new post. It meant choosing a topic, checking that the archive had not already covered it, finding sources when facts mattered, writing the article, choosing a category, adding tags, preparing images, converting media properly, setting a featured image, and making sure the result did not feel generic or careless.
None of those steps were impossible. Together, they were enough friction to keep the site quiet.
Not an autopublisher
The first rule was that this should not become an automatic content machine.
I did not want a plugin that silently publishes articles. I did not want unchecked AI text going live because a button was too powerful. I did not want SnoutScoop to turn into a pile of generated posts that technically exist but do not feel cared for.
So the plugin creates drafts. That matters.
The human review stays in the middle. AI can help with research, structure, topic generation, first drafts, and images, but the final editorial decision still belongs to the person running the site.
The workflow became the product
Once I looked at the real problem, the shape of the plugin became clearer.
Lubinik AI Publisher needed to understand the workflow around publishing, not only the text generation step. It needed to help with article ideas, sources, WordPress drafts, categories, tags, and optional images. It also needed to make the generated media usable for the site instead of leaving another manual cleanup step behind.
That is why the plugin became a small publishing workspace rather than a single “generate text” button.
- it can help suggest article ideas;
- it can turn a selected idea into a sourced draft;
- it can prepare the draft with the right category and tags;
- it can optionally help with article images;
- it keeps the post in draft until a human reviews it.
It is not trying to replace the WordPress editor. It is trying to make it easier to arrive there with a useful draft instead of a blank page and a tired brain.
The archive helps suggest what comes next
The topic suggestion feature came directly from SnoutScoop’s problem.
If a site already has dozens of posts, new ideas should not ignore that history. The plugin can use the existing archive as context, then suggest ideas that fit the site without repeating what is already there.
For SnoutScoop, the child theme defines the editorial context: a dog-focused site, warm and playful, but still useful and source-aware when the topic touches health, behavior, safety, history, or recommendations.
That is the Lubinik pattern again. The plugin owns the engine. The child theme owns the site-specific truth.
Configurable, but not site-specific
I also did not want the plugin to become hardcoded for SnoutScoop only.
The reusable part belongs in the plugin: the publishing workflow, the draft creation, the source-aware generation, the media preparation, and the review-friendly structure. The site-specific part belongs closer to the site itself: tone, editorial boundaries, image direction, and the kind of topics that make sense for that audience.
That keeps AI Publisher useful beyond one site without turning it into a generic black box.
Images had to be part of it
SnoutScoop is visual. A publishing assistant that only generates text would still leave a lot of manual work behind.
So AI Publisher can optionally create a featured image and inline images. Before they enter WordPress, generated images go through a WebP media pipeline. The goal is not to fill every article with random dog pictures. The child theme can define image styles, visual planning rules, and prompts that keep the images varied, article-specific, and useful.
That part is still evolving, but the rule is already clear: images should support the article, not become decoration that happens to have a dog in it.
The lesson
AI Publisher exists because a real site had a real publishing bottleneck.
That is the kind of AI tooling I trust more: not magic, not replacement, not autopilot, but a practical assistant built around the annoying parts of a workflow that already exists.
For Lubinik, it also adds a new kind of support plugin. SEO Light helps sites explain themselves. The updater helps them stay maintainable. AI Publisher helps them keep publishing without making every article feel like a full manual rebuild.
SnoutScoop stopped moving, and the fix was not only to migrate it. The fix was to make publishing lighter the next time.
