Site settings

Some themes, such as Astro Modular and Axis, mark each setting in their src/config.ts with a comment:

export const siteConfig = {
  // [CONFIG:SITE_TITLE]
  title: 'My site',
  // [CONFIG:HIDE_SCROLL_BAR]
  hideScrollBar: false,
};

When your project has these markers, Settings > Site shows each marked setting as a field: a switch for true or false, a number field, a text field, or a menu of choices. Zeku writes each change straight back to src/config.ts, keeping your formatting and quote style, and changes nothing else in the file.

A theme can describe its settings further in a config.settings.yaml next to the config, with a title, description, control type, and choices for each key. Zeku then lists the settings in the file’s order, under its group headings, as the Astro Theme Settings plugin for Obsidian does, followed by any marked setting the file leaves out. Every setting the file lists shows in the form. Settings it marks as advanced, such as Coffer’s font loading, appear once you turn on Show advanced settings at the bottom of the form. Edit as source, below that, opens the config file itself.

Note

Site settings live in your theme’s config, never in .zeku. A project without markers has no Site tab, and its config files open as source.

On a site built on Axis, Coffer, or Astro Modular, Settings > Site also checks for new versions of the theme and updates it, carrying your settings across. See Theme updates.

Open config files

These commands open a config file in the editor, from the command palette:

Command	Opens
Open site config	Your theme’s config, such as src/config.ts
Open Astro config	astro.config.mjs (Ctrl+Shift+,)
Open content collections config	src/content.config.ts