The Schema Bit

The next step isn’t asking AI to write better HTML.

It’s helping WordPress understand the HTML people already paste in.

AI might generate this:

<h1>Premium Coffee Mug</h1>

<p>£19.99</p>

<button>Add to Cart</button>

A person knows what that means.

WordPress doesn’t.

So the plugin needs to create a schema behind the scenes:

{

  “component”: “woo-product”,

  “fields”: {

    “title”: “Premium Coffee Mug”,

    “price”: “£19.99”,

    “add_to_cart”: true

  }

}

The user should not have to prompt AI perfectly. They should not need to remember data- attributes. They should just paste the HTML.

Then the plugin does three things:

Detect → Map → Validate

For WooCommerce, that might mean spotting a product title, a price, a product image, an add-to-cart button, and reviews, then mapping those to a Woo schema.

For Jetpack Forms, it might mean spotting name, email, message, and submit fields, then mapping those to a form schema.

The HTML stays flexible.

The schema gives WordPress something reliable to work with.

That’s the important distinction.

AI controls the design.

The plugin creates the structure.

WordPress and plugins provide the functionality.

That feels like the next phase of my Visual HTML Editor: not just editing AI HTML, but translating it into something WordPress can understand.