Post Kinds

Post Kinds adds support to the Classic Editor for responding to and interacting with other sites using the standards developed by the IndieWeb by implementing kinds of posts. It is not compatible with Gutenberg. It can also distinguish certain types of passive posts in a manner similar to post formats. While it can work alongside post formats, it is recommended as a replacement as it is designed as a replacement using IndieWeb Post Types. Many sites will not need all of the kinds set up. What kinds of posts you wish to publish are specific to your needs. Post Kinds requires PHP 7.4 or later and WordPress 6.2 or later. It also supports ClassicPress 2.7.3 or later. Privacy and Data Storage Notice Post Kinds stores extra data in a post indicating what you are responding to. This data is either hand-added or can be parsed from the source URL if provided. This means you have additional responsibilities to responsibly use this data, and to remove information on request. Credits Kind Icons are currently provided by Font Awesome and are licensed as CC BY 4.0. A copy of the license notice is bundled. Chris Aldrich always receives a credit on my plugins due his regular feedback, input, and usage. Theme Support Post Kinds works with most themes without changes. It adds the response (what you replied to, liked, listened to and so on) to the post’s content and excerpt, and to feeds. To place the response somewhere else in your theme, turn off the automatic display and call kind_display() in your template where you want it: add_filter( 'kind_content_display', '__return_false' ); Many kinds have no title. In templates that list posts, kind_get_the_title() returns the post’s title, or generates one from the kind and what it responds to. To change how a kind looks, create a kind_views folder in your theme, copy the view from the plugin’s views folder into it, and edit the copy. It persists through plugin updates, but it doesn’t receive fixes: compare it with the plugin’s views after upgrading. To style responses, target the .response wrapper that each view uses, and .kind-embed around embedded content. The template functions, hooks and view variables are listed in the developer notes.