Site Editor: Consider adding in descriptions to "Add New Templates" flow

[annezazu]

Right now, you can toggle/hide descriptions for templates when in data views, but when you click "Add a new template" there's no description of the template you might add:

This makes it hard to know at a glance what each template might do. Perhaps when you hover, a tooltip could show? Or we could consider adding in very brief descriptions.

[t-hamano]

In #50595, when this modal dialog was implemented, a description existed. After that, it seems that the description was deleted in #51806.

I'm leaning toward bringing back the description, but the current description is quite long, so I think it would be nice to add a short description.

example:

function get_default_block_template_types() {
	$default_template_types = array(
		// ...
		'archive'        => array(
			'title'       => _x( 'All Archives', 'Template name' ),
			'description' => __( 'Displays any archive, including posts by a single author, category, tag, taxonomy, custom post type, and date. This template will serve as a fallback when more specific templates (e.g. Category or Tag) cannot be found.' ),
			'short_description' => __( 'Displays any archive, including posts by a single author, category, tag, taxonomy, custom post type, and date.' ),
		),
		// ...
	);
	// ...
}

cc @ntsekouras @richtabor @jameskoster @jasmussen

[jameskoster]

That's right, the descriptions made the modal extremely noisy. Short descriptions could be worth a try, but it's not always easy to capture the full template purpose succinctly, especially things like front-page and home, or generic templates like archive.

There could even be a world where this becomes a data view grid with previews. Given blocks like Archive Title
now include contextual placeholders (for instance in the Author archives template it displays "Author name" on the canvas), the previews could be more useful. Then users / platforms could toggle fields like description accordingly.

[annezazu]

Agreed completely around contextual placeholders. That's where my brain went too. Right now, with the power of data views there, it would be awesome for this modal to then "respect" the choices set.