A plain-text version of this site for AI assistants is at https://contengi.com/llms.txt, with the full product documentation in one file at https://contengi.com/llms-full.txt. Every page is also available as markdown by adding .md to its URL.
Framer integration
Paste a project API key and Contengi puts an agent directly on your Framer blog. It reads the items in your CMS collection, writes new ones in your voice, edits the old ones and publishes back to the same URL, without touching the design you are still working on.
Read, write, publish, edit, republish
The CMS lists the items in your blog collection, newest first, with what is live and what is a draft. Open any of them, including posts you wrote in Framer, and the agent works from the real formatted text.
Content library and CMSThe SEO agent researches the keyword, reads your knowledge base and hard rules, and drafts the post. Four slop filters run before you ever see it.
Content agentsPosts become items in the collection you choose, with the body, summary, featured image, SEO title, meta description and date in the fields you mapped. Add them to the CMS, publish the site with them, or keep them as drafts.
Content library and CMSAsk the edit agent to tighten an intro, add a section or fix a stat. It changes only what you asked for, checks the links and shows you a diff you can revert.
Content library and CMSAn edited or refreshed post goes back over the original. If Contengi cannot find that original, the publish stops, so a second copy never appears at a new address.
Content agentsConnect Contengi to Claude and the same blog is one chat away. Claude can open a live post, edit it section by section and leave it waiting for you to publish.
Claude connectorUnder the hood
Framer sites are designed by hand, so Contengi never touches the canvas. It writes into your CMS collection and only publishes the site when you ask it to and nothing else is waiting to go live.
FAQ
No. By default a post goes into your CMS and goes live the next time you publish in Framer. If you let Contengi publish the site, it first checks for other pages with unpublished changes. If there are any, it saves the post, skips the site publish and tells you which pages are waiting.
Yes. Posts live on the CMS page for your collection, such as /blog/:slug. Without one, posts are saved in the CMS but have no address. Test tells you if the page is missing.
Yes. Set the connection to draft and new posts wait in the CMS as drafts. An edit to a post that is already live keeps it live.
No. An edit updates the same CMS item and never changes its slug, so a published address cannot move by accident.
Keep exploring