#wordpress 2025-09-09

2025-09-09 UTC
dagabeagenda and [pfefferle] joined the channel
#
[pfefferle] I think it is fine... it should fall back to the classic html5_comment if it is not a Webmention... otherwise the code below should mark up the Webmention...
#
prtksxna I had made a WP theme for my site a while back and wanted to figure out if there is like a checklist for it to be in 'IndieWeb Friendly Themes'?
#
GWG- [pfefferle]: I just thought only selectively overriding would produce better results than overriding the entire functionality
[morganm], [Al_Abut], gRegor and [asuh] joined the channel
#
[asuh] [pfefferle] from what I was seeing for the comments section from the code snippet I provided, every comment was being routed to the classic `html5_comment` instead of the custom code that GWG wrote for that function. Why would only Webmentions use the custom code and not comments that users submit to the blog post? I’m not quite certain of the logic
#
GWG- [asuh]: It was annoying the ActivityPub users I think
#
GWG- Not just them, but I think that's the group that had the first issue
#
[asuh] GWG, were ActivityPub users asking to use the classic `html5_comment` instead of your custom version?
#
[pfefferle] [asuh] because only Webmentions have the extra meta-data, that is used in the custom code... staying with the core functionality for classic content is most of the time the best solution, because it does not break theme styles!
#
[asuh] Interesting, does the extra meta-data code like `.h-card` for authors, `.e-content` and `.p-name` for comment text, these don’t add value to comments?
#
[pfefferle] I am not speaking about them... but sure they semantics add value, but it doesn't matter if the core theme does not support mf2 but only the comments...
#
[pfefferle] microformats in wordpress are a whole different topic
#
[pfefferle] that we still have not really solved
#
[asuh] Ah, I didn’t think about this. Webmentions, and well the Comment Walker itself, does not have a theme Microformats2 support in mind, so it’s relying on the classic code for that reason. That wasn’t clear to me but it makes sense in context
#
[pfefferle] the problem is, that the comment walker is ONLY about the comments section
#
[asuh] In my own theme development, I’m trying to have full support of MF2 by default, and I’m supporting the classic comments code if someone doesn’t want the Webmentions plugin, but I want the comments to use MF2 if enabled
#
[pfefferle] so either your theme already has built in support for mf2, then classic comments will be marked up properly and we would only have to add the special cases for Webmentions (like likes, shares, bookmarks, ...)
#
[asuh] I’ve manually added MF2 to everything in my theme, yes, but I have to also manually do this for comments (or rather, outsource is to Webmentions and build upon that)
#
[asuh] *outsource it
#
[pfefferle] this is how I did it: https://github.com/pfefferle/autonomie/blob/master/comments.php
#
[pfefferle] works perfect with webmentions
#
[pfefferle] and https://github.com/pfefferle/autonomie/blob/5aa70a5df068662d78180465a38644a0cf54c9fd/functions.php#L469
#
[asuh] Yes, that’s similar to my previous approach, but I want first-class Webmentions support when enabled
#
[pfefferle] https://github.com/pfefferle/autonomie/blob/master/includes/semantics.php
#
[asuh] If someone doesn’t use Webmentions plugin, it’ll fallback to classic comment code, but I could manually support MF2 in the theme even if Webmentions isn’t installed, I just had to draw a line somewhere
#
[pfefferle] the semantics.php file I linked above is adding microformats through core functions
#
[pfefferle] at least where possible
#
[pfefferle] this way you would not have to change too much of the code
#
[asuh] That’s similar to my Setup file: https://github.com/asuh/forage/blob/main/app/Setup.php
#
[asuh] I’m always trying to make sure I didn’t miss anything, and there’s not clear documentation to explain all these additions to standard WP themes, so I’ll review your semantics file. I already reviewed GWG’s iw26 theme as well
#
[pfefferle] so if you work on a custom theme, I would recommend to add as much microformats as possible to the theme and do not rely to much on external code
#
[pfefferle] this is the only real solution that worked for me
#
[asuh] Makes sense. I tried to take that approach
#
[asuh] Webmentions adds the custom functionality that I didn’t want to recreate so that’s the only bit I outsourced so far
#
[pfefferle] and that is fine I think
#
[pfefferle] Jan Boddez had a nice extension to the block editor
#
[pfefferle] to add mf2
#
[pfefferle] but he is no longer working on WordPress 😞 https://github.com/janboddez/indieblocks
#
Loqi [preview] [janboddez] indieblocks: Use blocks, and, optionally, "short-form" post types to more easily "IndieWebify" your WordPress site.
#
[asuh] Yes, a future goal I have is to see how I can support IndieBlocks, but it’s a lot since he’s targeting the Block Editor by default and I’m still in a hybrid state
#
[asuh] I’m also considering a feature branch that has pure PHP without Laravel Blade templating to make remove more abstraction and potentially make this buildless overall
#
[pfefferle] good luck 🙂
#
[asuh] Ha! That’s only if I get that far. It’s taken me years to get this far, considering my moderate PHP skills
#
[pfefferle] In germany we would say something like: The journey matters more than the destination :)
[manton] joined the channel
#
GWG- The journey is fun