Migrating an existing site to Gutenberg, day 4, first note: John and I spent a considerable amount of time fighting with, and swearing at, the Bitnami install script for WordPress.

John’s is working right now but I’m about to go through my fourth reinstall of actual Xampp because when you attempt an uninstall of the WordPress module it doesn’t clean up after itself so you have to nuke the whole thing and start over.

Once I figure this out, (I have an idea what the problem is and it has a lot to do with unlabled fields with placeholders that you can’t easily edit), I’ll start writing down all the dumb stuff you have to do with the keyboard and your screen reader to make this work.

And it’s a lot of dumb stuff.

And we’ll also walk through removing the several plugins that get installed with this thing so you can get back to an actual out of the box WordPress installation.

I absolutely despise install scripts that install a bunch of third-party plugins without asking me first. Extra points taken away if they’re plugins I’ll never use or actively go out of my way to remove wherever I find them.

We’re still going to do the manual install as well but now I’m livid at this script and its stupidity and I keep telling myself we’ll eventually get to actual block development.

Migrating an existing site to Gutenberg, day 3, second note, this one’s shorter.

As I was writing the last note and attempting to add a code snippet, I inwardly groaned at the task of converting all the quotes and other characters into their appropriate character entities, until I remembered that I have Justin Tadlock’s old-but-still-working-just-fine code snippets plugin installed.

Nice, accessible modal for adding code snippets, generates a shortcode for the post.

So it’s coming along with me as we make this migration because the Gutenberg code block would have to be absolutely amazing to get me to switch to it for my code snippet needs at this point.

So Justin’s code snippets plugin is added to the list of plugins that will need to be redone for a Gutenberg world and I will be more than happy to do it myself because I am not giving it up.

Migrating an existing site to Gutenberg, day 3, first note: This is a long one.

John figured out that you can right-click on the button on the Bitnami page and download your preferred app installation package that way. I looked at the source code for the page and the reason the links for downloads present as buttons is because of this gem: [snippet slug=this-one-weird-trick-to-override-native-anchor-behavior-to-make-it-a-button-with-aria lang=html]Somebody needs to have a talk with the Bitnami people about their Aria flare, because they’ve given the links the role of button, which There are some free WordCamp talks on how to use ARIA properly as well as on how roles work, and plenty of articles written by accessibility experts on ARIA roles and on top of that some courses.

Admittedly I didn’t think to try the right-click-on-the-button trick yesterday when I was fighting with it because I still haven’t managed to wrap my brain around the why of the stupid developer trick of changing the role of a perfectly-working anchor element via ARIA when if you really wanted the thing to be a button you could have made an actual button or even styled the thing to look like a button while still making sure it actually works.

But OK, on to the other bits.

Download the file, and then press enter on it once Xampp is running, and this is where things got weirder.

john got the fields filled in for the Bitnami script, (or at least he thought he did), and got the WordPress installation up and running, only to find that he couldn’t log in and couldn’t reset username and password because the email entry apparently didn’t take.

He fought with it for something like thirty minutes using various bits of Jaws magic, and then finally decided to wait to get the assistance of a sighted person to figure out where things went sideways.

I’ve decided to skip the whole thing and just do a manual install, which I will get to tomorrow. I’m not interested with putting more time into a script for a quicker install than an actual manual install would take.

If John can figure out what the problem is then we’ll write the whole thing up and publish it as a tutorial for those who use screen readers and don’t want to do manual WordPress installs. I’m of the opinion that this is merely putting off the inevitable because when it comes to installing various javascript tools for development or PHP or whatever the command line will become unavoidable, but we’ll offer the option.

Migrating an existing site to Gutenberg, day 2, second note. I got Xampp running, and am attempting to use Bitnami to install WordPress. The Bitnami page runs better in NVDA than it does in Jaws, but the download still won’t start, so we’ll be installing this manually.

I’m going to download all the necessary stuff so that John can avoid the surprise of trying to use Bitnami with Jaws and Firefox.

You can’t tab through the page, and updating the virtual buffer is a no-go.

Even in NVDA, once you select a download, you can’t tab through the page.

Might have to see if there’s another way to do this.

Migrating an existing site to Gutenberg, day 2, first note:

This is day 2 because I ended up not working on this on Thursday and Friday of last week. I’m back at it today though.

And today’s first task: Fighting with Xampp on Windows.

I was thinking about attempting this with Desktop Server since it’s already installed, but since we’re doing the Gutenberg thing may as well do it properly with no shortcuts.

So far I have it installed but am having difficulty getting it running, (user account control appears to be the bane of my existence), but will keep trying and hopefully will have something to say once it’s running properly.

Next is installing all the tools.

53 Resources for Developers & Designers building Blocks for Gutenberg by Birgit Pauli-Haack (Gutenberg Times)
There has been an increase in developer resources around Gutenberg. We collected quite a few here. We’ll update along the way.

This resource from Gutenberg Times looks like it might be a great place to begin with Gutenberg development.

Development note: for the purposes of being able to remember gotchas when developing, I’ve added this development note with this bookmark.

While I’m not sure if this is a function of Gutenberg or not, I needed to manually input the information for the post name but not post excerpt, and I needed to manually input the site name. All of this applies when attempting to parse the information from the URL, which uses the “Parse This” portion of the Post Kinds plugin. This may mean something to look at specifically when migrating that plugin.

Migrating an existing site to Gutenberg, day 1, first note: I’m trying to catch up on the latest with what’s going on regarding Gutenberg, and I can’t help but notice all the noise.

This could be a function of my social media curation, or it could be a function of there really being a lot of noise out there, or it could be a little bit of both.

I’m going to see if I can find some sort of roadmap, although I may need to create one myself.

One final note for this evening.

I’m trying to get John to agree to participate in screen share recordings via Zoom of this process. I figure if we’re doing this whole migration thing, and it’s his idea, he can participate in the work.

I also told him that this is the fluffy bunny stuff he has to do for marketing.

I think he’s still in get-off-my-lawn mode but I’m sure he’ll come around.

First thing’s first. Let’s find some books.

I have a few on React, but I want to make sure there are some absolute beginner resources. So I load yee old QRead, and

I have to re-enter Bookshare credentials because, (on this computer), books stored in QRead periodically get wiped along with credentials.

This is annoying, but I’m used to is, so I’ll get those re-entered and then search Bookshare for appropriate books.


Amanda wearing a blue knit cap

I’m spending Contributor day working on some accessibility fixes to the Indieweb Publisher theme, which I will submit as a pull request when done because I need some easy wins if the WordPress accessibility fight is going to continue.

I’m also celebrating Blue Beanie Day early because every day is a good day for web standards.

In short, WordPress.com would need to support at least two of the Indieweb building blocks: Webmention and full Microformats 2. See all the building blocks at the first link.

In order for WordPress.com to be a turnkey solution, it’ll need to support these things out of the box, and make it as simple as checking some boxes, or better yet, turn them all on for everybody by stealth.

part of this involves themes, and for the time being users either have to install a plugin like MF2 from the WordPress repository which will try to programmatically add Microformats 2 to a theme, or choose a theme that has full Microformats 2 support already baked in, or manually add them to a theme themselves.

I’m not saying WordPress.com couldn’t do this, (I’d love it if they did, and if they became a turnkey solution for people who want to join the Indieweb), but I don’t see that happening any time soon.