leoloso

<p>This plugin helps convert WordPress into a manager of our digital content, to publish it in different mediums or platforms: not just the website, but also email, iOS/Android apps, home-assistants (like Amazon Alexa) and others.</p>
<p>It does this by extracting the metadata from all Gutenberg blocks inside of a blog post. Because each Gutenberg block stores its own content and properties, these ones can be extracted as metadata and exported through a JSON object, accessible through a REST API endpoint, to feed any application on any platform.</p>
<p>The plugin makes the following REST API endpoints available:</p>
<ul>
<li>/wp-json/block-metadata/v1/metadata/{POST_ID}: Extract all metadata from all Gutenberg blocks in a blog post with id {POST_ID}, converted to medium-agnostic (eg: removing all non-semantic HTML tags)</li>
<li>/wp-json/block-metadata/v1/data/{POST_ID}: Extract all data from all Gutenberg blocks in a blog post with id {POST_ID}, as originally stored in the block by Gutenberg (eg: containing HTML code)</li>
</ul>
<p>Demonstration:</p>
<ul>
<li><a href="https://nextapi.getpop.org/posts/cope-with-wordpress-post-demo-containing-plenty-of-blocks/" rel="nofollow ugc">Blog post</a></li>
<li><a href="https://nextapi.getpop.org/wp-json/block-metadata/v1/data/1499" rel="nofollow ugc">Blog post’s Gutenberg blocks</a></li>
<li><a href="https://nextapi.getpop.org/wp-json/block-metadata/v1/metadata/1499" rel="nofollow ugc">Blog post’s medium-agnostic metadata</a></li>
</ul>
<h4>How does it work?</h4>
<p>This plugin is based on the strategy called “Create Once, Publish Everywhere” (also called “COPE”), which reduces the amount of work needed to publish our content into different mediums by establishing a single source of truth for all content.</p>
<p>Having content that works everywhere is not a trivial task, since each medium will have its own requirements. For instance, whereas HTML is valid for printing content for the web, this language is not valid for an iOS/Android app; similarly, we can add classes to our HTML for the web, but these must be converted to styles for email.</p>
<p>The solution is to separate form from content: The presentation and the meaning of the content must be decoupled, and only the meaning is used as the single source of truth. The presentation can then be added in another layer, specific to the selected medium. For instance, given the following piece of HTML code, the <code><p></code> is an HTML tag which applies mostly for the web, and attribute class=”align-center” is presentation (placing an element “on the center” makes sense for a screen-based medium, but not for an audio-based one such as Amazon Alexa):</p>
<pre><code><p class="align-center">Hello world!</p>
</code></pre>
<p>Hence, this piece of content cannot be used as a single source of truth, and it must be converted into a format which separates the meaning from the presentation, such as the following piece of JSON code:</p>
<pre><code>{
  content: "Hello world!",
  placement: "center",
  type: "paragraph"
}
</code></pre>
<p>This piece of code can be used as a single source of truth for content, since from it we can recreate once again the HTML code to use for the web, and procure an appropriate format for other mediums.</p>
<h4>Supported Gutenberg blocks</h4>
<p>This plugin attempts to extract the metadata for all Gutenberg blocks shipped in WordPress core; support for additional blocks, such as from plugins, can be added through hooks. Not all Gutenberg blocks can be supported (for instance, because they may only work for the web, or only make sense when applied to screen-based mediums, among other reasons).</p>
<p>The following WordPress core blocks are currently not supported:</p>
<ul>
<li><code>"core/columns"</code></li>
<li><code>"core/column"</code></li>
<li><code>"core/cover"</code></li>
<li><code>"core/html"</code></li>
<li><code>"core/table"</code></li>
<li><code>"core/button"</code></li>
<li><code>"core/media-text"</code></li>
</ul>
<p>The following Gutenberg blocks are supported, and this plugin extracts their metadata:</p>
<ul>
<li><code>"core/paragraph"</code></li>
<li><code>"core/image"</code></li>
<li><code>"core-embed/youtube"</code> (all other <code>"core-embed"</code> blocks can also be extracted, but must be implemented through a hook)</li>
<li><code>"core/heading"</code></li>
<li><code>"core/gallery"</code></li>
<li><code>"core/list"</code></li>
<li><code>"core/audio"</code></li>
<li><code>"core/file"</code></li>
<li><code>"core/video"</code></li>
<li><code>"core/code"</code></li>
<li><code>"core/preformatted"</code></li>
<li><code>"core/quote"</code></li>
<li><code>"core/pullquote"</code></li>
<li><code>"core/verse"</code></li>
</ul>
<h4>Extracting metadata for additional blocks</h4>
<p>We can extend this plugin to extract the metadata for additional blocks, such as those shipped through plugins. To do this, simply add a hook for filter <code>"Leoloso\BlockMetadata\Metadata::blockMeta"</code> (located in function <code>get_block_metadata($block_data)</code> from class <code>Metadata</code> in file <code>block-metadata/src/Metadata.php</code>). The attributes that must be extracted must be decided on a block type by block type basis:</p>
<pre><code>add_filter("Leoloso\BlockMetadata\Metadata::blockMeta", "extract_additional_block_metadata", 10, 3);
function extract_additional_block_metadata($blockMeta, $blockName, $block)
{
  if ($blockName == "my-plugin/my-block-name") {
    return array(
      "property1" => $block["property1"],
      "property2" => $block["property2"]
    );
  }

  return $blockMeta;
}
</code></pre>
<h4>Further references</h4>
<ul>
<li><a href="https://leoloso.com/posts/my-1st-wp-plugin/" rel="nofollow ugc">Inspiration for the plugin</a></li>
<li><a href="https://slides.com/leoloso/cope-with-wp" rel="nofollow ugc">Slides from presentation “COPE with WordPress”</a> (from WordCamp Singapore 2019), explaining how the plugin works</li>
</ul>
<h4>Contributing / Reporting issues</h4>
<p>Please head over to the project’s <a href="https://github.com/leoloso/block-metadata" rel="nofollow ugc">GitHub repo</a> for contributing, reporting issues or making suggestions, and others.</p>
<p><em>Banner image <a href="https://www.freepik.com" rel="nofollow ugc">designed by Freepik</a></em></p>


