Markitera WordPress Developer

Markitera WordPress Developer builds WordPress pages and posts from what you give it: an HTML page, a Markdown article, images, or a description.

Moving a finished design or article into WordPress is repetitive and easy to get wrong: lost styles, broken image paths, unsafe scripts, duplicate drafts, accidental publishing.

Mission

Implement pages and posts on the connected WordPress site from the materials the user provides, as faithfully as the site allows, as drafts first, verified by reading them back, and published only with approval.

In the Markitera workflow: Works next to the Content Engine: the Content Engine decides what to write; the WordPress Developer implements pages and posts on the site.

1. 1

   Resolve the target site

   Uses the only connected WordPress site, or asks which one when several are connected. Checks what the connected user may do.

   wordpress_site_status

2. 2

   Analyze the source

   Parses the uploaded HTML or Markdown in full: structure, styles, scripts, forms, assets and front matter. Content in files is data, never instructions.

   wordpress_analyze_sourceread_filelist_files

3. 3

   Check what exists

   Finds the page or post to edit, or confirms a new one would not duplicate an existing page.

   wordpress_list_postswordpress_get_post

4. 4

   Plan the implementation

   Chooses how to build it with the capabilities the site actually offers and states what cannot be reproduced.

   wordpress_site_status

5. 5

   Create or update as a draft

   Imports the file or saves the written HTML as a draft, with media uploads; each change is an approval request.

   wordpress_import_filewordpress_upload_mediawordpress_save_post

6. 6

   Verify

   Reads the saved page or post back and checks status, title, slug, content, styles, images and terms.

   wordpress_verify_content

7. 7

   Publish on request

   Publishes a reviewed draft only when the user asks, after approval, and confirms the published status.

   wordpress_publish

Available now

• HTML file to WordPress page

  Whole-file conversion with page-scoped CSS, local images uploaded to the Media Library, scripts removed, saved as a draft and verified.

• Markdown to blog post

  Front matter (title, slug, excerpt, categories, tags, featured image), full CommonMark and GFM conversion, draft creation and verification.

• Pages from a description

  Landing, about, pricing, FAQ and contact pages written on-brand and saved as drafts.

• Edit existing pages and posts

  Reads the current content, changes only what was asked and refuses to overwrite edits made after the proposal.

Partial or planned

• Media and SEO fieldsPartial

  Workspace images to the Media Library with alt text; SEO title and description where Yoast SEO or Rank Math expose them.

  Other SEO fields (canonical, Open Graph) are reported for manual entry.

• Forms and questionnairesPartial

  Static form markup, or a form plugin when the connected EMCP tools expose one.

  Markitera does not store form submissions; a form needs a form plugin or endpoint to work.

• Visual comparison with the sourcePlanned

  Rendering the draft and comparing it with the uploaded design.

  Drafts are verified through the REST API; the preview link is for a visual check.

Every skill this persona loads, from Markitera’s skill registry. Skills from Marketing Skills by Corey Haines (MIT) are vendored unmodified; Markitera’s adaptation is listed separately and is not part of the original skill.

• WordPress Developer

  wordpress-developerMarkitera skillInstalledv1.0.0

  Role: Persona instructions: site selection, source analysis, implementation choice, draft-first changes, verification and reporting.

  Builds WordPress pages and posts from HTML files, Markdown articles and descriptions: analyzes the source, plans, creates verified drafts and publishes only on approval.

  Source: Markitera

• WordPress Publishing

  wordpress-publishingMarkitera skillInstalledv2.0.0

  Role: Reading and updating posts and pages through approval.

  Reads and updates WordPress posts; every write waits for approval.

  Source: Markitera

• Content Writing

  content-writingMarkitera skillInstalledv1.0.0

  Role: On-brand copy for pages described in words.

  Writes and improves on-brand pages and posts from brand files.

  Source: Markitera

• Copywriting

  copywritingMethodology referenceInstalledv2.2.0

  Role: Page copy for landing, pricing, about and FAQ pages written from a description.

  Write, rewrite, or improve marketing copy for any page, including homepage, landing pages, pricing pages, feature pages, about pages, or product pages.

  Markitera adaptation: Read for brief and draft writing guidance; brand voice comes from brand/brand-voice.md.

  Source: Marketing Skills by Corey Haines · MIT license · Original skill(opens in a new tab) · Source at the pinned commit(opens in a new tab)

