#microformats 2018-06-09

2018-06-09 UTC
gRegorLove, [chrisaldrich] and chimo joined the channel
#
@snowcloneminute
He may be a microformats, but he's our microformats
(twitter.com/_/status/1005304443825315845)
barpthewire, [xavierroy], KartikPrabhu, [jeremycherfas], [chrisaldrich], GWG, tglobe, nitot, nitot_, [davidmead], [jgmac1106], gRegorLove and barpthewire1 joined the channel
#
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
#
gRegorLove
I don't know if you've seen this yet, but pin13.net will show you the parsed output. pin13.net/mf2 will let you do direct HTML input, too.
#
gRegorLove
Here's an example of microformats1 backcompat parsing: http://pin13.net/mf2/?id=20180609184155625
#
gRegorLove
If your page has mf2, the parser *should* ignore mf1 properties within it. Backcompat parsing only happens if it's an mf1 root.
KartikPrabhu and [cjwillcock] joined the channel
#
[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?
#
sknebel
no, it has to put both on the same element
#
gRegorLove
Which 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
#
gRegorLove
The 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]
aha, so an mf2 root doesn't create an mf2-only context - the parser may still upgrade mf1 roots
#
[cjwillcock]
within the mf2 root
#
[cjwillcock]
there's really no way for me to indicate that I want all mf1 tokens to be ignored
#
[cjwillcock]
sknebel++
#
Loqi
sknebel has 9 karma in this channel (101 overall)
#
[cjwillcock]
gRegorLove++
#
Loqi
gregorlove has 31 karma in this channel (245 overall)
#
[cjwillcock]
thanks, very helpful
#
gRegorLove
If you have `.h-entry .hentry` on the same element, mf1 properties will be ignored, as long as there isn't a child mf root.
#
[cjwillcock]
list of mf1 roots for reference? I'm searching the microformats.org wiki now
#
Loqi
Welcome to the microformats wiki!
#
gRegorLove
WP should, I think, only be adding .hentry root mf1
#
gRegorLove
Unless it's some specialized theme
#
[cjwillcock]
example: vcard, is that a root
#
[cjwillcock]
I really thought I had a better handle on this, lol. Only when you try to talk about it do you realize
#
gRegorLove
Hehe, mf2 definitely made it simpler
#
gRegorLove
Yes, the hCard spec uses class 'vcard'
#
gRegorLove
Sorry, forgot about that one. I'd expect WP themes to have hEntry and hCard
#
[cjwillcock]
that's my troublemaker in the WP twentyseventeen theme, vcard
#
gRegorLove
The parsed author property there looks good.
#
[cjwillcock]
Right, in this case I modified the the wordpress-uf2 plugin to include my u-photo in the vcard context that the theme uses
#
[cjwillcock]
and as you or sknebel said, u-photo is not a requirement -more of a snapshot of what was once a suggested way to go
#
[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
#
gRegorLove
.u-photo in an .h-card is still recommended, if you're showing a photo
#
gRegorLove
The `author vcard` at the top of the post is being parsed as a child microformat and a bit incorrectly
#
gRegorLove
Okay, sounds good. Feel free to ask any questions :)
#
[cjwillcock]
yes, I don't want to misquote - it was that the h-card is not necessary there, as a simple <a class='u-author' href="..."> would do
pniedzielski[m], [davidmead], KartikPrabhu, [kevinmarks], [cleverdevil], wakest, schmarty, [grantcodes], [mrkrndvs], [chrisaldrich], barpthewire, [deeden] and tantek joined the channel