- This topic has 6 replies, 2 voices, and was last updated 4 years, 2 months ago by
.
-
Posts
-
After extensive user testing with my clients, a solid 92% strongly dislike trying to use blocks. While I completely understand the rationale behind moving toward them, deprecating sections and forcing users toward Guttenberg is such a negative prospect, I’m actually considering ditching WordPress entirely unless there’s something else that can be done.
Add to this, I have over 100 clients with 1-5 content managers per organization and manually converting thousands of posts of user content only pushes toward the direction of using a different platform entirely.
Are there any plans to address this other than telling end users they have no choice but to change?
Lead Developer
Hi there,
This wasn’t an easy decision, but it is a necessary one, unfortunately. The classic editor itself will no longer be supported by WordPress at the end of this year: https://make.wordpress.org/core/2018/11/07/classic-editor-plugin-support-window/
Sections depends on the classic editor, and we don’t feel comfortable continuing to offer a feature that may not remain stable far into the future.
If you need to keep using it, you can always use a filter to “overwrite” our decision: https://docs.generatepress.com/article/sections-overview/#deprecated
However, it’s important to keep in mind that it’s something that may break in the future if WordPress decides to change/remove TinyMCE.
When I built Sections, WordPress desperately needed a way to break out of the classic editor to allow more customization and better design. That simply isn’t the case anymore – the Group block or the Container block in GenerateBlocks are vastly superior. There is, of course, a learning curve. I understand that it can be difficult to “force” a switch on a client who’s used to the Classic editor. That’s why we included the filter I linked to, but it does come with risks.
Moving forward, we simply don’t have the resources to maintain something like Sections if the foundation of it (the classic editor) is no longer supported.
Thanks tom, I appreciate the reply. Is there any potential for some sort of migration tool. Manually converting user sites will be hundreds of hours of work. And really, at this point if that’s what it requires and providers are forced to eat 100% of those costs (or pass them along to clients) then it’s time to consider ditching WordPress entirely.
Everyone knew WP needed change, that was no secret. But the direction they’ve gone with blocks (which still aren’t fully WCAG compliant!) is as bad as Google Analytics 4 updates. It’s produced a product so bad and so user unfriendly to the very people it appealed to, there’s no future in it as a developer.
Are you wanting some sort of migration tool from Sections to the block editor, or to something entirely different?
While I agree that the block editor isn’t perfect, I feel like it’s a pretty impressive addition to WordPress. I know the developers are actively working on accessibility and improving usability every day. Compared to other site/page builders I’ve used, I prefer the block editor.
My bad, that was rather unclear but yes, having a migration tool to go from Sections to Blocks will be a large part of the overall decision making on my end. I can’t speak for other users but I have to imagine it will be an enormously valuable asset to at least replicate existing layouts.
The WCAG compliance issue is a serious problem in my sector. Nonprofits are getting hammered with BS lawsuits that pull in dozens of organizations per suit because they know they’re easy targets to bully. Having a platform that openly acknowledges it isn’t compliant only increases that risk.
Cool, I’ll take a look at what would be involved there. Definitely a good idea.
I know they’re actively working on a11y issues. Compared to many page builders, it’s very good when it comes to a11y. I know it’s difficult to ever reach full compliance, but they’re definitely trying.
Thank you Tom, I sincerely appreciate it. As many conversion tools as possible for sections and header elements make all the difference.
- You must be logged in to reply to this topic.