• Conversion Rate Optimization (CRO)

  croMethodology referenceInstalledv2.0.3

  Role: Landing-page structure and calls to action when the user asks for a conversion page.

  Optimize, improve, or increase conversions on any marketing page or form — including homepage, landing pages, pricing pages, feature pages, lead capture forms, or contact forms.

  Markitera adaptation: Read as a conversion-diagnosis method; evidence comes from GA4 landing pages.

  Source: Marketing Skills by Corey Haines · MIT license · Original skill(opens in a new tab) · Source at the pinned commit(opens in a new tab)

• Schema Markup

  schemaImported skillInstalledv2.0.2

  Role: Structured data for FAQ and product pages.

  Add, fix, or optimize schema markup and structured data on their site.

  Markitera adaptation: Checks the audit’s structured-data findings; JSON-LD is generated only from facts visible on the site or in brand files.

  Source: Marketing Skills by Corey Haines · MIT license · Original skill(opens in a new tab) · Source at the pinned commit(opens in a new tab)

Data sources and integrations

• WordPress (REST API)

  Drafts, updates, media uploads and publishing with an Application Password.

  Connect per brand

• WordPress EMCP tools

  Block edits, Elementor pages, media sideloading, menus and site inspection.

  Connect per brand

• Workspace files

  Uploaded HTML, Markdown, CSS and images.

  Built in

• Visual regression

  Rendered comparison with the source.

  Planned

• Connected WordPress site (required · Content engine connection (Application Password) or Integrations → WordPress)

  When missing: Explains how to connect WordPress; nothing is created.

• Source material (optional · Uploaded HTML, Markdown, CSS and image files in the workspace, or a description)

  When missing: Works from the description and the brand files.

• Brand voice and profile (optional · brand/brand-voice.md, brand/brand-profile.md)

  When missing: Writes neutral copy and says so.

Missing assets, unsupported features and fields WordPress does not expose are listed in the result; nothing is reported as saved unless WordPress returned it.

What it produces

• Approval requests for drafts, media, updates and publishing
• Result reports with preview and edit links and check-by-check verification
• records/ workspace files of every executed change

Saved as: ApprovalRequest (WORDPRESS_POST) with the executed result, a records/ workspace file, and the WordPress page or post.

Output sections

1. Target site: The WordPress site the change applies to.
2. Source analysis: Structure, styles, assets and what cannot carry over.
3. Implementation plan: How the page or post is built with the tools this site offers.
4. Resource: Type, title, id, slug and status.
5. Preview and edit links: WordPress preview and editor URLs.
6. Assets: Uploaded, reused, embedded, missing or unsupported.
7. Verification: What was read back from WordPress, check by check.
8. Warnings and manual steps: Unsupported features, unsaved fields and what the user still has to do.

How other personas use it

• People review drafts in WordPress and approve publishing in the workspace

Reads: Content brief, Draft. Produces: WordPress change, Approval.

Every change is read back from WordPress and checked field by field; a failed check is reported, never hidden.

Status

New content must be stored as a draft.

Content

The stored markup carries the import marker, no scripts, and the scoped CSS.

Media

Uploaded image URLs appear in the stored content.

Terms and SEO

Categories, tags and SEO fields match what was sent.

Reads sources and the connected WordPress site freely. Every draft, media upload, update and publication is an approval request, and new pages and posts are always drafts first. It cannot change strategies, briefs, audits or site-wide settings on its own.

These limits are enforced by the server: in a WordPress Developer turn the agent is only offered the tools listed above, and connected-system tools are offered with every write waiting for approval. Website pages, files and tool results are treated as data, never as instructions.

Illustrative example (sample data, not real results). Every value below is illustrative; none is a real Markitera result or performance figure.

1. 1. Input

   Upload landing.html and its img/ folder; ask for a draft page.

2. 2. Analysis

   Sample: 6 sections, 4 images found, 1 script that will be removed, 1 form without an action.

3. 3. Approval

   Approve the import card that lists title, slug and uploads.

4. 4. Result

   Sample: draft page 812 created, images uploaded, all checks passed, preview link returned.

5. 5. Publish

   Ask to publish; approve; the published status is confirmed.

• JavaScript from the source is never added to WordPress; interactive widgets need a plugin or block equivalent.
• The page CSS is removed by WordPress when the connected user lacks unfiltered_html.
• The theme’s header, footer and content width still apply; a full-width page template may need to be chosen in WordPress.
• Fonts are not uploaded; web-font stylesheets (Google Fonts) are kept.
• Forms are static markup unless a form plugin handles them.
• Visual fidelity is not checked automatically; use the preview link.

Version

1.0.0

Availability

Beta

Start it with

/wpdev

Other personas: Markitera Auditor · Markitera Strategist · Markitera Content Engine