(Skip to the end for the TL;DR summary) After an evening of debugging and rewriting sections of the HTML in “K”, I think I’ve fixed the markup and parsing issues I mentioned yesterday. It turns out that X-Ray, the parsing engine used by IndieNews, Aperture, and probably others, was only findin...
With this announcement, I have two great pieces of news. The first, is that you'll now be able to follow my website's h-feed, which is a microformats2 structure for a feed of data. This is in addition to my RSS feed (/feed.xml) and my JSON feed (/feed.json), and will allow further interoperability with the IndieWeb.
We used to control our online identities, content, and experience. We now share Twitter names instead of domains; even web developers tweet and post on Medium instead of their own sites. We scroll social media and feel empty instead of reading news & blogs to feel informed and connected. Algorithmic feeds amplify rage & conspiracies, enabling tribal ad-targeting to polarise and spread misinformation, threatening democracy itself.
What happened? And what are we doing to fix it?
That's a big question that will require all of us, our communities, our employers, to shift. I don't want to wait, and you probably don't either.
What can you do for yourself, today?
Own your domain. Own your content. Own your social connections. Own your reading experience. IndieWeb services, tools, and standards enable you to take back your web.
This page is for brainstorming about various uses and details of XFN, as well as collecting input for potential extensions.
It took me a while to puzzle it out when I first ran across it, but the text just underneath your title:
<SPAN CLASS='P-AUTHOR H-CARD'>MIRIAM AVERY</SPAN> is occurring because you’re using the microformats 2 plugin which tries to inject the p-author h-card portion into your page, but it’s having a conflict with your theme which is escaping the output for that author section. (More details on this known issue here.)
Chances are pretty good that you could deactivate the microformats plugin to fix the cosmetic issue without causing other major issues. Depending on your theme’s native microformats markup, you may likely find that you don’t see or experience any other major issues with any of the other technology. The one issue I’ve seen people come across here is if they’re using Brid.gy to syndicate their content via webmention to Twitter, in which case having stronger markup becomes much more important. Hopefully this will at least help you track down and either fix the issue or figure out the best way around it for your particular needs.
The best long term solution would be to add the proper microformats markup directly into the theme itself.
I’ve been chipping away at several things over the last two weeks, mostly focussing on markup, presentation, and theme file organisation. I want to get these finalised before I look at theme customisation options. If you’ve visited the home page, you might have noticed the display of certain pos...
Pixellated Microformats SVG button to celebrate the 15th anniversary of Microformats being shown off at ETCON 2004 by Tantek and myself.
I spent yesterday working on a version of a blogger theme compatible with IndieWeb tools like webmentions. You can see an example here: https://drmacsspot.blogspot.com/ Then using IFTT I syndicate my notes to Twitter and the tweets get displayed back on my blog as comments. Here is an example: https...
Importing and editing custom templates on Micro.blog.
There are also simpler methods than RSS now including the microformats-based h-feed which one can use to create a simple feed that many feed readers will support.
Part of RSS’s ubiquity is that it is simply so prevalent that most common CMSs still support it. The fact that the idea of RSS is so old and generally un-evolving means there isn’t a lot of maintenance involved once it’s been set up.
Now that phase one of Gutenberg has dropped the interest in #ClassicPress grows by the day. So many WordPress developers fear the loss of control they will face under the new regime of 5.0. Many just don't want to do the work of all that refactoring. #IndieWeb and #ClassicPress should join forces. w...
2018 war ein durchwachsenes Jahr!
Mein privates „Ich“ hat letztes Jahr sehr viel Raum eingenommen und auch beruflich hat sich viel verändert.
Das heißt ich hatte generell wenig Zeit für mein online „Ich“ und wenn ich doch etwas Zeit hatte, war das Ergebnis meistens eher frustrierend.
I’ll have to revisit some of his work on OStatus and ActivityPub with respect to WordPress. It would be nice to be able to follow @email@example.com on Mastodon wouldn’t it?
Thanks, as always Pfefferle, for keeping the web open!
When will the government shutdown end? The bombshell Russia story from the New York Times: is Trump working for Russia?
Sen. Ted Cruz (R-Texas); Sen. Tim Kaine (D-Va.); former Sen. Claire McCaskill (D-Mo); roundtable discussion with Cornell Belcher, Al Cardenas (American Conservative Union), Carol Lee (Wall Street Journal) and Peggy Noonan (Wall Street Journal)
"sameAs":"http://www.imdb.com/title/tt0103396/". This feels reminiscent of the function of the microformats for u-syndication or rel-syndication which gives the folks at the network a trail to the copy of the data for the episode that they likely syndicated to imdb.com so that it’s findable there. Sadly, the URL link incorrectly points to a page for Dateline, so I’m not sure if their data is pointing to the right place, though it appears that the data for the episode on imdb.com is correct for this episode. It would also be nice if they were using the correct markup so that web parsers and crawlers would pick up the data properly.
The tougher part is that some of your post seems a bit misleading to me.
The couple of microformats related lines you’re adding in your child theme like
add_theme_support( ‘microformats2’ ); are in fact declaring that your theme properly supports microformats v1, v2, and microdata which it doesn’t quite. Those lines don’t actually add support (as the hook might indicate), but tell other WordPress plugins that your theme is microformats compatible which may prevent them from adding particular pieces of redundant microformats related code.
While you’ve got an
h-entry in your header file, you’re closing the related
</div> just after the title so that if the body of your post includes a
p-summary or an
e-content microformat, parsers are likely to have problems. Instead you might want to do something similar in either your
content.php (or other file that adds the body of your post) or your
footer.php files where you close that
div in one of those two files instead of in your
header.php file. If you need it the article page on the wiki has a simple example of what the final result should look like.
My favorite template for how to add microformats to a WordPress theme is David Shanske’s fork of the TwentySixteen theme. Because of GitHub’s interface and the fact that he made changes in relatively small increments, you can look at the history of his changes (start with the oldest ones and move forward) and see the highlights of what he added and removed in individual files to effect the necessary changes. (He made some other drastic changes like removing Post Formats in preference to Post Kinds as well as some other non-microformats changes, so you’ll necessarily want to skip those particular changes.) I think I learned more about WordPress Themes by going through this one example a change at a time than any of the books or tutorials I’ve ever seen.
If you need some help, feel free to catch one of the WordPress folks in the IndieWeb chat. I suspect that since you’ve got the fortitude to dive into the code the way you have, that you’ll be able to puzzle it out.