Configuration on Emet CMS

Site config

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

admin/site.yaml describes your site to Emet: where the content is, what fields each kind of entry has, which shortcodes exist, where uploaded images go and which branches matter. It’s the file the setup wizard writes, and the one you’ll edit most as the site changes shape.

Everything in here is about the site rather than about how you like to work; preferences live in cms.yaml. Note that Emet only reads particular keys from each file, so editor settings in site.yaml do nothing, and neither do preview.styles in cms.yaml.

CMS config

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

admin/cms.yaml is optional. It holds the settings that are about how Emet behaves rather than how your site is built: which editor opens by default, what the link dialog offers, which SEO rules count, the AI providers, whether entries need review and where the local Hugo server is. Delete the file and everything falls back to defaults, with one exception: AI features are off entirely until this file has an ai: block.

Sections

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

A section is a folder of content whose entries share a set of frontmatter fields: posts, pages, projects, docs. The sections block of site.yaml is where you tell Emet which folders those are and what the form for each one should look like. The sidebar lists the sections, the entry list shows what’s in the one you pick, and the frontmatter panel is built from its fields.

A section#

sections:
  blog:
    label: Blog posts
    label_singular: Blog post
    folder: content/blog
    slug: "{{year}}/{{slug}}"
    fields:
      - name: title
        type: string
        required: true
      - name: date
        type: datetime
      - name: tags
        type: list
    body:
      shortcodes: true

The key (blog here) identifies the section. It’s also the default folder and label, so blog: {} is a valid section: Emet will look in content/blog, call it “blog” and show no configured fields. You’d still be able to edit entries, because frontmatter keys that aren’t in the config are shown anyway (see Entries), but you’d lose the type-appropriate widgets.

Media

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

The media block says where uploaded files go in the repository and what URL they’ll have on the site. Everything that puts a file in your repository uses it: the media library, images pasted or dropped into the editor, image fields and AI-generated images.

media:
  folder: static/images
  public_path: /images
  max_size_mb: 10
  accept:
    - image/png
    - image/jpeg
    - image/webp
    - image/gif
    - image/svg+xml

Key	What it does	Default
`folder`	Where uploads are committed, relative to the Hugo root. Prefixed with `base_path` if you have one.	`static/images`
`public_path`	The URL prefix for those files on the built site. This is what gets written into your Markdown and frontmatter.	`/images`
`max_size_mb`	Upload size limit in megabytes.	`10`
`accept`	Which files are allowed.	the five image types above

The whole block is optional, as is each key in it.

Data browsing

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

Hugo’s data/ directory doesn’t need any configuration. There’s always a Data entry at the bottom of the sidebar, and it browses every .json, .yaml, .yml and .toml file under data/, nested folders included. You can create files and folders from there too, even if the directory doesn’t exist yet. New files default to YAML, with JSON and TOML a click away.

If you’ve set base_path, the browser uses that site’s data/ directory (docs/data/ for a site in docs/) and won’t let you wander outside it.

Languages

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

Hugo does multilingual sites either by giving each language its own content directory (content/en and content/de, or content for the default language and content.de for the other) or by keeping every language in one directory and putting the language code in the filename (post.md, post.de.md). Emet needs the same mapping so it can switch between them, find an entry’s translations and work out URLs.

languages:
  - code: en
    name: English
    contentDir: content/en
    default: true
  - code: de
    name: Deutsch
    contentDir: content/de

Key	What it does
`code`	The language code, as in your Hugo config.
`name`	What the language switcher calls it.
`contentDir`	That language’s content directory, relative to the Hugo root.
`default`	`true` on exactly one language. If none is marked, the first in the list is the default.

Leave the block out and Emet assumes a single language, en, in content. The language switcher only appears once there are two or more.

Environment variables

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

Everything about your site is in admin/site.yaml and admin/cms.yaml. Environment variables are for the things that belong to a deployment of Emet rather than to a site: which GitHub App it signs in with, where its API proxy is, and the secrets that proxy needs.

There are two kinds. Build-time variables are read by Vite and baked into the JavaScript bundle, so changing one means rebuilding. Runtime variables are read by the Cloudflare Pages Functions on each request, never reach the browser, and can be changed without a rebuild. Secrets go in the second group.