The /dr-publish Command — From Approved Draft to Live Content
How /dr-publish adapts content for each target platform, runs pre-publish checks, and produces ready-to-send payloads — without reformatting by hand.
Getting a piece of content live is not just copying text into a compose box. Each platform has different length limits, formatting rules, and link-handling conventions. /dr-publish handles that translation layer so the same approved content reaches every target correctly.
The command reads the file path provided and first checks whether the content has gone through /dr-edit. If it hasn't, a warning appears before proceeding. Then the command asks which platforms to publish to — Telegram, LinkedIn, Facebook, X/Twitter, VK, Instagram, or a website or blog.
Platform adaptation
For each target platform, the content gets formatted according to that platform's rules. Telegram uses plain UTF-8 text by default; when Markdown formatting is needed, all special characters are escaped correctly before sending. LinkedIn and X receive plain text. Websites get an OG tag check, meta description, canonical URL, and heading hierarchy review before anything is written to the file.
Length is checked against hard platform limits before the formatted version is presented. Telegram text-only posts have a 4096 UTF-16 unit ceiling; photo captions are limited to 1024 units. Content that exceeds limits gets explicit split-points inserted at logical breaks — between sections or before code blocks — rather than cut at an arbitrary character position. Each adapted version is presented for approval before any action is taken.
Pre-publish checklist
Before a platform version is considered ready, six items are checked: text within limits, formatting renders without raw markup showing, links are valid and clickable, images are sized for the platform, OG tags are present for websites, and for Telegram a test send to a private chat is recommended. A checklist is shown with pass/fail status for each item.
One specific case worth noting: links in social posts belong in the first comment, not in the post body. The command knows this convention and structures the output accordingly — the post body ends on a content beat, and a separate block is labelled for the first-comment publication.
What gets produced
For Telegram, the output is a ready Bot API payload — a formatted sendMessage or sendPhoto call. For websites, the content is applied directly to the target file and the sitemap or RSS feed is updated if applicable. For other platforms, the output is formatted text ready to paste, with platform-specific notes on what to do next.
After all platforms are published, the command notes the publication date for the content record. The recommended next step in a Datarim pipeline is /dr-archive to close the task.
Where it fits
/dr-publish is the last active step in the content track. Content that hasn't been editorially reviewed should go through /dr-edit first. Content that doesn't exist yet starts at /dr-write.
See what Datarim is for the full pipeline, or read about the /dr-edit command that precedes this step.