Docs

Setup guides for the publishing destinations. Each one lists the exact fields the connector asks for, taken from the code rather than written from memory, what approving and unpublishing do on that platform, and what it never asks for. The product itself is open source, so the definitive answer to any “what does it actually do” question is the repository .

MCP server: drive it from an AI agent →

26 tools, a scoped REST API and a hosted endpoint for ChatGPT, Claude and Claude Code. No publish tool, on purpose.

Command line

The same readiness check runs from a terminal, from apps/web in the repository:

npm run readiness -- example.com

It checks the site, writes the missing artifacts and says where each one goes. It does not publish anything.

Be the site the assistant names.

Add a domain and the first draft is written while you watch. Every publish is your decision, a click on the draft or a rule you set and can hold, and you can read the source or self-host it free.

Add a domain, it sets up your workspace