Blogging · WordPressYour 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.
The Gridlines Blog
by Maya · Published just now
What changed in the 3.0 release
Three things moved this month, and one of them is the reason the dashboard now loads before you finish reading this sentence.
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.
Give us the address
Type your site and nothing else. No API key to find, no plugin to install, no support ticket to your host.
https://yoursite.comApprove it on your own site
WordPress asks whether Ocoya may have access — on your own admin, in your own session. You click yes.
Yes, I approveThat is the connection
WordPress creates a password scoped to us and hands it back itself. Nothing is typed, nothing is pasted, your own login is never shared.
ConnectedA 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
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.
Every 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 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
<!-- wp:paragraph -->
<p>Three things moved this month…</p>
<!-- /wp:paragraph -->
A post, with a post's rules.
These follow from how WordPress itself works — worth knowing before you plan a series around it.
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.
One 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.
How publishing worksKeep 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 WorkflowsBefore 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.
Your next post, already scheduled.
Connect WordPress and queue one in a minute.