Framer
Connect your Framer project and choose the CMS collection for your articles. Hoxigen uploads cover and inline images, then publishes the site.
What connecting it does
Hoxigen connects to the main Framer project with a project API key you create in your own settings. Verify lists editable user-managed collections with CMS detail pages and stores no connection.
Save validates your field choices again and adds or reuses a plain-text Hoxigen ID field for safe retries. New articles are created as drafts, their remote IDs are recorded, and the same items are then published through the Server API.
Publication rebuilds the whole project. It can include other unpublished changes, so keep the project ready to publish. Hoxigen waits for the deployment to be ready and deploys that version to the production custom domain when one is configured.
What it needs from you
The same steps the connect screen walks you through, so you can see the whole of it before you sign up for anything.
- 1Prepare your article page
In Framer, create an editable CMS collection with title, formatted text and image fields. Add a CMS detail page, bind its title, body and cover image, and publish the site once.
- 2Create a project API key
Open the project's Settings, then Site settings, General, API keys. Select Add, name the key Hoxigen, then Create. Copy it immediately.
- 3Verify the project
Paste the Framer project URL and API key below, then select Verify connection. Choose the article collection, its detail page and matching CMS fields.
- 4Save the connection
Review the production site and field mapping, then Save. Hoxigen adds a plain-text Hoxigen ID field for safe publication retries. Publishing rebuilds the whole project and may include other unpublished edits.
What actually gets published
Field by field, so nothing arrives as a surprise.
The title, slug and formatted-text body go into the selected collection. Your CMS detail template controls the layout and the article URL.
Cover and inline images are uploaded to Framer. The cover uses the article title as alternative text; inline image alternatives and captions remain in the body.
Map an excerpt, SEO title, SEO description and published date when your collection has those fields. Bind SEO and social-preview fields in Framer's page settings; the connector does not change your template.
What happens when an article is refreshed
Yes — the same CMS item and URL.
Hoxigen reads the selected article's CMS fields and slug, then checks that revision again before writing. A changed item is refused as a conflict.
A refresh updates the title, body and mapped metadata. It keeps the slug, original date, other fields and the existing cover when there is no replacement image, then rebuilds the site.
Framer has no verified atomic compare-and-set for this write. Avoid editing the same item during publication. If a rebuild fails after the CMS edit was saved, retry the same reviewed refresh to resume its recorded deployment. An unconfirmed CMS write needs review in Framer before trying again.
Refreshing an article rather than writing a new one is how a page that used to rank keeps ranking.
What it cannot do
You would find these out in week two anyway. Here they are in week zero.
The collection needs title, formatted-text body and image fields and a CMS detail page. Publish the site once in Framer. Managed plugin collections and branch projects are not supported.
The connector publishes the entire project, including other unpublished edits. Projects with Framer staging enabled need a production custom domain; Hoxigen does not treat a staging preview as a production publication.
Framer normalizes HTML, including captions and styles. Private site access remains in place. No newsletter sending, layout generation, relationship mapping or JSON-LD insertion is included.
Your project needs Server API access and a key with editing and publishing permission. Framer's API terms, availability and future fees apply.
Everything on this page describes what the connector does today. Found something that does not match what you see in the product? hello@hoxigen.app — we will correct the page.
How publishing works, whichever you pick
Drafts land in your queue with their images, meta description, a short FAQ and internal links. You can edit, approve or reject each one. Ignore the queue and it publishes on schedule anyway — that is the point of an autopilot. Prefer to sign off first? Set the connector to Approve first.
Connect two blogs and each gets its own article per publishing slot, written for it. Hoxigen does not syndicate one body to several sites and hope search engines pick a winner.
Each connector verifies access against the real API before you save its publishing destination. OAuth sign-in stores the login first; choosing a collection and saving finishes the connection.
A publish that fails keeps the reason on the article and tries again, up to three times. If it still fails, it stops and tells you, so you can reconnect the site and retry it.
Publishing somewhere else
- WordPress
Our own plugin turns your site into a signed receiver. Articles arrive as posts and refresh at the same permalink.
- Shopify
Publishes to your store's blog through the Admin API, on your own domain, with the product-adjacent content Shopify stores rarely get around to writing.
- Wix
Publishes to your Wix blog with an API key you generate, converting each article into Wix's own rich content format.
- Webflow
Publishes live CMS items into the blog collection you choose, mapping your existing fields instead of demanding new ones.
- Ghost
Publishes articles to your Ghost publication with a custom integration, including cover and inline images, and refreshes the same post.
- Notion
Sign in with Notion and publish formatted articles with covers to your public blog collection.
- Any site, by signed webhook
One signed HTTP POST per article to an endpoint you own. Next.js, Rails, Astro, Django, a static build — if it can receive JSON, it can receive articles.
Give it your URL. See what it drafts.
Connect Framer when you like what you read — nothing publishes before that.