Zegnatspenc: most microformats parsers require a DOM tree as input, so they will only see classes that are part of that, but most of them will not run JS. So the parsers will probably not see classes that are being inserted by the custom-element
[mail918]Do you have a recommended way to do some simple HTML templating ? I had some liquid templates I was happy with but I'm trying to move away from having a build process
ZegnatThere are so many templating systems, hard to say anything. Basically all of them can generate HTML with classes, so all of them would be able to add microformats.
ZegnatTheoretically microformats parsers can run after JS, e.g. as part of browser addons, but most parsers run on some sort of server and parse HTML retrieved over HTTP without involving a JS engine.
ZegnatI think https://indieweb.org/template links to a bunch of templating engines if you are looking for one, else maybe join the #indieweb-dev channel for that discussion. It will quickly fare away from microformats themselves and probably not best answered in this channel.
capjamesgI see "There is currently no text in this page. You can search for this page title in other pages, or search the related logs, but you do not have permission to create this page."
tantekedited /existing-rel-values (+6) "/* HTML5 link type extensions */ rel-edit is in use with visible edit hyperlinks (e.g. to GitHub repos)" (view diff)
[tantek]capjamesg, unfortunately we don't have a "best practice" or a template / boilerplate for rel- value specs. Take a look at the specs linked from the home page, and use your judgment for which sections to copy/paste and see if you can improve upon past specs: https://microformats.org/wiki/Main_Page#rel_microformats
[tantek]go for it, I have a few other things to take care of, and it would benefit from your fresh perspective (looking at those prior rel- specs and picking and choosing the sections that make sense to you)