Skip to content

.sek.yml reference

The exhaustive reference entry for .sek.yml. For the narrative walkthrough (what the file does, how it’s discovered, and how the Config Editor can bootstrap one), see The .sek.yml theme opt-in.

Key Required Points at Default
postTypes Yes A directory of post-type config YAML files, one per post type. None: the CLI’s resolveConfig() throws if the key is missing.
sections Yes A directory ConfigLoader scans recursively for section type YAML files. None: same as above.

Both paths are resolved relative to the theme root: the directory .sek.yml itself lives in. There is no third key: no version field, no feature toggles, no per-post-type entry.

That “no per-post-type entry” is scoped to this file only: .sek.yml’s opt-in is theme-level and binary. Per-post-type takeover of the edit screen is governed separately: SEK replaces the native editor for a post type only when a config resolves for it (a matching file under postTypes, or the main.yaml catch-all). See Post-type configs for how that resolution works.

Both the plugin and the sek CLI find .sek.yml by searching upward from a working directory through parent directories until they find it, or reach the filesystem root (a “no .sek.yml found” error). Every path a consumer then resolves is relative to the directory .sek.yml was found in (the theme root), not the working directory the search started from.