[kevinmarks], [miklb] and [unoabraham] joined the channel
#[unoabraham]That's really not required, folks can simply go to their profile > Other Sites and paste in a bunch of their sites and social profiles. Works perfectly. Even shows up on the Rel=Me widget with all of the links.
#[unoabraham][miklb] No issue, but there are really more important issues to fix/areas to work on. Like Microformats plugin breaks meta data and causes the permalinks to disappear. I'd rather have that working and with that Bridgy backfeed working.
#[miklb]oh, sorry, I meant an open GitHub issue. GWG linked to it. I just think discussions around the community plugin should be documented there. That’s all.
#GWG[unoabraham]: The problem being no one who developed the Microformats plugin actually uses it.
#GWGThere was a debate as to whether we should even publish it at all, as it is a hack of sorts.
#GWGBut, it definitely needs a settings page to explain that.
#[miklb][unoabraham] understood. The nature of the varying degree of control over who/how/when each plugin gets updated is a bit difficult to follow at times, but the community plugins like the core IndieWeb should reflect community input.
#GWG[miklb]: They'd have to, as the Indieweb plugin requires two people to merge.
#[unoabraham]I'd think WP users should have Rel=Me figured. They would have to know the basics seeing they use plugins, themes, configure web host (even if it's a 1 click install).
#GWG[miklb]: I also wanted to look at another enhancement to the documentation.
#Loqi[IndieWeb WordPress Outreach Club] Description
It is only a very basic implementation, because not every element is accessible through actions or filters. It is better to use a theme that supports Microformats 2 fully.
FAQ
What are Microformats 2?
Microformats are a simple way...
#GWGAnd equally afraid that we'd lose a section of people who could get some basic microformats but wouldn't switch to a friendly theme.
chrisaldrich joined the channel
#chrisaldrichWhat if the mf2 plugin had a settings page for the various filters? Then at least folks could pick and choose pieces against their theme and/or some of us could better help indicate which ones to enable?
#chrisaldrichWe could also keep a spreadsheet of recommended filters to add to some of the bigger/popular themes.
#GWGchrisaldrich: That is what I was thinking of doing.
#[unoabraham]I have thought of that, and will even be giving it a try on a demo site.
#[unoabraham]But using a free theme for microformats support instead of premium themes costing several hundred dollars seems like no solution to me. Especially after the hours I've spent going through the tutorials and learning how to customize child themes.
#[unoabraham]I don't think that the theme developers will be open to adding in microformats support either.
#GWG[unoabraham]: That is why we came up with the compromise of a plugin, but it can't do very much, and is often thwarted by the developer unintentionally.
#[unoabraham]I'm going to have a play with it. Will see how easy it is to add to a child theme. If it's easy then I can roll out a child theme that works with the Genesis Framework.
gRegorLove, sebsel, [kevinmarks] and [miklb] joined the channel
#[miklb]theme developers are already adding microformats, just the wrong microformats and that’s part of the problem. 99% of themes use the mf from outdated core WordPress themes, used those classes for styling, and now Core won’t change it because they don’t want to “break themes”. We need to convince them that the current broken mf is breaking themes wanting to use current standards.
#[miklb]I’m not sure yet, but I’m going to start banging the drum. In semantic versioning, 5.0 should mean breaking API changes. Where else would it make sense to switch to core supporting mf2 than now?
#[miklb]a broken style hook isn’t the end of the world for developers
#GWGThey just rejected another Pingback change till 5.0
#[miklb]I’m OK with pushing to 5.0 as long as it isn’t a veiled punt.
#GWGThey once pushed a simple change 5 versions and it only got in because kraftbj pushed for it
#GWGThe comments room on WordPress slack is abandoned for months, no attention there
#[miklb]then we need a more concerted effort to push the change. Instead of these things looking like one or two people.
#GWGI have not pushed much on the theme side, but my push for filters and hooks to support structured markup got poo pooed
#[miklb]the greater IndieWeb community to start. aaronpk deals with broken WP all the time.
#[miklb]WP needs to be better web citizen in how it moves forward and interacts with the net.
#aaronpkthe updated mf1 backcompat parsing has helped
#[miklb]is that generally on sites that aren’t trying to use mf2 though?
#aaronpkoh yeah no, broken mf1 on sites that don't know about mf2 is still a problem
#[miklb]I ask because I want to get the facts right when I present some of this in trac tickets.
#GWGaaronpk, I am working inside the WordPress Microformats 2 plugin today
#aaronpkthings that are particularly bad are things like hfeed appearing on every page because it's in the <body> tag, or hentry appearing on feed pages because it's on the <body>
#GWGaaronpk, I got them to fix hfeed on the underscores starter theme and on new bundled themes.
#[miklb]sent! let me know if comes through though [chrisaldrich] I think I got mailgun setup for sending but you’re the first I’ve tested since doing everything manual
#[miklb]Also my server isn’t configured to install plugins from the admin, most of what I use I manually install/update from GitHub repos, so if there’s a tool or plugin we need there, just holler.
#[miklb]if I’m not mistaken, table comes from like Robert’s Rules of Order or something like it. But I’ve also seen discussions where in some circles table means to put to a vote. ¯\_(ツ)_/¯
#GWGThe block based thing is going to change everything
#[miklb]hmm. I thought all the crazy stuff was going into HTML comments. No?
#chrisaldrichAnother question is that for themes which might be changing as a result of gutenberg, is there a way that we can help folks to do better mf2 at the time of the change?
#[pfefferle]There is no real need to change something
#[pfefferle]Gutenberg will work with Most themes without big changes
#[pfefferle]And if there are, it is mostly css based
#GWGI guess to be a WP developer, you have to do JS now
#GWGI think I need to support json feed in Post Kinds
[kevinmarks], sebsel, tantek and doubleloop[m] joined the channel
#tantekre: all the arguments about lots of WordPress plugins vs a few (or one) IndieWeb plugin that just "does everything for you", note that Drupal is taking the "one plugin" approach - check out the list of functionality here: https://www.drupal.org/project/indieweb
#GWGI would consider merging some of them. I'm in the minority
tantek joined the channel
#tantekGWG it almost sounds like there is a need for two kinds of indieweb plugins
#tantekfirst, the dominant style preferred by people here, are the "small single function" plugins that allow for tinkering, mixing & matching etc. lots of preferences because everyone wants their own way
#GWGI think Micropub and IndieAuth could merge together into one thing.
#GWGI'm merging new functionality into Syndication Links instead of creating something new, as I originally thought.
#GWGI'd love to have Semantic Linkbacks and Webmentions together, but those aren't mine to merge.
#tantekGWG if you want to merge your plugins together, you'll have to make it clear that your merged super plugin is for ease-of-install and maintenance for gen2-4
#GWGPost Kinds is much more user friendly than hand-coded microformats, but I fear imposing my view of things on others.
#tantekotherwise you'll tons of issues / complaints from all the gen 1 folks asking for everything to be separate
#tantekthe "one super plugin" is going to require that you impose a view / vision of ease-of-use
#GWGMy next plan is to deprecate Bridgy Publish as a plugin. It is going to merge into Syndication Links
#GWGI'm going to start folding things into each other.
#GWGI think IndieAuth and Micropub can merge together.
#tantekGWG, the more you can merge plugins (and eliminate separate plugins) the better
#Loqi[snarfed] i still don't use micropub much myself, so I'm gradually realizing that I'm the wrong person to own this plugin or drive its development.
so, i don't expect to work on this change myself, but it's still probably still the single most important thing...
#GWGsnarfed isn't actively working on Micropub. I think he'd be happy to give it up.
#tantekHow about merging them both into the IndieWeb plugin?
#tantekif folks still want a separate "do nothing" installer, then create a separate plugin that someone else can maintain (whoever wants a bazillion plugins) called "IndieWeb Installer"
#[pfefferle]hard question… as a one man show it is a tough plan…
#[pfefferle]that is the main problem… there are a lot of people discussion the issues, but there is not much help when it comes to coding… at least for WP…