-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Give categories a full gutenberg editor #37746
Comments
Hi, Thanks for reporting and all of the detailed pictures and clear use case :) Please reopen if I'm misunderstanding and you're looking for something different than in #17099 |
Hi, just to jump in here - we have a plugin that lets you customize a block theme woocommerce category pages - https://www.pootlepress.com/storefront-blocks/ We updated it last month so it works with block themes and fse - there's an explanation here https://youtu.be/V0uWuXXOjr4. |
A native solution would definitely be appreciated. I tried the Storefront Blocks plugin as mentioned in an above comment, as part of their Blocks bundle, and it was one of the worst WordPress experiences I've had in years. It was full of bugs, barely worked with classic themes, and after a year of no updates they forced a paid renewal without any notice. Support didn't respond once to any requests. It's not a good option here. Regardless, the plugin's solution was to simply map a category to a regular page with a redirect. It doesn't actually add the Gutenberg editor to the categories themselves. That's not a good approach because it introduces 301s into regular navigation, and requires two URLs to maintain. A real upgrade to category pages is needed. I understand there's some issues in how the data is currently stored in the backend, but modifying the schema should be possible. Categories are an important part of many website's designs - especially on eCommerce sites where they tie together different products. More than just enabling Gutenberg, I would also expect category pages to work in contexts like query loops to pull in all relevant posts/products. Certainly WooCommerce Blocks could make use of that functionality as well. It would also be useful if the standard loop could be disabled so that custom loops could be used instead. While it's possible this could be detected heuristically (eg. is a query loop in use?), I think an actual checkbox would be more explicit and easier to reason about. If the question is, "Why even use a category page at that point"? It's because it's more semantic, better organized in the backend, the slugs will be accurate to your site's hierarchy, and 301s won't be required during navigation (these are bad for SEO, and can drop information like query strings on click). |
What problem does this address?
In my store, the top two pages people arrive at from google are categories. It's super frustrating that I can't fully edit these pages, both for customer information and SEO, I would love to be able to edit each category with the full gutenberg experience. I could made beautiful pages with links to key products, blogs, with images and information. Google, myself and most importantly my customers would be happy. It would work great with the new templates system too!
What is your proposed solution?
When you click edit on the category, you don't get the basic text editor
You get a full editor.
The blocks you add create the content that goes at the top of category page. It will probably be a few hundred words as normal BUT you can have really engaging info like key products, blogs, quotes, buttons... videos... images!
Then, when you're done and publish it - the category archives show below that.
It seems like the templates system is trying to achieve this in a way, for example woocommerce blocks have done this:
However I don't think WordPress should end up with people creating a new template for each category page. It seems simpler from a user perspective just to allow full editing of archive pages to begin with.
Of course this still works brilliantly with templates - category pages might be treated more like a landing page, for example - stripping out some design elements to focus the user. That's what the template would do.
The text was updated successfully, but these errors were encountered: