developersteve / block-four-oh-four Goto Github PK

In the block.json you've set the template to:

{
  "@type": "404",
  "head": "This is not the 404",
  "subhead": "You are looking for",
  "image": "image.png"
}

Blockify uses the JSON-LD structure with Schema.org,
In you're code above you set the @type to 404, this isn't a valid Schema.org Type.
In this case a simple Thing has all the properties shown above:

{
  "@type": "Thing",
  "name": "This is not the 404",
  "description": "You are looking for",
  "image": "image.png"
}

By default, Blockify makes any object a Thing, so it's not necessary to state: "@type": "Thing"

If you're wanting to add your own properties that Schema doesn't specify, you can use the Extension Mechanism.

There are a bunch of helpful types already on Schema.org such as: WebPage, WPHeader and EmailMessage. So it's worth checking the Schema.org Type Hierarchy before defining your own.

Now here's why this is helpful, say you have some data in the Schema.org structure, for example a LocalBusiness, you can easily provide this to any block that supports the LocalBusiness structure, without needing to manipulate the data on a per block basis. So once we have a bunch helpful functions to help integrate Blockify/Schema.org with other applications such as WordPress, you can use any suitable block with minimal effort.

Hope this helps :)