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.
Content library and CMS
Drafts, published, scheduled and repurposed, all in one place, plus a lightweight CMS for everything that is live on your website. Search it, edit it, publish it.
Not the same thing as the knowledge base
Brand strategy, tone of voice and hard rules, loaded before every single agent run. It's the spine every piece of output has to agree with.
Drafts, published pieces, notes and transcripts - a CMS and DAM in one place, where anything can be opened, edited or repurposed with a click.
Every output from every agent lands here: blog drafts, LinkedIn posts, newsletters, press releases, transcripts, repurposed variants. Structured around what you actually do - review, mark ready, schedule, track what published where.
Send a blog into the social writer. Push a transcript into the newsletter writer. Hand a draft to the assistant for a brand-alignment pass. Every piece carries its context with it.
See every post on your website, write or paste new ones, set the SEO fields yourself and publish, unpublish or delete them without logging in anywhere else.
Built-in CMS
A site built with Claude, Astro or v0 goes live in a weekend. Then someone asks where the blog gets edited, and the answer is usually a code editor. Connect the site to Contengi and the CMS lists every post on it, so you write, fix and publish from the same app that wrote the content in the first place, with less tabs open.
Start a blank post and write in the editor, or paste in a draft you already have and keep going from there.
Set the URL slug, SEO title, meta description, excerpt and featured image yourself. The character counts flag anything Google will cut off.
Ask it to tighten an intro or add an FAQ and it changes that section only, in your brand voice, and leaves the rest of the post exactly as it was.
Push a post live, pull it back to draft so its URL stops resolving, or delete it for good. Deleting asks you to type it out first, because that one does not come back.
Rename a live post and Contengi checks the new slug against your other posts and your sitemap, then reminds you to redirect the old address.
Every CMS post is reachable over the Claude connector, so your Claude can read a live post, edit it and leave it waiting for you to publish.
Works with your own Claude too
One of the biggest problems with working in an LLM directly is that there is nowhere organised to save and edit what it makes - everything lives in a chat window that forgets the moment you close it. Connect Contengi to Claude and every draft it writes lands in the library instead, structured, searchable and ready to open in the CMS. Claude can pick up a live post from there too, edit one section and leave the publishing to you.
Feature demo
0:50
Content Library
Find, preview, and repurpose everything you have made.
FAQ
Yes. The CMS sits in the library and lists every blog post on your connected website, with what is live, what is still a draft and which posts have changes waiting to go out. You write, edit, publish, unpublish and delete from there. The workspace owner switches it on in Settings.
Custom websites connect through a signed webhook and static sites through a pull feed, which covers sites built with Claude, Astro or v0. WordPress and Shopify posts can be browsed and edited in place too. Unpublish and delete work on custom websites and pull feeds, WordPress and Shopify keep those in their own admin.
Yes. Change the slug and Contengi checks it against your other posts and your sitemap before publishing, takes the old address down and publishes at the new one. Contengi does not manage redirects, so set one up on your site for the old URL.
Yes. Blog drafts, social posts, newsletters, press releases and transcripts all land here the moment an agent finishes, ready to review.
Yes. Connect your website once and a blog draft goes live from the library or the CMS in a couple of clicks, at the same URL every time you update it.
Each integration shows a last-published timestamp and surfaces any errors directly, so you always know what went where and when.
Yes. Send a blog into the social writer, push a transcript into the newsletter writer, or hand a draft to the assistant for a brand-alignment pass - the context travels with it.
Keep exploring