[Dan_Q]It's all very prototypey/experimental, and my goal isn't actually post-kinds-for-Gutenberg (that's just a side-effect) because I've got OTHER Gutenberg-unfriendly plugins too! My goal, though, is to outsource microformats-stuff to my theme and just use post-kinds for the backend interface.
[Dan_Q]* Writing a Gutenberg meta-widget for selection of post kinds. I first just set 'show_in_rest' and 'hierarchical' to get Category-style "checkboxes" with which to specify the "kind" of a post, but then started working on a "proper" meta box to give me a drop-down. Then I broke it.
[Dan_Q]* Started making "blocks" for different functions; the first one I'm looking at is for citing/embedding; the idea being that you can e.g. make a post of kind "reply-to" and then add a "cite" block to it, containing the stuff you're replying "to" as a blockquote (optionally empty, I suppose) and the relevant metadata (right now it's only static; I've not made a form yet because I'm very new to React).
[Dan_Q]For many purposes the ultimate solution here would be _harder_ for authors than the current approach, but would allow e.g. replies that cite multiple sources, for example. Webmention still seems to work regardless (it doesn't care).
[Dan_Q]I'm going to keep an eye out for upcoming Gutenberg-blocks-related work at my "day job" that I can volunteer myself for, so that I've got an excuse to learn it properly.
[Dan_Q]I just love being able to differentiate my different types of content in a meaningful way (while keeping them all fundamentally "posts") in a microformats-friendly way! I'm among the folks who care more about the backend, too.
[Dan_Q]^ that's both a h-entry and a h-review, and includes a p-rating and a h-card (with name, address, lat and long) for the "thing" being reviewed ^
[Dan_Q]No, unfortunately the time I first heard about it I'd already come up with my own metadata schema for locations, and I haven't had the time or energy to think about migration!