#microformats 2021-08-24

2021-08-24 UTC
jacky, ur5us, gRegor and aranjedeath joined the channel
#
@RonaldKeeling6
Likely candidates are Microformats, and RDFa.
(twitter.com/_/status/1430042986780536834)
hendursa1, KartikPrabhu, [fluffy]1, asteria1, ur5us, sayanarijit[d], [jgmac1106], gRegor and gRegorLove_ joined the channel
#
@voxpelli
↩️ Discord/IRC + a wiki + GitHub repos + GitHub issues? I think the @indiewebcamp / @microformats community has a very good setup for this
(twitter.com/_/status/1430152855340650497)
hendursaga, GWG and strugee_ joined the channel
#
@liran_tal
↩️ Thanks for expanding beyond the poll. I'm wondering if it isn't too much distributed for folks to actually get a grip on this? if I were joining a community and needed to follow on all of these mediums I'd probably get lost at some point
(twitter.com/_/status/1430165931620241434)
#
@aaronpk
↩️ IMO it's the opposite. If a community has only one platform I end up overwhelmed by how much discussion is all in one place. Separating it out means you can tune in to just the conversations that are relevant.
(twitter.com/_/status/1430167327241379843)
#
@petermolnar
↩️ A well maintained and curated wiki combined with the brainstorming-enabling, always-logged, searchable IRC (that is bridged to Slack, and Discord) is surprisingly nice.
(twitter.com/_/status/1430171271732604937)
KartikPrabhu joined the channel
#
sayanarijit[d]
Hi all, is there an `X-` equivalent (as in http headers) for microformats that lets me use custom class names as specifiers? E.g. `x-p-name`?
#
sayanarijit[d]
sayanarijit[d]: Or rather, is there any plan for something like this?
#
sknebel
-x- prefix on the name is sometimes used for experimental things, e.g. p-x-foobar. or if you are doing something custom, you can choose a prefix. (e.g. if I were to put a thing on my website that's clearly specific to what I do, I might call it p-sknebel-foobar
#
sknebel
to avoid confusion with other -foobar properties other people define
#
sayanarijit[d]
Ah got it... Thanks.
#
@GirelliGabriele
↩️ I completely agree with Peter. Especially, I think that the bridging plays a crucial part for new users, as it makes the platform choice into a flavour-picking one, without the risk of being left out of conversations :)
(twitter.com/_/status/1430177492225175555)
#
@voxpelli
↩️ Totally agree with Peter and Aaron here. Combining the fast pace IRC-style discussion with long term incrementally improved wikis enables people with different pacing needs to all stay on top. Then there's the actual BarCamps a few times a year as well, on top of the chat
(twitter.com/_/status/1430181729415929859)
#
@voxpelli
↩️ Having the chat and the wiki connected to one another is also pretty key I think. @indiewebcamp has a chat bot, Loqi, who connects the wiki to the chat, making it easy to look up subjects and document subjects, resulting in "tanteking", named after @t: https://indieweb.org/Tantek-ing
(twitter.com/_/status/1430182333383053316)
#
@voxpelli
↩️ All in all – a multi-channel approach / omni-channel approach to community building, making sure that everyone can engage in some way and that everyone feels included, yet that there is good progress. Also, here's Loqi himself: https://indieweb.org/Loqi
(twitter.com/_/status/1430183793181212672)
#
@voxpelli
↩️ There's also a newsletter bot built on top of the wiki (and integrated into the Loqi bot): https://indieweb.org/this-week-in-the-indieweb
(twitter.com/_/status/1430183477773840386)
hendursaga, gRegorLove_, [chrisaldrich] and gRegorLove__ joined the channel
#
@liran_tal
↩️ The omni-channel case resonates a lot, thanks for that perspective!
(twitter.com/_/status/1430220639332405256)
[snarfed] and KartikPrabhu joined the channel
#
[tantek]
I think it's more about different "channels" for different use-cases / communication cadences?
#
[tantek]
actually that should be in #indieweb-meta
ur5us, jacky and [tw2113_Slack_] joined the channel