Block Metadata

Extract all metadata from all Gutenberg blocks inside of a post

JS Morisset

<p>The JSM Show Order Metadata for WooCommerce HPOS plugin displays order meta keys and unserialized values in a metabox at the bottom of the WooCommerce HPOS order and WooCommerce Subscriptions editing pages.</p>
<p>Note that if you’re NOT using WooCommerce HPOS (High-Performance Order Storage), available since WooCommerce v8.2, then your WooCommerce orders are post objects and you should use the <a href="https://wordpress.org/plugins/jsm-show-post-meta/" rel="ugc">JSM Show Post Metadata</a> plugin instead.</p>
<p>There are no plugin settings – simply install and activate the plugin.</p>
<h4>Available Filters for Developers</h4>
<p>Filter the order meta shown in the metabox:</p>
<pre><code>'jsmsom_metabox_post_types' ( array $post_types )
</code></pre>
<p>Array of supported HPOS post types (i.e. ‘woocommerce_page_wc-orders’ and ‘woocommerce_page_wc-orders–shop_subscription’).</p>
<pre><code>'jsmsom_metabox_table_metadata' ( array $metadata, $order_obj )
</code></pre>
<p>Array of regular expressions to exclude meta keys:</p>
<pre><code>'jsmsom_metabox_table_exclude_keys' ( array $exclude_keys, $order_obj )
</code></pre>
<p>Capability required to show order meta:</p>
<pre><code>'jsmsom_show_metabox_capability' ( 'manage_options', $order_obj )
</code></pre>
<p>Capability required to delete order meta:</p>
<pre><code>'jsmsom_delete_meta_capability' ( 'manage_options', $order_obj )
</code></pre>
<p>Icon for the delete order meta button:</p>
<pre><code>'jsmsom_delete_meta_icon_class' ( 'dashicons dashicons-table-row-delete' )
</code></pre>
<h4>Related Plugins</h4>
<ul>
<li><a href="https://wordpress.org/plugins/jsm-show-comment-meta/" rel="ugc">JSM Show Comment Metadata</a></li>
<li><a href="https://wordpress.org/plugins/jsm-show-order-meta/" rel="ugc">JSM Show Order Metadata for WooCommerce HPOS</a></li>
<li><a href="https://wordpress.org/plugins/jsm-show-post-meta/" rel="ugc">JSM Show Post Metadata</a></li>
<li><a href="https://wordpress.org/plugins/jsm-show-term-meta/" rel="ugc">JSM Show Term Metadata</a></li>
<li><a href="https://wordpress.org/plugins/jsm-show-user-meta/" rel="ugc">JSM Show User Metadata</a></li>
<li><a href="https://wordpress.org/plugins/jsm-show-registered-shortcodes/" rel="ugc">JSM Show Registered Shortcodes</a></li>
</ul>


JSM Show Order Metadata for WooCommerce HPOS

Must need for Developer

Show WooCommerce order metadata in a metabox when editing HPOS orders - a great tool for debugging issues with HPOS order metadata.

Block Metadata vs JSM Show Order Metadata for WooCommerce HPOS