External platforms require publicly accessible absolute URLs (https://...). If your markdown contains ./assets/img.png, pass --base-url when publishing:

zyvop publish post.md --base-url "https://myblog.dev/posts/distributed-systems"

Alternatively, ensure your frontmatter defines canonical_url: "https://myblog.dev/posts/distributed-systems", which ZyVOP uses to automatically infer the base URL origin.

DEV.to's Liquid template parser crashes if an article series title contains round parentheses ( or ). ZyVOP automatically replaces () with square brackets [] in series titles. If you manually embed raw Liquid tags (e.g. {% ... %}), escape them or wrap them in code blocks.

The official Medium REST API does not support editing published posts. When you run zyvop publish on an existing post, ZyVOP updates your DEV.to, Hashnode, and WordPress copies, but logs a notice that Medium must be edited manually in the Medium web editor.

Hashnode requires every post to belong to a publication. Log in to Hashnode, ensure you have created a blog (e.g. yourname.hashnode.dev or a custom domain), and generate a Personal Access Token with read/write access.

Ensure you are using an App Password created in Bluesky Settings → App Passwords, NOT your primary master password. Your identifier should be your complete handle including .bsky.social (e.g. alice.bsky.social).

The ZyVOP Developer API limits requests to 10 requests per minute per developer token. In CI/CD pipelines publishing batch posts, add a 6-second sleep between requests or implement exponential backoff checking the Retry-After response header.