friedcell, nitot, mlncn, davidmead and cmal joined the channel
#cmalhey, is there some guidelines for multi-lingual h-card? should I have one h-card per language but share the same u-url?
#Loqicmal: petermolnar left you a message on 7/13 at 12:35am: I tried to switch to grav a while ago, because I love their approach, but it seems the amount of full size photos I have is too much for the cache system grav has. However, I did make this; it might come handy: https://github.com/petermolnar/grav-plugin-syndicationlist
#cmalpetermolnar, thanks for the link, I'll check it out :)
#cmalGrav is indeed intended for small-size sites (few thousand pages), but I believe there's a lot of room for improvement on this side, but there's discussions about it atm
#cmalstill, I see many use-cases for small Indieweb-powered Grav websites :-)
KevinMarks, Lancey and [kevinmarks] joined the channel
#[kevinmarks]How do your h-cards differ by language?
#cmalKevinMarks, translation of p-job-title, p-description, potentially p-name as well?
KevinMarks_ joined the channel
#cmal> KevinMarks, translation of p-job-title, p-description, potentially p-name as well?
#cmalI'd say the limitation with this approach is it's fully content-based, i.e. you need to provide the actual translations in the same stream of information, I'd rather go for something url-based
#cmallike having lang markup on h-entries/h-feeds/h-events, then have maybe something like <a class="u-translation-url" lang="fr" href="https://cmal.info/fr/something">Français</a> inside of those h-feeds, h-entries, h-events
#voxpelliif one already is on a page with a representative h-card
#voxpelliand wants to find other language variants for that h-card
mlncn joined the channel
#cmalvoxpelli, I wouldn't count on that, you could have stuff translated to many languages, doesn't mean everything on the page will be (say, the h-card)
#cmalI think it's more reliable to depend on values within the h-card itself
#voxpellicmal: well if you are on the u-url of the h-card and that url has language url:s then it would be odd if the h-card wouldn't be translated as that's the main content of that page?
nitot joined the channel
#voxpellia lang="" on/around/in the h-card could however indicate whatever content that for some reason isn't
#cmallike if you have a page translated to spanish in your site but you don't have spanish translation for the h-card that's embedded within, we shouldn't consider a rel alternate with spanish language as a translation for the h-card itself
#cmalvoxpelli, but what for instance if your h-card is on your homepage along with other information?
KevinMarks joined the channel
#voxpellicmal: if you are on a page representing something else but the h-card, then yes, I agree :)
#cmalwell should the u-url of the h-card be pointing to something that *exclusively* represents the h-card?
#voxpellicmal: no, but it's hard for me to imagine a translated representation of an h-card, like a front page, where everything but the h-card itself is translated :/
#cmalI think it makes sense for the end-user (browser-side or for global site lang switcher buttons) to have links for all potential translations (as in, languages enabled on the website) on a best-effort basis, but then individual h-entry/h-feed/h-event/h-card should have their own individual translation markup for more precision on what can be translated in what
#voxpelliI think both hreflang="" on <a> and hreflang="" on lnk rel-alternate as well as lang="" within the page itself all serves their purpose depending on what setup one is going for :)
#myfreewebhi! haven't been here in a while, looks like micropub media endpoint is now a thing, nice! aaronpk: the spec says ?q=config, but i see Quill doing an empty query?