wordpress-publisher
**Target audience:** marketing operators and content publishers who own one or more WordPress sites and ship markdown from a vault or static-site source.
Nodig
- file_path — Path to markdown file with YAML frontmatter
- env — Target environment (dev|staging|prod), default dev
- file_path — Path to markdown file already published in source env
- from_env — Source environment (dev|staging)
- to_env — Target environment (staging|prod)
- phrase — Safety confirmation phrase; required when to_env=prod (must be APPROVED)
- post_id — WordPress post ID to fetch
- site — Site domain matching a _site-config.md entry
- env — Source environment (dev|staging|prod), default dev
- folder — Path to folder containing markdown files
- file_path — Path to markdown file with wp_post_id in frontmatter
- mode — trash (recoverable) or delete (permanent), default trash
- config_path — Path to _site-config.md (or any file inside the site folder)
- env — Environment name, default dev
Zo vraag je het
- publish to WordPress
- push to WP
- promote to prod
- sync wp posts
- _site-config.md.
- publish to WP
- push to WordPress
- promote to prod
Oplevert
- Determined by site content folder structure
- OK/FAILED message
- OK/FAILED message` — register-meta-result (text)
- deleted-post (yaml)
- environments.{env}.wp_post_id, wp_url, wp_status, last_published, external_id
- environments.{env}.wp_status (trash|deleted), sync_state (deleted)
- environments.{to_env}.wp_post_id, wp_url, wp_status
- promoted-post (yaml)
- published-post (yaml)
- pulled-post (markdown)
- succeeded/failed/skipped counts per file
- succeeded/failed/skipped counts per file` — tree-report (text)
Niveauintermediate
Invoerurl
Uitvoerdocument
Vereist[config]
Rollen[Head of Marketing, Content Manager]