Documentation help

  • I’m trying to set up an “indieweb compliant” blog now, and I feel like I just don’t quite understand what’s going on with this plugin. ?? Here’s a few questions that would really help me get a handle on things, and might be good for documentation purposes in general. I’m a technical writer and would be happy to help work on documentation for you if you’d like, but I need to clear up my own confusion first.

    What’s the relationship between “Post Kinds” and WP’s native “Post Formats?” Do I have to set both of them, or should I just be ignoring Formats if I’m using Kinds?

    What’s the relationship between the “Post Properties” box and the main edit box? What I mean is that it seems for some post kinds (e.g., notes and articles), you don’t need to fill in anything in post properties, but for other post kinds it seems like you shouldn’t fill in anything for the main entry field and instead do everything in the properties box.

    Last but not least: are there any tips for CSS styling kinds in a theme? Is there a way to tell the plugin <i>not</i> to automatically insert the SVG icon denoting the kind if I don’t want it?

    (I’m serious about the documentation help offer, by the way, if you’re interested)

Viewing 1 replies (of 1 total)
  • Plugin Author David Shanske

    (@dshanske)

    Post Kinds is an Indieweb replacement for Post Formats. Post Formats never took off, to be honest. For backward compatibility, post formats are set when they map similarly to Post Kinds though.

    The Main Edit field acts as the ‘content’ property. Not all types of posts have content.

    As for styling and the icon…your theme can have its own custom template for each kind or all kinds, if you add a kind_view directory in the theme. Inside, kind.php or kind-{type}.php will override the plugin files.

    The only way to be more clear is to try tool popups and similar.

Viewing 1 replies (of 1 total)
  • The topic ‘Documentation help’ is closed to new replies.