Your blog, on the same calendar as everything else.
The one channel you actually own has always been the one planned somewhere else. Connect your WordPress site and the post goes out from the same composer, at the same hour, as the announcements pointing at it.
No API key. No plugin. No copy-paste.
WordPress can authorise an application itself, so connecting is a few clicks on your own admin rather than a hunt through settings pages.
A caption in, a real post out.
A WordPress post is not a status update, and it does not arrive as one. Your post becomes the body, your images follow at the end of it, and the title is yours to write — nothing is promoted to a headline you did not choose.
- The body arrives as paragraph blocks, not one opaque lump
- Anything you schedule can still be edited on the site afterwards
- A title only if you want one — nothing is invented for you
It arrives as WordPress, not as HTML somebody pasted in.
Scheduled posts are written as real Gutenberg blocks. Open one on your site and it behaves like a post you wrote there — paragraphs you can split, images you can move, nothing locked inside a single Classic block.
- Paragraphs, line breaks and links survive intact
- Images become image blocks pointing at your own uploads
- Nothing to unpick before you can edit it
What changed Three things moved this month, and one of them is the reason the dashboard now loads before you finish reading this sentence. Three things moved this month… A faster dashboard New reports Fewer clicks The best release yet.
<!-- wp:paragraph -->ParagraphThree things moved this month, and one of them is the reason the dashboard now loads before you finish reading this sentence.
Three things moved this month…
- A faster dashboard
- New reports
- Fewer clicks
The best release yet.

Write in Markdown mode and headings, lists and quotes become blocks of their own.










Up to 10 per post
Your images land in your media library, not on a link.
A post whose pictures are served from somewhere else is a post with an expiry date. Everything you attach is uploaded to your own site instead, sits at the end of the post at its own proportions, and is yours to reuse afterwards.
Uploaded, not linkedEvery image is uploaded to your own site, so the post keeps working whatever happens to the original afterwards — and you can reuse them there like any other upload.
It goes live at the minute you pick.
Posts are not left as drafts. They publish on your site at the time you set, the same as every other channel on your calendar.
Keep the blog from going quiet
A feed trigger, a Generate text step and a Publish to WordPress step are enough to turn every release into a write-up on your site — tested step by step before you set it live.
See WorkflowsOne draft, the post and its announcement.
The long version goes to your site, the short version to X, LinkedIn and Facebook — each under its own limit, each at the minute you choose. Writing the article and telling people about it stop being two separate jobs.
What changed in the 3.0 release
Tue, 09:00A post, with a post's rules.
These follow from how WordPress itself works — worth knowing before you plan a series around it.
Colophon
- Publishing surface
- Posts on your own site
- Title
- Optional, 200 characters
- Body
- Paragraph blocks, editable after
- Status
- Published at the minute you pick
- Images
- Up to 10, into your media library
- Sign-in
- An application password from your profile
Check before you connect
- Your site opens over https
- The REST API is switched on
- No plugin strips the Authorization header
Two things worth checking before you connect: the site has to be reachable over https, and a security plugin that strips the Authorization header or switches the REST API off will turn the connection down.
Behind extra protection? Create an application password yourself and paste it in.
Before you connect
Any WordPress site you can reach over https and sign in to, self-hosted or otherwise. It talks to the REST API that ships with WordPress itself, so there is nothing to install. On WordPress.com, application passwords are available on the plans that allow plugins.
An application password, which WordPress creates for us and which you can revoke on its own at any time under Users → Profile. It is not your login password, and revoking it locks us out without changing anything else about your account.
They publish at the minute you schedule them, the same as every other channel on the calendar.
They are uploaded into your own media library and placed at the end of the post, each at its own proportions. Nothing is hotlinked from us, so the post keeps working whatever happens to the original file afterwards.
Yes. The body arrives as ordinary WordPress blocks rather than one opaque lump, so a scheduled post opens in the editor exactly like one written there.
Usually. Some plugins strip the Authorization header or switch the REST API off, and Ocoya says so plainly rather than failing silently. If wp-admin is behind extra protection there is a manual path, where you create the application password yourself and paste it in.

Your next post, already scheduled.
Connect WordPress and queue one in a minute.











Answer the comments without opening WordPress.
Comments on your posts show up in the Inbox. Reply from there, and approve the ones your site is holding back if your role on the site allows it.
Comments are checked while the Inbox is open.
Love the new dashboard.
Thanks, Sam! More coming next week.
Sent from Ocoya