barnabyyeah if you’re writing markup based on anticipated use cases (rather than just mark up everything which you can, which is also a valid approach) then just having mf1 vcards doesn’t really get you anything afaik
SeirdyI see that the microformats wiki has some brainstorming, and suggests rel="source" or rel="code". schema.org defines a SoftwareSourceCode itemtype, but idk if that fits.
[snarfed]Seirdy the usual question is, what do you want other tools/applications to do with those links? we don't necessarily mark things up unless we have consuming use cases in mind
Seirdy[snarfed], jacky: i'd imagine that tools that tell you the tools behind a page could leverage it. right now we have stuff like "generator" meta tags and the ability to check a server's IP range to see who hosts it; this could be part of a set of additions to mark up a page with the tools behind it.
Seirdyso a page could have a "generator", "source", "sourceLicense" (as opposed to a license for the page content), "language" (vanilla html/js, vue, elm, typescript, etc), "platform" (writefreely, plume, etc), etc.
Seirdyin fact, there could be a "forge" schema that specifies links like "repo", "issuetracker", "discussions" (discuss mailing list, forum built into the forge), "contributions" (devel mailing list or PR tracker), etc.
jackytbh I'd prob put that in the AS2 for my site for each page (if it's referencable - most pages are from templates and I can link to what file at what version)
Seirdyone more question: I know that we can specify a date published, date updated, copyright date, etc. which make sense for a creative work. but how about a "date deployed"?
Seirdylike if you make a change to your website's HTML templates and redeploy it but don't change any articles, so the publication/updated dates should be the same. but I have a "site last deployed on..." footer that's populated with the current timestamp in the CI job.
aaronpkShow whatever you want on the page for humans to read, but unless there is actually some other software out there that's going to do something useful with the data there isn't really a point in adding markup to tell computers about it
ben_thatmustbeme, [fluffy]1, gire21, [jeremycherfas]1, [manton]1, darkkirb, gRegor and [pfefferle] joined the channel
[KevinMarks] well, it will be parsed by google/schema but it won't necessarily show up anywhere
[tw2113_Slack_] can't say i do anything with this topic
Seirdy [snarfed], jacky: i'd imagine that tools that tell you the tools behind a page could leverage it. right now we have stuff like "generator" meta tags and the ability to check a server's IP range to see who hosts it; this could be part of a set of additions to mark up a page with the tools behind it.