How the Admin Agent works

By

The Admin Agent turns structured YAML into a live WordPress site — pages, menus, reading settings, and blog posts — without manual wp-admin work.

Declarative content

Content lives in opsforge-site-spec.yaml at the repo root. Each page has a slug, title, and HTML body. The same file declares the menu, front page, posts page, and blog posts under top-level pages, posts, menu, and reading keys.

Apply workflow

  1. Edit the site spec (or ask the Dev Agent to do it)
  2. Run ./scripts/opsforge-admin-agent.sh apply on the VM
  3. Bootstrap creates or updates posts/pages idempotently by slug
  4. Menu is rebuilt; front page and blog settings are synced

Why YAML instead of clicking

Version control, review, and repeatability. Agencies can maintain one spec per client. Teams can diff copy changes like code. And agents can propose updates from Telegram or Cursor — then apply in one command.

This post itself was published by the Admin Agent from that same spec. See the platform →

Similar Posts