Skip to content

Content team playbook

You own the words. This playbook covers drafting posts and pages, staging content in the shared GitHub inbox, and driving QueryMind’s content pipeline — all as drafts, never publish-now.

  • Draft, edit, schedule and unschedule blog posts (WordPress + Duda).
  • Draft pages — Gutenberg, Elementor (from a template), or code-first (raw HTML/CSS/JS).
  • Use the GitHub markdown inbox as a shared handoff with the design team.
  • Upload media and manage tags / categories.
  • Run QueryMind content jobs — read outputs, and (if enabled) create or re-run jobs that generate full drafts.
  1. A token scoped to your sites.
  2. For pages on WordPress: know the site’s builder (Gutenberg / Elementor / code-first). Elementor needs a template id + variables.
  3. For the GitHub inbox: the site has github_repo / github_branch / github_path_prefix configured.
  4. For QueryMind: the site is linked to a QueryMind workspace, and creating / re-running jobs needs the super-admin flag allow_querymind_write.
FeatureTools
Blog postscreate_draft, update_draft, schedule_draft, unschedule, get_post, list_drafts
Pagescreate_page_draft, update_page_draft, schedule_page, list_builders_for_site, list_page_templates
Duda pagesduplicate_page, inject_page_section
Code-first pagescreate_page_from_code, update_page_from_code
Media & taxonomyupload_media, list_taxonomies, create_taxonomy
GitHub markdown inboxsave_md_to_github, list_md_from_github, read_md_from_github, deploy_md_to_site, update_md_status
QueryMind jobs (read)querymind_list_content_jobs, querymind_get_content_job, querymind_get_content_job_output, querymind_list_content_types
QueryMind jobs (write, gated)querymind_create_content_job, querymind_rerun_job
On "acme-blog", draft a 900-word post titled "How much does ceramic coating
cost in 2026?" with H2 sections, an intro, and a FAQ. Add the tag "ceramic
coating". Keep it a draft — don't schedule.

Claude calls create_draft (and create_taxonomy if the tag is new).