@w-sky – Appreciate the feedback, and we are moving to full block editor support by default in near future, that said block editor support has been there since Gutenberg first came out, just not on by default as our Shortcode UI is built on TinyMCE button bars and was much more refined for the time (still is compared to some of Gutenberg).
For that matter we are realistically editor agnostic. You can also use any page builder, shortcodes.
As for Gutenberg support not only can you edit popups, but you can also set any block or text on pages/posts to be a click trigger for any of our popups, just like making a link.
To enable editing popup go to Popup Maker -> Settings, there is a checkbox for that.
https://p60.tr2.n0.cdn.zight.com/items/4guGJjNp/8398e88c-248e-4a6c-a852-740dea772cad.png
Hopefully you will see we didn’t ignore it and reconsider your star rating. It just wasn’t a priority of our users, nor one of our own, in fact from usage tracking we know that less than 5% of our users are utilizing the block editor for popups, most opting for simple shortcodes or full page builders.
— General gutenberg opinions from WP product company —
Even as a dedicated WP company we are only just starting to truly adopt Gutenberg for editing beyond simple posts.
Even years into the block editor project, most agencies & site bulders are not using it, opting instead for modern page builders (Class/ID based styling rather than modules/elements, such as Bricks, Cicily etc), capable of producing complex designs without limiting you based on what settings fields are shown or some wonky post editing optimized interface.
As someone who has personally contributed to gutenberg, released packages built on top of it for other devs & generally been involved at every level of WordPress for the past 15 years, Gutenberg is a good step in the right direction, but far from the ultimate solution.
## Reasons its not a great investment for plugin companies:
- In its current state, and the state for the past 5 years for that matter, there are breaking changes, major UI/UX shifts, changes of general direction etc, that occur every few releases if not more often. This means it costs a heck of a lot more developer time to build and support products on top of it, and then rebuild those products over and over again with every breakage. No signs of stabilization any time soon.
- Finding or training developers to full proficiency is very time intensive. A small company with 1 developer and multiple products ?? having to constantly relearn because the changed the whole thing, is not something I should be wasting time on.
