Birgit Pauli-Haack

Hmm, you might be able to do it via “Customize > Additional CSS” if you know a little CSS. How did you create the form? Might be a plugin forms builder? Is this on a public page?

There is a lot of things going on in your blog post above, very interesting points of view. The architecture and foundation of the block probably won’t change, though. It’s the method of choice to store relevant information in the post_content now.

Most of your enhancement ideas might be best discussed directly with the Gutenberg developers via GitHub. I want to encourage you to contribute your views in already happening discussions there, and create new feature requests.

To manage expectation on Code Editor enhancements. the WYIWYG editor is the main focus of the team right now, and bug fixing compatibility and UX issues. It’s worth a try, what’s the worst that can happen, right?

The biggest drawback from shortcode is,content lock-in. If you have a Theme and also installs a page builder and then you want to switch to a different Theme you are left with a shortcode mess and potential loss of content. Gutenberg definitely aims to make it attractive for plugin developers to move away from shortcodes.

Divi has its own way how it will handle integration with Gutenberg. Nick Roach just published an introductory blog post

Hi there again!
Shortcodes are a bit different than the method how Gutenberg blocks store content. The HTML comments don’t show up once the block is rendered in the browser and their use reflect the human readable over machine readable.
A detailed explanation is available in the FAQ section of the handbook.

Yes, the novelty of the interface, the block borders and ‘things’ showing up on mouse over, can be distracting and gets you right out of your workflow. We read and heard similar comments. I also had a similar experience when I first started using it.

If you are up for another experiment, you could try to use the Classic block. It’s available as a standard block from the block selection. Once you use it more often it’ll be in the top section. Alternatively, where is now says, “Write your story” type “/cla” to call up the classic block from the list.
Using the slash “/” command + Classic block might get you close to the old editor experience with the benefits of Gutenberg. Let me know how it goes….

A while = probably years after WordPress 5.0 the release.

The whole Classic Editor topic has multiple layers. I try to explain, but I might just muddy the water even more 🙂

Part of it is that most decision on how Gutenberg is merged into core have not been made yet. That’s what the so-called ‘merge proposal’ is for.

1)There is a Classic Editor Block within Gutenberg = always available.

2)There is a Classic Editor plugin, which is created to provide a transition tool to install before WordPress 5.0 is released for sites that are not ready for Gutenberg. No decision is made how long this will be available. Hence the ‘A While’ comment. I have seen estimates up to two or three years. Others say it will be available as long as people need it. Indefinitely is also a variation, however that’s not likely. Everything comes to an end eventually.

3)Then there are fallbacks when plugins or custom blocks are not compatible with Gutenberg, then it will automatically fallback to the Classic Editor, that feature is backed into Gutenberg.

The Gutenberg team goes through great length to make the transition as smooth as humanly possible.

And just to make sure we cover this, too. No one forces you to use Gutenberg. You have plenty of options:
– Install Classic Editor
– Install Gutenberg Ramp
– Don’t upgrade to WordPress 5.0

WordPress 5.0 won’t be an automatic update.
The core team applies security patches/update back to version 3.7, which was released October 2013.
You would also not be in bad company: Roughly 40% of WordPress sites are still on version prior to 4.9 (released 11/2017)

Cheerio!

Hi there! Thanks for leaving a review.

Gary Pendergast actually published a great code example how a plugin developer could convert shortcodes to blocks fairly easily. Might be a better place to start for you.

Another constructive way would be to file a github issue, on the plugins incompatibility to get assistance from the Gutenberg team.

Hi there, it’s good you left a review on a plugin.

The purpose of the “Try Gutenberg” prompt was do get more feedback to make Gutenberg better for a larger audience.

It would help if you could add which part of Gutenberg didn’t work as expected that made your reject Gutenberg outright?

• This reply was modified 7 years, 8 months ago by Birgit Pauli-Haack.

That’s not much of a review. Would you mind elaborating? The purpose of the “Try Gutenberg” prompt was do get more feedback to make Gutenberg better for a larger audience. If you get a minute, I’d like to find out more why you think the old editor is better than Gutenberg, beyond, that you don’t like to change the way things work.