AI features on Emet CMS

Providers

Mon, 01 Jan 0001 00:00:00 +0000

Emet speaks to four kinds of provider: OpenAI, Anthropic, Google Gemini and anything with an OpenAI-compatible API (Ollama, LM Studio, Groq, vLLM and so on). You configure them in admin/cms.yaml, and each person using the CMS either uses a key you’ve put in that file or adds their own in the AI Settings modal.

Turning AI on#

AI is off until cms.yaml has an ai: block. The shortest one that works is:

AI chat

Mon, 01 Jan 0001 00:00:00 +0000

The chat panel lives in the AI tab of the editor’s right column, alongside SEO and Comments. It appears whenever ai.enabled is true in cms.yaml. It’s a conversation with the model about the entry you have open, and, unlike a chat window in another tab, it can act on what it says: change the frontmatter, rewrite a paragraph, search your other posts, generate an image.

The panel#

The header shows a status dot and the active provider and model, in the form gemini · gemini-3.5-flash. Green means a provider is ready, pulsing yellow means it’s thinking and grey means there’s no key yet, with an Open settings link that takes you to the key form. The cog on the right opens the same AI Settings modal.

Inline actions

Mon, 01 Jan 0001 00:00:00 +0000

Most of the time you don’t want a conversation; you want this sentence to be shorter. Inline actions are the one-click version of AI: select some text in the visual editor, pick an action, and the selection is replaced with the result. No chat, no confirmation, and Ctrl+Z if you don’t like it.

They only exist in the visual editor. In Markdown mode you’ll want the chat panel instead.

Select some text. The small floating toolbar that appears above it has an AI button on the right, as long as a provider is configured and ready. Click it, or press Ctrl+J (Cmd+J on a Mac), and the actions menu opens below the selection. The shortcut is ai.shortcuts.inlineAction in cms.yaml if you want a different one.

Page builder

Mon, 01 Jan 0001 00:00:00 +0000

The page builder is for the blank-page problem. You describe a page (“a landing page for the new pricing tiers, with a comparison table and an FAQ”) and the model drafts the whole thing: YAML frontmatter that matches your section’s fields and a Markdown body that uses your shortcodes. You review it, tweak it and apply it to the editor.

It’s a draft, not a finished page. The useful part is that it knows your site’s vocabulary.

Image generation

Mon, 01 Jan 0001 00:00:00 +0000

Every post wants a header image and most of us don’t have one. The image generator takes a prompt, gets an image back from OpenAI or Gemini, uploads it to your media folder and drops it into the body or a frontmatter image field. There’s also an Edit with AI route for images you already have.

It needs a provider that can make images, which means OpenAI (gpt-image-2) or Gemini (gemini-3-pro-image-preview or gemini-2.5-flash-image). Anthropic can’t, and custom endpoints are never asked to. If your current provider is the wrong one, the modal says so and points you at AI Settings.

Translation

Mon, 01 Jan 0001 00:00:00 +0000

Emet’s translation workflow is built around copies: Translate on an entry card starts a translation from a copy of the source (or a blank archetype), and Create translations copies entries in bulk, each in the right place for a human to translate. No AI is involved in either.

The AI side is two separate things. You can translate a selection in place from the inline actions menu, and you can translate a whole entry, frontmatter and body, from the toolbar. Both need at least two languages in site.yaml and a provider that’s ready.

AI features on Emet CMS

Providers

Turning AI on#

AI chat

The panel#

Inline actions

Opening the menu#

Page builder

Image generation

Translation