#Meatwad[m]ty for the link, wish it was just a paper not an event
#Meatwad[m]cannot think of any reason why that needs to be an event
[chee], tweet[m], justBull, [KevinMarks], wagle, ben_thatmustbeme, Oclair, hey, shrysr_, GWG, Kaja, beko, jeremycherfas, Meatwad[m], globbot, reed, pauho[m] and sergiotarxz[m] joined the channel
#[chee]i'm curious why the Wordpress post kinds plugin implements post kinds from scratch rather than building on top of post formats with `register_post_type`? i'm trying to learn the codebase so i can look into doing some work on it
chee joined the channel
#GWG[chee]: Post Kinds doesn't use register_post_type
#GWGPost Formats is a WordPress taxonomy, but not extensible
#GWGIndieweb post types...called kinds in WordPress solely due to name collisions, are derived from the properties used. The setting in the interface just tells it which properties to use in the various fields
#GWGIf it comes via Micropub, for example, it uses post type discovery...the deriving of post type from supplied properties to figure it out
#GWGThe taxonomy also allows the archive page generation
#[chee]this is excellent, thank you for this information
#[chee]i'm a javascript programmer in my day job, by the way, and would be very interested in helping bring post kinds to gutenberg
#GWGI wouldn't object in theory to learning more JavaScript... just haven't figured out the best design for adapting it to blocks.
#GWGAn earlier step is probably to implement the different post kinds as a schema
#GWGEssentially document the properties utilized in each one, so they could be rendered...I sort of started that.