Blockify everything, prefering HTML+blocks rather than patterns.

[dd32]

PR'ing this against my own repo intentionally for a self-reminder. This is probably going to go stale very quickly, but that's OK.

This was a trial-run at removing some of the template-parts and using block templates instead instead of pattern hacking.

Things I ran into:

• wp:query works, but I ran into shortcomings around the blocks available via it.
• When using wp:post-template you can set the className on the <ul> but you can't set the class on the <li> (which is what the post_class is). This lead to a str_replace on the block render HTML to add plugin-card to the plugin-cards, later fixed by using a different CSS selector instead.. Unable to add a class to query block list item WordPress/gutenberg#41441
• When using wp:post-template you can't define a "top level" block, so the "plugin-card" block is actually only the contents of the node that it would be rendered as, ie. it's all of the contents inside the <li>....</li> not including the li tags.
  • Likewise, you can't change the element from a <ul> to something like <div>. Use core/post-template to have each post render within <article> tags WordPress/gutenberg#37659
• A bunch of template tags I wanted aren't present.
  • I made a wporg/missing-template-tag eval block for this, and I quite like it as a hacky fixer.
  • <!-- wp:wporg/missing-template-tag {"function":"the_archive_description","args":["<div class='taxonomy-description'>", "</div>"]} /-->
  • <!-- wp:wporg/missing-template-tag {"function":"the_posts_pagination"} /-->
• Blocks are rendered before wp_head fires, so there's some customization on archive titles that doesn't apply to the block rendered header.
  • This is probably OK for us, as we'd probably want to use our own search archive template header/title and probably the same for the archive.
  • As a proof of concept, I tried to convert it to a variation of the query-title block which was laughable. See 9260f8f