Making Progress on Jekyll-IndieWeb v2

I’ve been working on v2 of Jekyll-indieweb and the main change is that its a gem based theme. What was holding me back for a long time was that only whitelisted theme gems were allowed on GitHub Pages, with no clear path to how a theme could get whitelisted. Then I found Jekyll Remote Theme from @benbalter. I hadn’t actually tested it, but I went on faith. Lo and behold today I was successfully able to set up a new gh-pages project by using the public repo of jekyll-indieweb.

There are plently of bug fixes and tweaks and most importantly, documentation before an official release. But to get there faster, I’ll be quickly switching over to blogging at which will be running on GitHub Pages.

I intend to fully document how to have a complete IndieWeb site running with the different microservices and a GitHub Pages hosted Jekyll site. I now believe a lot of it can be done without complicated CI tools as I’ve done in the past, but it will be a fun journey.

From there I want to explore using the templates with Eleventy as planned. Though I thought I was going to jump right into Elventy for my own site, I ran into some configuration headaches and went with the more familiar tool.

WordPress isn’t on the current roadmap but at some point I’d like to circle back & look at Gutenberg blocks. WIth the recent release of Advanced Custom Fields, I think you could use the existing table structure for post kinds and re-create the kinds as blocks without having to Learn the New Way™ ¯_(ツ)_/¯

Anyway, this will probably one of the last ever posts on which feels a little weird to type. But onward…

As always, progress can be tracked in the repo. All suggestions welcome.

turns out™ if you add the global $post object and add $title == $post->post_title then it will not target the other titles on the page that use the filter

Had to see it for myself but you can not filter the_title without titles in page navigation also picking up that filter. I only want to add a class to the actual title of the content.

Homebrew Website Club: One Year In

Jonathan outlines a path very similar to my own journey from static site generator to WordPress with the added plan of helping grow the IndieWeb WordPress ecosystem. 6 months into my WP IndieWeb journey I have some thoughts I should write about, both about the WP ecosystem as well as my own plans for this domain.

Homebrew Website Club: One Year In (

However, I started to eventually hit a bit of a wall: when I was faced with limited time I was constantly needing to evaluate whether to spend my time learning the tool (Hugo/Golang) and wanting to create content. I had the ideas and knew what I wanted to create, and even started several series of articles on my previous site, but when I would start pushing out blog posts I wouldn’t be working on implementing necessary features to my site.