Skip to content
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

Editor: Organize editor inserter menu in user friendly way #35876

Closed
apeatling opened this issue Aug 29, 2019 · 5 comments
Closed

Editor: Organize editor inserter menu in user friendly way #35876

apeatling opened this issue Aug 29, 2019 · 5 comments

Comments

@apeatling
Copy link
Member

apeatling commented Aug 29, 2019

Our editor inserter menu group organization on WordPress.com looks like this:

Screen Shot 2019-08-29 at 11 07 47 AM

This is a mix of plugin groupings and block type groupings, and is not very user friendly. Our users on WordPress.com simple sites have not installed CoBlocks or Jetpack, so the plugin groupings are confusing. We need to organize groups in a more user intuitive way.

I think the first step here is moving third party plugins from the top of the inserter, and grouping 3rd party blocks lower in the menu. CoBlocks should not be showing above "Common Blocks" for example.

There is some work happening in core Gutenberg to better organize groups: WordPress/gutenberg#11406

Let's contribute to the ideas there, and help inform that work with any usage data we can provide to help core Gutenberg with the most effective ordering.

/cc @kwight @mmtr @shaunandrews @mtias

@apeatling apeatling added [Status] Needs Design Review Add this when you'd like to get a review / feedback from the Design team on your PR [Type] Epic [Goal] Editor Improvements labels Aug 29, 2019
@mmtr
Copy link
Member

mmtr commented Aug 29, 2019

From a technical point of view, we can customize the categories in WP.com with the current tools available in Gutenberg:

import { getCategories, setCategories } from '@wordpress/blocks';
import { __, sprintf } from '@wordpress/i18n';
import { addFilter } from '@wordpress/hooks';

const changeBlocksCategories = ( settings, name ) => {
	if ( 'coblocks' === settings.category ) {
		settings.category = 'common';
	}
	if ( 'coblocks-gallery' === settings.category ) {
		settings.category = 'wpcom-category-1';
	}
	if ( 'jetpack' === settings.category ) {
		settings.category = 'wpcom-category-2';
	}
	return settings.
} );

addFilter( 'blocks.registerBlockType', 'wpcom/categories', changeBlocksCategories );

setCategories( [
	{
		slug: 'wpcom-category-1',
		title: 'Custom WP.com category 1',
		icon: <svg>...</svg>,
	},
	{
		slug: 'wpcom-category-2',
		title: 'Custom WP.com category 2',
		icon: <svg>...</svg>,
	},
	...getCategories().filter( ( { slug } ) => ! [ 'coblocks-galleries', 'coblocks', 'jetpack' ].includes( slug ) ),
] );

@kwight
Copy link
Contributor

kwight commented Aug 30, 2019

Oh cool, that's great. Even if we push it down the list, we need to keep CoBlocks clearly marked as so; we're benefitting from community contributions, it's only right to not hide that.

@shaunandrews
Copy link
Contributor

shaunandrews commented Aug 30, 2019

it's only right to not hide that.

I get that perspective, but from a users point of view there's no understanding what a "CoBlock" is and we shouldn't be grouping things with branded names. The blocks themselves can/should be branded in someway, but the groupings likely isn't the best solution for customers.

@simison
Copy link
Member

simison commented Oct 22, 2019

Unregistering these categories on .com and re-registering something like block collections would be neat: WordPress/gutenberg#16866

I think that way it would be possible to solve some of the branding questions, too.

@simison
Copy link
Member

simison commented Jun 11, 2020

I'll close this as outdated.

@simison simison closed this as completed Jun 11, 2020
@matticbot matticbot removed the [Status] Needs Design Review Add this when you'd like to get a review / feedback from the Design team on your PR label Jun 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants