wp-content

WP Content

Core-REST CRUD skill. Owns the most common WordPress operations: write a page, list posts, update an option, register a user, query the DB read-only. Anything builder-specific (Elementor JSON, Divi shortcodes) belongs to wp-edit-design; anything plugin-specific (Yoast meta, Woo products) belongs to wp-edit-plugin.

Iron Rule

1. NEVER post `status=publish` on a brand-new draft without explicit user confirmation — drafts are reversible, publishes are user-visible. 2. NEVER call `rolepod_wp_db_query` with anything other than SELECT — write/update/delete via REST or wp-cli; the db_query path is read-only by design and the guard fires hard. 3. ALWAYS read the existing post (`post_get` or `post_list`) before `post_update` if you do not know the current content — the REST endpoint replaces fields, and overwriting an unknown post loses the live content irrecoverably.

When to use

• "Create a landing page with these sections..."
• "List the last 10 posts" / "show all pages" / "find posts containing X"
• "Update the site title to ..." / "change blogname"
• "Add a tag / category"
• "Show me all admins"
• "Query wp_options to see ..."
• Anything /wp/v2/* REST surface.

Skip when:

• The content is a builder layout (Elementor / Divi / Oxygen / Bricks) → wp-edit-design.
• The content is a plugin config (Yoast SEO meta, WooCommerce product) → wp-edit-plugin.
• The content is a custom block / plugin / theme bootstrap → wp-scaffold.

Boundary

Owns:

• rolepod_wp_post_{get,list,create,update} for posts/pages/CPTs.
• rolepod_wp_user_list.
• rolepod_wp_option_{get,set} for the WP-allowed settings surface (siteurl, blogname, etc.).
• rolepod_wp_db_query (SELECT only).
• rolepod_wp_rest_request for arbitrary /wp/v2/* calls.
• rolepod_wp_rest_dump to discover routes.

Does not own:

• Builder content (_elementor_data, Divi shortcodes, Oxygen JSON, Bricks JSON) → wp-edit-design.
• Plugin-specific writes (Yoast post meta, ACF fields, Woo products) → wp-edit-plugin.
• File writes outside the REST surface → wp-scaffold or wp-edit-design.

Return / hand off:

• User wants a layout in Elementor → wp-edit-design.
• User wants ACF custom fields on the new post → wp-edit-plugin.
• DB SELECT shows a problem worth diagnosing → wp-diagnose.

Inputs to gather

• target_id (always).
• For create: type (default posts), title, content, status (default draft).
• For update: id + the fields to change (read the post first if content is unknown).
• For list: type, optional search, status, per_page, page, orderby.
• For options: name; for set, value + confirm: true if on production.
• For rest_request: path, method, optional body/query.

Workflow

1. Pick the operation

User intent	Tool
create a page/post/cpt	rolepod_wp_post_create
update an existing one	rolepod_wp_post_get first (if unknown), then rolepod_wp_post_update
list / search / filter	rolepod_wp_post_list
list users	rolepod_wp_user_list
read site setting	rolepod_wp_option_get
write site setting	rolepod_wp_option_set (production guard fires if siteurl-matched)
arbitrary REST call	rolepod_wp_rest_request
discover what routes exist	rolepod_wp_rest_dump
read-only DB	rolepod_wp_db_query

2. Gutenberg block markup for content fields

When content is a Gutenberg-block page, use the comment-syntax block markup:

<!-- wp:paragraph -->
<p>Hello world.</p>
<!-- /wp:paragraph -->

<!-- wp:heading {"level":2} -->
<h2>Section title</h2>
<!-- /wp:heading -->

See examples/content-examples.md for non-trivial cases (group blocks, columns, cover, image with attributes).

3. Status flow

Default to status=draft on create. Promote to publish only with explicit user OK. Never set publish for the first commit of a major page (allows revision review).

4. Confirm + surface

State the operation, the id (post / user / option), and any warnings. If the response includes _links, just show the canonical link.

If a matching Rolepod agent is available

• rolepod:content-strategist (audience: user) for copy quality.
• rolepod:backend-developer for non-trivial REST orchestration.

If no matching agent is available

1. Pick the tool from the table.
2. For updates: read first, then update.
3. Default status=draft.
4. Surface the result.

Output

No durable artifact — content lives in WordPress. The MCP returns IDs + canonical links.

Examples

Read when constructing Gutenberg block markup or chaining multiple REST calls:

• examples/content-examples.md — good vs bad block markup; full landing-page composition example.

References

Inline only. REST surface is documented at https://developer.wordpress.org/rest-api/reference/. Use rolepod_wp_rest_dump to discover the current site's actual routes.

Hard stops

• db_query with non-SELECT → tool returns DB_WRITE_BLOCKED. STOP; re-route via REST or wp-cli (companion /wp-cli endpoint via wp-execute-php's sibling pattern — but cleaner: use the right REST endpoint).
• option_set on production-matched siteurl without confirm: true → STOP. Ask user for explicit confirmation, then retry with confirm: true.
• post_update without id → STOP, ask the user which post.

Full Rolepod enhancement

Full Rolepod adds bulk batching (run 20 post_create in one composite call with optimistic concurrency); standalone, batch by orchestrating individual calls.

Next phase

• After publish → wp-health-check to verify the page is reachable.
• For a builder layout pass → wp-edit-design.
• For plugin-specific writes (Yoast meta, ACF fields) → wp-edit-plugin.