Write it in Claude. Publish it from Claude.

On a website built on OYNKcms, publishing a blog post is one message to Claude. You ask for the post, or you paste in one you have written, and Claude puts it on your website: on brand, checked, and live at its own address. This article was published that way on 11 September 2026, and it explains what happens in between.

How do I publish a blog post from Claude?

Once your site is connected, which takes a couple of minutes and is done once, the whole job is a single request. Something like:

“Write a post for our insights section on why we moved to hand-coded sites, about 800 words, and publish it.”

Claude then does the following without being asked, because the connection tells it to:

1. Reads the site brief. Every OYNKcms site carries a description of its voice, its audience, what to avoid, and the scores a page has to reach before it can go live.
2. Reads an existing post. So the new one uses the same sections, the same heading style and the same closing call to action as the rest of the site.
3. Writes the post into the blog collection, with a search title, a meta description and a readable address.
4. Runs the checks. The CMS scores each page for search engines and for AI search tools. Claude reads the results and fixes anything below the site’s minimum before going on.
5. Publishes. The post goes live at its own address and the insights index is rebuilt to include it.

You get a link back. Total time, from request to live page, is a few minutes.

What if I have already written it?

Then paste it in and say “post this”. Claude will not rewrite your words. It puts them into the site’s structure, adds the search title and description if you have not, runs the same checks, and publishes. If a check fails, say the description is too long or a heading is missing, it tells you what it changed to pass, and nothing more.

The same works for a Word document, a Google Doc, or notes typed into your phone. What Claude needs is the words. The rest is already decided by the site.

Why the design cannot break

This is the part that makes it safe to let an assistant publish. In OYNKcms, the site owns the design and the CMS owns the words. A blog post has a heading, a lede, a body and a closing line, and those are the only things Claude can fill in. There is no layout to knock out of shape, no font to swap, no column to move. What Claude publishes looks like every other post on the site because it cannot look like anything else.

The public website is plain files with no editor running inside it, so the post that goes live is the page we built, with your words in it, and nothing added by the system that published it.

What you still control

• Which sites. You choose what Claude can see when you connect it. One site, several, or all of them.
• Whether it publishes. Publishing is its own permission. If you would rather read a draft first, leave it off and Claude proposes the post into a change set for you to approve. If you want the post live, leave it on.
• The record. Every publish is logged with who connected the assistant and what changed, and every published page can be rolled back to the version before it.
• The off switch. Disconnecting an assistant is one click in settings and takes effect immediately.

A worked example: this article

This post was written and published by Claude on 11 September 2026. The request was for an article explaining how a client publishes a blog post from Claude on an OYNKcms site. Claude read the site brief, read the llms.txt article to match its structure, wrote this, ran the search and AI-readability checks, and published it to the insights section. The first attempt was taken down and redone because it made the wrong argument, which is worth saying: taking a post off the site is one instruction too.

Who this is for

Teams with something to say and no one whose job it is to say it. Marketing managers who write the post on a Tuesday and wait a fortnight for it to appear. Small organisations where the website is edited by whoever has the login this month. On an OYNKcms site the person with the idea is the person who publishes it, and the tool they use is the one they already have open.

How OYNKcms fits into a build, and what it costs, is on the OYNKcms page. If you want your site to be readable by AI as well as editable from it, llms.txt is the other half of that.