Each question keeps its category, its short answer, and the fuller reply.
Yes. Give them your ingest address and the inbound key, or pair the two desks.
Linking · Imani Okoye · Published 25 Oct 2026, 04:23
Linking is two directions. You can push to their ingest, and they can push to yours. A pairing code does both at once when the other desk runs Bloghave.
What arrives here
An inbound story is stored as it was sent and filed by its kind. Articles join the stories. Questions join the FAQ. The byline and the original dates stay as the writer left them.
You will see “Arrived from” and their desk name on the page.
The edited page: type, pictures, outline, writer, and the stamps of time.
Delivery · Jules Hart · Published 24 Oct 2026, 20:23
The envelope is bloghave.v1. It carries the kind (article or FAQ), title, deck, HTML, outline, tags, cover, and every inline image as bytes so the other desk can keep its own copies.
The writer and the clock
Author name, role, bio, and portrait
Created time, set when the manuscript was opened
Published time, set when you send
The other desk is meant to render that HTML with the same care. This one does.
Register the desk, keep its system id, and choose that id when you send.
Linking · Jules Hart · Published 24 Oct 2026, 18:23
Each linked site has a system id, an ingest address, and a key. In Desks, register it — or pair with a code if the other side is Bloghave too.
The moment of sending
In the manuscript, choose that system id. Publish posts the piece to its ingest address with the key. The HTML, the images, the byline, and both dates go in the same envelope.
If you choose this desk’s own id, the story is published here. If you choose another, it goes there. You can send it again later to a second id.