Gutenberg Archives - herb miller

Apostrophes

It s a cryin shame.
It s really not that fair.
I ve this need for apostrophes,
but there isn t one to spare.

I ll find a way around it.
They re easy to replace.
Just use the missing letters
that used to take their place.

If you use the rules
it s not that hard to see
when you could ve used one
or where it shouldn t be.

I m sure that readers everywhere
will appreciate your time
eradicating excess ones
from each and every line.

And then there ll be some spare ones
so I can help you see
a proper use for the single quote;
as an a'p'os tro'phe.

To see the missing letters, hover over the space where the apostrophe might have been.

Notes

When you’re writing HTML an apostrophe can be represented by:

' which may appear as '

or

’ which may appear as ’ – right single quotation mark

aka a curly closing single quote.

See Wikipedia for more information on Apostrophes, especially those showing omission.

when using WordPress

When using the Gutenberg block editor, the chance of ‘ making a round trip and reappearing as ‘ in the editor is pretty slim.
It gets converted to the character you may have wanted.
Sometimes an apostrophe gets converted to a left single quotation mark.
This is due to texturisation logic trying to match left and right single quotation marks.
Gor blimey guv’nor, that’s what’s ‘appen’d ‘ere.

My Favourite Block – annotated

My Favourite Block, by Herb Miller. Annotated with the WordPress blocks used and a screen capture of each block in the editor.

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29

My Favourite Block

A poem about Gutenberg blocks for the new block editor.

WordPress 5.0, Gutenberg and the Classic Editor – what did you expect?

Well that was a fuck up!

I’ve heard reports that the Classic Editor plugin was updated just a few hours before WordPress 5.0 was released and now there’s a completely different user experience.

The ability to easily choose the editor to create your content has disappeared. For me, that was the whole reason for having the plugin. Some things don’t work in Gutenberg / 5.0 so I need the ability to use both.

I don’t think the use cases for the Classic Editor and Gutenberg and WordPress version combinations have been thought through. I know that I am going to continue to want to use both Gutenberg and the Classic editor under WordPress 5.0. And I need the ability to easily select my preferred editor. That’s how it was with 0.5. It’s how I tested my sites’ compatibility.

You don’t bugger about with something hours before a release. You give people a chance to test it.

Lessons need to be learned. WordPress 5.0 release should have been delayed until:

v1.0 of the Classic Editor had been tested with Gutenberg 4.6.1 and WordPress 4.9.8 & 5.0-RC3.
User documentation was ready.
The host of issues starting with #4855 had been addressed.

Fortunately, I haven’t yet upgraded anything yet. I will be testing Classic Editor v1.1 very carefully.

oik-block – Gut feel revisited

Back in April I was developing a prototype plugin called oik-block that contained a number of prototype Gutenberg blocks plus a whole load of code that helped me to form opinions regarding Gutenberg’s compatibility with my sites and to estimate the code of migrating to Gutenberg and/or WordPress 5.0. I’ve recently forked oik-block to create a new plugin called oik-blocks. Here’s an update.