via wpjohnny.com => original post link
A looking-back at the highly speculated (and shocking) announcement of CWICLY’s sudden abandonment in the past week.
It was a shock to many WordPress developer circles because of how personal it felt to everyone. Whether or not you’ve even tried CWICLY, a modern Gutenberg pagebuilder only several years old, you could still relate to its personal challenge in today’s WordPress workflow. One of wrestling between pagebuilders and Gutenberg, and page load and page scores. An elusive (if not mythical) balance hunted for by all WordPress developers.
CWICLY was trying to do what we were all trying to do…make sense of WordPress’ most recent evolution into Gutenberg. It had evolved to a point to where it was almost no longer the same platform we had started with years prior.