WP Tavern › Forums › Create Topic
Steve Grant I was excited for Gutenberg (way) back when I thought it was going to be a quick frontend editor, because my clients do often need to fix typos on the front-end, without the perils of a pagebuilder. But NOW I can see Gutenberg threatens my whole business. Its focus on “article writing” is detrimental to my work. Most of my work in WP for clients has been to make them each a plugin suite which adds CPTs, taxonomies etc and a huge huge bunch of bespoke metaboxes . EG Client/Job: a rental agency site needs a feature for editors to fill a standardised form to populate a property listing and link to geodata and offline systems. I spec and build a plugin suite to do this, but the metaboxes here won’t include the standard “editor” but will include many repeatable group boxes for editing segments, with custom boxes which call from other CPT posts and taxonomic queries, etc. Large complex metabox based solutions displayed in the primary post editing area. For my clients, “writing articles in wordpress” is 0.1% of why they use it. What I see from Gutenberg is no support for my practice. All metaboxes in a sidebar! No consideration for the non-blogging client, no indication of a path for a developer relying on the metabox model. So, what happens to me with WP5.0 ? All my clients want their 4 year old sites fixing for free? The onus is on me to deliver a fix, so am I recoding from scratch? Where are the WP official guidelines to deliver a familiar and equivalent UI? Where is the statement on legacy support? How are the big players such as woocommerce going to implement this, I’d be fascinated to see, because I’m looking at a massive problem here with no solution. Untill I see firm advice for people with my business-model (developing bespoke plugins for Business functions) I will be sticking on WP 4.9 and migrating away from WP as a platform. I am disapointed, and dismayed by what I have seen.
Steve Grant
I was excited for Gutenberg (way) back when I thought it was going to be a quick frontend editor, because my clients do often need to fix typos on the front-end, without the perils of a pagebuilder.
But NOW I can see Gutenberg threatens my whole business. Its focus on “article writing” is detrimental to my work.
Most of my work in WP for clients has been to make them each a plugin suite which adds CPTs, taxonomies etc and a huge huge bunch of bespoke metaboxes .
EG Client/Job: a rental agency site needs a feature for editors to fill a standardised form to populate a property listing and link to geodata and offline systems. I spec and build a plugin suite to do this, but the metaboxes here won’t include the standard “editor” but will include many repeatable group boxes for editing segments, with custom boxes which call from other CPT posts and taxonomic queries, etc. Large complex metabox based solutions displayed in the primary post editing area. For my clients, “writing articles in wordpress” is 0.1% of why they use it.
What I see from Gutenberg is no support for my practice. All metaboxes in a sidebar! No consideration for the non-blogging client, no indication of a path for a developer relying on the metabox model.
So, what happens to me with WP5.0 ? All my clients want their 4 year old sites fixing for free? The onus is on me to deliver a fix, so am I recoding from scratch? Where are the WP official guidelines to deliver a familiar and equivalent UI? Where is the statement on legacy support?
How are the big players such as woocommerce going to implement this, I’d be fascinated to see, because I’m looking at a massive problem here with no solution.
Untill I see firm advice for people with my business-model (developing bespoke plugins for Business functions) I will be sticking on WP 4.9 and migrating away from WP as a platform.
I am disapointed, and dismayed by what I have seen.
Name *
Email *
Website:
Topic Title (Maximum Length: 80):
Forum: — No forum —AI and WordPress Articles Blocks Showcase Discussions Events Introductions Jobs and Working in WordPress Podcast Episodes Site and Block Editor
Enter your email address to subscribe to this blog and receive notifications of new posts by email.
Email Address
Submit
Enter the destination URL
Or link to existing content
