From IndieWeb

possible article stub for theme developer guide:

  1. Run the theme and post through
  2. You can also visit htpps:// and ask for help looking at the source code of a post to see if it has the correct microformats2 mark up.
  3. Remove any old microformats if they are found. This is usually indicated by a v-card or fn in your classes.
  4. Add micoformats2 to each post type template.
    1. Begin with the h-card. The IndieWeb plugin handles this by adding rel=me links in the profile and adding an h-card widget. You can just fold these into the theme or add an h-card to the header or footer.
    2. Then you can look to h-entry. You can start with just your post and page types. You could stop there and be done
    3. If you wanted to add all the #IndieWeb Post Types (hence known as post-kinds to avoid confusion) look at the post-kind page on the wiki
    4. The Post-Kind Plug in adds these, but it would be better to fold this plug in into your theme. I do not know why the custom post types aren't used but I would ask Matthias Pfefferle and David Shanske
  5. Add a notification to add the following plug-ins. There are more but these will get your users started.
    • semantic linkbacks
    • Bridgy
    • webmentions
    • micropub...technically not required but publishing with third party clients is awesome
    • IndieAuth
    • Indieweb... if you didn't do rel="me" and h-card in your it in your theme
    • Post-Kinds...if you didn't do it in your it in your theme
      • There might be some UI changes that I don't have a clue about. Better question for David or Mathais
      • Remember keeping things as basic HTML as possible is a major design consideration of the #IndieWeb. Plus it helps out the microformats parsers
      • Go to again try again. Hopefully all passes.
      • Go to webmentions.rock and test all the validators. Hopefully you will pass