gRegorLove[cjwillcock], reading your starting-with-wordpress notes. microformats2 parsers are backwards compatible, so a microformats1 hentry will be upgraded to h-entry. That's what you're seeing on indiewebify.me
[cjwillcock][gregorlove] Thank you. If you are familiar with the indieweb/wordpress-uf2 plugin, it's putting an h-entry on <body>, and moving hentry to <body> as well. I will need to do my own testing, but in your view, might it be better to leave hentry as-is and only add the h-entry?
gRegorLoveWhich element they appear on isn't too important, but yes it's important they appear on the same element if you're using both. I'm not too familiar with wordpress-uf2
gRegorLoveThe backcompat parsing rules would treat a .hentry found *inside* an .h-entry as a child microformat and use the backcompat parsing on that child .hentry
[cjwillcock]I think I'll go back to my starting-with-WP work, and try to emphasis the indiewebify.me 'full green' much less so - well something to think about as I get back there