This spring E took down her WordPress blog and replaced it with a static website. In the past weeks she did the same for her business website (and added her own sales channel to it, with just the payment provider as third party element).
Now I have static website envy. Until 2002 I had static websites, hand coded in a text editor. Still the easiest way for simple websites, I’m amazed to say. Then from 2003 I used a CMS for my blog, first Movable Type for about a decade and then WordPress from 2012 until today, and ran some Drupal based websites alongside it.

On many occasions using a CMS, I have thought about providing the actual web pages as static html. Because it is so very fast to load. And for most of this blog here, the only reason to have a CMS is back-end related. A CMS makes it easy to maintain consistency, create lists of posts or pages from whatever criteria, quickly change looks and lay-out, manage menu options, etc. All those dynamics mostly are aimed towards me, to make it easier to post something. But the same dynamics is then used to present a web page to you. Even if for almost anything on this site that is not needed, because the content itself is static. So why isn’t the site?

I’d rather cut the machinery to make a posting or site from the resulting posting and site. The machinery then can sit on my local device, and the results can live on a web server. It makes the website less vulnerable as well, not just faster.
That’s what static site generators mostly do, the machinery locally with the content in some repository, after which a script transforms it into static web pages and places them online.

Having seen E make this change, gives me static website envy.

There are some things to consider before starting a project like that. There are some interactive aspects of this site that I need to keep working. Sending and receiving Webmentions, and allowing comments for instance. On the back-end I want to be able to keep posting through micropub, so that like now I can post from within my feedreader or my local notes directly to my site.

Favorited link rel="alternate" type="text/plain" by Terence Eden

This is nice, providing a way to serve every posting in a WordPress site as plain text. Useful for faster load times, but also as a way to more easily pipe a posting into some other script as HTML is already stripped. I think I want to play around with this option. Full template and set-up at his GitLab page.

Simply append .txt to the URl of any page and you’ll get back the contents in plain UTF-8 text. No formatting, no images (although you can see the alt text), no nothing!

Terence Eden

It seems using Micropub to publish to a Gutenberg WordPress site no longer works. For my company’s site, where we use Gutenberg, pushing a new blogpost through Micropub now causes a fatal error and lets the site crash. Removing the offending post fixes it. May well have to do with our use of other plugins for page design (such as Avada). It doesn’t seem like the IndieWeb MicroPub plugin is getting a lot of attention (not a criticism, just an observation). On my own blog, where I don’t use Gutenberg everything’s fine.

I use MicroPub to publish directly from within my local markdown notes, which reduces friction to write quite a bit. Having to write or copy paste stuff into the WP back-end is something I’d rather avoid.

Bookmarked WordPress AI: Generative Content & Blocks (by Joe Hoyle, found via Chuck Grimmett)

As many others I am fascinated by what generative algorithms like ChatGPT for texts and Stable Diffusion for images can do. Particularly I find it fascinating to explore what it might do if embedded in my own workflows, or how it might change my workflows. So the link above showing an integration of ChatGPT in WordPress’ Gutenberg block editor drew my attention.

The accompanying video shows a mix of two features. First having ChatGPT generate some text, or actually a table with specific data, and having ChatGPT in ‘co-pilot’ style generate code for Gutenberg blocks. I think the latter might be actually useful, as I’ve seen generative AI put to good use in that area. The former, having ChatGPT write part of your posting is clearly not advisable. And the video shows it too, although the authors don’t point it out or haven’t reflected on the fact that ChatGPT is not a search engine but geared to coming up with plausible stuff without being aware of its actual information (the contrast with generating code is that code is much more highly structured in itself so probabilities collapse easier to the same outcome).

The blogpost in the video is made by generating a list of lunar missions, and then turning them into a table, adding their budgets and sorting them chronologically. This looks very cool in the vid, but some things jump out as not ok. Results jump around the table for instance: Apollo 13 moves from 1970 to 2013 and changes budget. See image below. None of the listed budgets for Apollo missions, nor their total, match up with the detailed costs overview of Apollo missions (GoogleDocs spreadsheet). The budget column being imaginary and the table rows jumping around makes the result entirely unfit for usage of course. It also isn’t a useful prompt: needing to fact check every table field is likely more effort and less motivating than researching the table yourself from actual online resources directly.

It looks incredibly cool ‘see me writing a blogpost by merely typing in my wishes, and the work being done instantly’, and there are definitely times I’d wish that to be possible. To translate a mere idea or thought into some output directly however means I’d skip confronting such an idea with reality, with counter arguments etc. Most of my ideas only look cool inside my head, and need serious change to be sensibly made manifest in the world outside my head. This video is a bit like that, an idea that looks cool in one’s head but is great rubbish in practice. ChatGPT is hallucinating factoids and can’t be trusted to create your output. Using it in the context of discovery (as opposed to the justification context of your output such as in this video) is possible and potentially useful. However this integration within the Gutenberg writing back-end of WordPress puts you in the output context directly so it leads you to believe the generated plausible rubbish is output and not just prompting fodder for your writing. ‘Human made’ is misleading you with this video, and I wouldn’t be surprised if they’re misleading themselves as well. A bit like staging the ‘saw someone in half and put them together again’ magician’s trick in an operating room and inviting surgeons to re-imagine their work.

Taking a native-first approach to integrating generative AI into WordPress, we’ve been experimenting with approaches to a “WordPress Copilot” that can “speak” Gutenberg / block-editor.

Copy-pasting paragraphs between ChatGPT and WordPress only goes so far, while having the tools directly embedded in the editor … open up a world of possibilities and productivity wins…

Joe Hoyle


An android robot is filling out a table listing Apollo missions on a whiteboard, generated image using Midjourney

Ik zag (op Twitter, jawel) dat de video van mijn presentatie op WordCamp Netherlands van afgelopen september is gepubliceerd. De video heb ik aan de presentatie toegevoegd, maar zie je ook hieronder.

Op WordCamp NL deed ik een oproep om standaard microformats en webmention in WordPress core, blocks en themes te ondersteunen zodat de 40% van het web die op WordPress draait ineens ook betekenisvol met elkaar kan verbinden: “WordPress sites tot IndieWeb alleskunners maken”.


Bookmarked What IndieBlocks Does, and Why by Jan Boddez

I really need to start testing Jan’s IndieBlocks plugin, to see if it allows me to switch to WordPress Gutenberg. If yes, I think it will allow me to also do a few things with my site to make it less blog-centric. Because from what I’ve seen from E’s work on my company’s site, Gutenberg makes that easier than writing a theme from more or less scratch which I’ve been balking at for some time, aka 2 years.

I probably will need to set-up one of my test WP sites (nicknamed proto and meso) with IndieBlocks. A key thing to test will be if interacting with the site through my Micropub client(s) needs to be changed. I now push everything into a raw html text that gets submitted to the site, and I don’t know in what ways that would need to be different in Gutenberg blocks, and how it might change how I need to talk to the micropub end-point.

Because nearly everything in IndieBlocks is configurable, it will be possible to keep using the other IndieWeb plugins beside it. Simply disable the bits you don’t need!

Jan Boddez