WordPress | Chris Aldrich

Dividing and Conquering the IndieWeb Related Content on My Website

Both for my own benefit as well as for that of others who may be following along, I realize that I’ve been tagging a lot of material on my site with the broad category of “IndieWeb”. Some of it is definitely more significant and content rich than others, but in aggregate it may often seem like a firehose. If you’re following the community relatively closely already, you’ll probably be seeing a lot of redundant material.

As a result, and since it’s easy to do, I’m only going to categorize a much smaller segment of the richer material that I write or which is I deem to be extremely broadly appealing with the IndieWeb category. The remainder of smaller pieces by others, bookmarks, short replies, or other tangential related things (UX, UI, silos, silo quits, etc.) I’m going to use the alternate and separate IndieWeb tag.

Thus if you’re active in the IndieWeb community and only want my IndieWeb related materials then follow the category and not the tag. If you’re not closely following the community and want everything then I recommend following the content from both the category and the tag.

With the subtle change this may also help IndieWeb related planets like Aaron Parecki’s https://stream.indieweb.org/ or Malcolm Blaney’s https://unicyclic.com/indieweb/ pick up relevant data without needing to do heavy de-duplication for fear of spamming various channels.

In the coming days/weeks I’ll try to go back into my backlog of posts and re-categorize and re-tag things based on this general scheme.

My direct content:
Category Only | feed: https://boffosocko.com/category/indieweb/feed/

Miscellaneous bookmarks, replies, other content I collect for my commonplace book, etc:
Tag Only | feed: https://boffosocko.com/tag/indieweb/feed/

The firehose of everything IndieWeb related from my site:
Category AND/OR Tag | feed: https://boffosocko.com/?s=indieweb&feed=rss2

And of course I still try to aggregate and orient most of the important pieces in my IndieWeb Collection.

An IndieWeb Podcast: Episode 13 Lacking a Theme

Episode 13: Lacking a Theme

Running time: 1h 25m 29s | Download (25.5MB) | Subscribe by RSS |

Huffduff

Summary: David Shanske and I reunite for the first episode of 2019. Special apologies to Jeremy Cherfas, as the recording equipment was not working to specifications this week.

Recorded: January 2019

Shownotes

👓 4 Reasons @GetClassicPress Should Add Native Microformats Support | Greg McVerry

Read 4 Reasons @GetClassicPress Should Add Native Microformats Support by

Greg McVerry (quickthoughts.jgregorymcverry.com)

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...

👓 twenty eighteen | Matthias Pfefferle

Read zwanzigachtzehn by

Matthias Pfefferle (notiz.Blog)

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.

My German is atrocious, but it’s well worth stumbling through to see what Matthias is up to lately, particularly with regard to his work on the IndieWeb.

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 @chrisaldrich on Mastodon wouldn’t it?

Thanks, as always Pfefferle, for keeping the web open!

👓 Everything Old is New Again: Adventures in the IndieWeb | Desert of My Real Life

Replied to Everything Old is New Again: Adventures in the IndieWeb by

Cathie LeBlanc (Desert of My Real Life)

I’ve written about my forays into the IndieWeb movement before. I have even written about how I feel like I’m moving to a philosophy of sharing my work that is kind of old school. Last week, I had the occasion to see a perfect example of how the “new” ways that I’m working are actually the old ways.

Kudos Cathie for rolling up your sleeves and delving in like this! You’re getting some fairly solid results and have far stronger grasp of what is going on than I certainly did in my first year–not to say that I’m much better off now to be honest.

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.

Another tool in addition to indiewebify.me is the Pin13 parser which will parse your page and give you some indication about what it is finding (or not) and how things are being nested (or not).

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.

📺 Finding things in WordPress core with GitHub and Grep | YouTube

Watched Finding things in WordPress core with GitHub and Grep by

Ross Wintle from YouTube

A short video on using tools to search the WordPress core code for filters and actions. Tips and tricks for WordPress development with Github and grep.

A short and useful little tutorial. It’s small stepping stones like these that can lead you down the primrose path of some additional serious hacking.

hat tip: John Johnson