#[TMichelleMoore][chrisbergr] I figured out how to keep the JetPack sharing on. I put almost all of the classes in the template except for e-content. I did leave p-summary on the excerpt in the template. Each individual post would need a group with class=e-content. I believe this allows the freedom to add things like u-in-reply-of or other types of things which was another thing I was going to experiment with.
#[chrisbergr]I'm happy that you figured this out 🙂 JetPack related stuff is somithing I don't notice because I am not allowed to use any of it's features in germany. I get that those context-issues comming from post kinds may produce some issues if they are printed in e-content. I always prevent the default printing of the plugin and print it via hook on the desired placce, but I haven't woked on it since the introduction of block
#[chrisbergr]themes. Way to busy the last 2 years.. I am happy that I managed a server transfer of my short domain and the replacement of my old wordpress page with a vcard similar to linktree in my last 5 days at home...
#[TMichelleMoore]Well [chrisbergr] that’s interesting you can’t use the features there. They seem pretty harmless. My h-card is next. I am thinking I really shouldn’t have it in the footer of every page. I think it should be on the home page only and then the author card on each post refers to it. This is sort of how this all came up, I was doing some testing for @gwg and I started with the IndieWeb plugin, which talks about h-car
#[TMichelleMoore]which I don’t have widgets for…which then led to the discovery of the mf2 plugin. And now I am two days behind. Lol
#[chrisbergr]It seems like the IndieWeb plugin only provides a widget for that h-card, no shortcode. twentytwentythree doesn't have any widget areas, so there is nothing to use atm. The mf2 plugin I don't know. But always ask yourself: Do you really need a plugin for something simple like a h-card? It is so simple to build with html, so it is also simple to build with wp block. At least the html block.