Category: AI, Computation, and Technology

Gutenberg frustrated me because:

1. It takes seemingly endless time to load – Painfully endless. Sufferingly so.
2. It loses websocket connections if you sleep and wake your laptop, meaning you can either (a) lose your work or (b) can’t save your work.  There is no reason for this (my company’s applications restore websockets using the gmail incremental delay method, and it’s flawless).  And there doesn’t appear to be any way (from the admin interface) to see the frequency of saves (it should be every minute or three).
3. Blocks are a long time coming, and great for content presenters – but they’re terrible for content producers: writers. 

And, well, I’m a writer.  In fact, WordPress is quite possibly the optimum platform for writers – because of autosave, lots of versions, version history comparisons, WYSIWYG. I find it a better experience than every other editor I have.  

To “correct” the problem of the ‘hostility’ of Gutenberg Blocks for writers, add one plugin:

TinyMCE Advanced adds a “Classic Paragraph” block for the block editor (Gutenberg).  This classic paragraph block maintains the distraction-free writing experience. And the advanced configuration allows you to customize your editing by setting advanced TinyMCE options for both the classic block and classic editor.

The Classic Paragraph Block can be used instead of the Gutenberg Paragraph Block. And it supports transforming to and from (converting between) multiple Paragraph blocks, Image, Table, List, Quote, Custom HTML, and most other blocks.

 One of the Options is to set the Classic Paragraph Block as the Default Paragraph. Set it. Then you’re done. You have the best of both world for content, whether PRODUCING(writing) or PRESENTING.

Gutenberg frustrated me because:

1. It takes seemingly endless time to load – Painfully endless. Sufferingly so.
2. It loses websocket connections if you sleep and wake your laptop, meaning you can either (a) lose your work or (b) can’t save your work.  There is no reason for this (my company’s applications restore websockets using the gmail incremental delay method, and it’s flawless).  And there doesn’t appear to be any way (from the admin interface) to see the frequency of saves (it should be every minute or three).
3. Blocks are a long time coming, and great for content presenters – but they’re terrible for content producers: writers. 

And, well, I’m a writer.  In fact, WordPress is quite possibly the optimum platform for writers – because of autosave, lots of versions, version history comparisons, WYSIWYG. I find it a better experience than every other editor I have.  

To “correct” the problem of the ‘hostility’ of Gutenberg Blocks for writers, add one plugin:

TinyMCE Advanced adds a “Classic Paragraph” block for the block editor (Gutenberg).  This classic paragraph block maintains the distraction-free writing experience. And the advanced configuration allows you to customize your editing by setting advanced TinyMCE options for both the classic block and classic editor.

The Classic Paragraph Block can be used instead of the Gutenberg Paragraph Block. And it supports transforming to and from (converting between) multiple Paragraph blocks, Image, Table, List, Quote, Custom HTML, and most other blocks.

 One of the Options is to set the Classic Paragraph Block as the Default Paragraph. Set it. Then you’re done. You have the best of both world for content, whether PRODUCING(writing) or PRESENTING.