Framer + Maintouch
Write to your Framer CMS and deploy the site, all from Maintouch.
Overview
Framer keeps blog posts in CMS collections, and nothing goes live until the whole site is published. Copying a post in means rebuilding its formatting field by field, then remembering to hit publish.
Connect Framer with your project URL and an API key. Maintouch writes each post into the collection you mapped, queues a site deploy so it goes live, and pushes title and meta fixes to items already on your site.
How it works
- 01
Add your API key
Paste your Framer project URL and an API key. Maintouch loads the project’s CMS collections.
- 02
Map your collections
Add a collection and match title, content, SEO fields, image, author and dates to its fields.
- 03
Publish from Maintouch
Publish live to deploy the site, or save the item as a draft to check in Framer first.
What you get
Site deploys handled
A live publish queues a deploy of your project. If you use a staging environment, the build is promoted to production once it is ready.
Rolled back on failure
If the deploy still fails after retries, the post moves back to scheduled in Maintouch instead of showing as published.
Authors as references
Map the author to a collection reference field and Maintouch links the right item from your authors collection.
SEO-only collections
Turn off content publishing for a collection and Maintouch only writes its title tag, meta description and schema.
Questions
Does publishing deploy my whole site?
Yes. Framer publishes a project all at once, so a live publish also ships any other changes waiting in that project.
Why am I asked to open my project?
Framer sometimes reports a project as closed. Open it in Framer once, then retry the publish.
What happens if I connect a different project?
Collections that are not in the new project are disconnected, and Maintouch tells you which ones.
