Match the project, collection and key
Use the Framer editor project URL and that project's Server API key. Discover the article collection, then check the title, formatted body, summary and image mappings. Optional date, author and search metadata mappings should match fields used by your template.
A key from another project or a collection with different fields will not describe the blog visitors see. Confirm the actual project and article collection before enabling delivery.
Preserve your article design and address
Set the article URL prefix to the current CMS detail-page path. Keep existing post URLs, and check category and visibility settings if the listing filters posts into sections such as Featured or Latest.
Field mapping is only useful when the template renders the selected fields. Inspect both a public listing item and its article page after delivery. Read existing posts through Connections to inventory the content already in the project.
Plan around Framer project changes
Publishing waits while the Framer project has other unpublished changes. Resolve those changes in Framer before retrying article delivery, so a content action does not inadvertently publish unrelated design work.
Choose review mode while testing the first articles and confirm the final public result. If you prefer to keep the blog separate from the Framer CMS, a managed blog on your own subdomain is another supported route.
Common questions
- Will this redesign my Framer website?
- The connection publishes content through your chosen collection and mappings. Your Framer templates control the design and need to display the mapped article fields.
- Why might an article wait to publish?
- Check for unrelated unpublished project changes, the project key, field mappings and the article's status. The Framer guide explains the setup and retry checks.