#microformats 2020-01-21
2020-01-21 UTC
Nuve, YEA, mattgorecki, KartikPrabhu, [Marlin_Forbes], [dmitshur] and gRegorLove joined the channel
# I'm back from the Barbados, learning more about HTML microformats! https://twitch.tv/thibpat https://t.co/MC7aMiHLpr ( twitter.com/_/status/1219521133109706752)
[tantek] and KartikPrabhu joined the channel
# ↩️ @googlewmc Hi @googlewmc, will you continue to support & display structured data with http://microformats.org ? Thanks! ( twitter.com/_/status/1219567755118174208)
KartikPrabhu joined the channel
KartikPrabhu, jgmac1106 and [KevinMarks] joined the channel
# ↩️ We don't have any plans for changes to announce there at the moment. I don't know off-hand how broadly microformats are used, my guess is it's much more than data-vocabulary. That said ... https://trends.google.com/trends/explore?date=all&q=microformats,data-vocabulary,schema.org ( twitter.com/_/status/1219597542318538752)
[LewisCowles] joined the channel
Isaac joined the channel
# ↩️ @ChrisFerdinandi This is one reason why I have always preferred @microformats over this. It's much more straightforward in my mind. ( twitter.com/_/status/1219628210801070080)
[Marlin_Forbes], KartikPrabhu and [jgmac1106] joined the channel
# ↩️ @JasonNeel @microformats Is that what they use on WordPress? I know I've seen this before. ( twitter.com/_/status/1219654054680449024)
# ↩️ Hmm, that’s a good question. I don’t have nearly any experience with WordPress so I can’t really say with any certainty that they use it there. But I know it’s used in a lot of IndieWeb patterns: https://indieweb.org/Getting_Started#Add_microformats_to_your_content ( twitter.com/_/status/1219655473584099328)
KartikPrabhu joined the channel
# ↩️ WordPress used older version of microformats, but not any more. Still find few pieces hanging in core, lot more in different themes.
For the best #IndieWeb WordPress experience use a community built theme or add microformats to yours (https://quickthoughts.jgregorymcverry.com/s/2l5GHx) ( twitter.com/_/status/1219657044090937345)
# ↩️ There is a microformats plugin but success with it is theme specific, you can try it on your theme and stop by #IndieWeb chat for help seeing if it works. But best bet, as I said, is use a community built theme so we know the metadata correct (https://quickthoughts.jgregorymcverry.com/s/1L3Lt3) ( twitter.com/_/status/1219657871727767554)
# Google finally realizes it created a trashfire. They should just support Microformats 2, much easier to construct and therefore use. https://twitter.com/googlewmc/status/1219565763759165441 ( twitter.com/_/status/1219659841100242944)
jgmac1106, adfzah5q4q28u6yj, Hooftly1337[m], [tantek], gRegorLove, jacky, [email096], mauz555 and [schmarty] joined the channel
# @JohnMu @googlewmc @danbri What about microformats? Do you still support the markup?
https://webmasters.googleblog.com/2020/01/data-vocabulary.html ( twitter.com/_/status/1219714852505014272)
[yo] and [tantek] joined the channel
icaruszDiscord[4, daveatQCDiscord[, KartikPrabhu, [manton], [jgmac1106] and jgmac1106 joined the channel
# ↩️ 3/2 Additionally, it's much easier to *generate* JSON-LD because it isn't tied to the HTML structure.
So the tooling is much better in terms of tools that can dynamically or statically generate the JSON-LD for you, based on your inputs.
Doing that with microformats is not easy ( twitter.com/_/status/1219750071652245512)
[Michael_Beckwit joined the channel
# ↩️ Well, nothing is ideal, everything is varying layers of suck.
But given the choice between JSON-LD and itemprop= microformats, it's no contest. JSON-LD is just a much more sane, manageable format in practice.
Just my two cents from using them both. ( twitter.com/_/status/1219753186602426368)
jgmac1106 and [Michael_Beckwit joined the channel; silent_ActivistD left the channel