{"id":179,"date":"2024-10-04T11:41:39","date_gmt":"2024-10-04T15:41:39","guid":{"rendered":"http:\/\/id-developer-upgrade-58.cms-devl.bu.edu\/gutenberg\/?page_id=179"},"modified":"2025-02-20T13:50:49","modified_gmt":"2025-02-20T18:50:49","slug":"icons-naming-categories","status":"publish","type":"page","link":"https:\/\/id-developer-upgrade-58.cms-devl.bu.edu\/gutenberg\/handbook\/wp-core\/icons-naming-categories\/","title":{"rendered":"Block Icons, Naming, & Categories"},"content":{"rendered":"\n

Naming<\/h2>\n\n\n\n

The Name of a block is the primary namespace and identifier for a given block. Though it might be tempting to include the plugin name as part of the block name, this should be avoided since a Collection can be used to denote that grouping. Ideally the name of a BU block should be limited to its most basic descriptor, and additional identifiers should only be thrown in if the use of collections and the BU Red icon styling are not enough to differentiate it from an existing block. For example a BU Button block is named just “Button” same as core WP Button block, but the BU version has a red icon to differentiate it.<\/p>\n\n\n\n

Categories<\/h2>\n\n\n\n

A Category is the name space to which a given block is grouped to. The block will appear under that category in the Inserter Menu. A block can only be registered to one category.<\/em><\/p>\n\n\n\n

\"\"
Example blocks assigned to custom categories.<\/figcaption><\/figure><\/div>\n\n\n\n

Categories are created in php<\/code> and assigned via the “category” node in block.json.<\/p>\n\n\n\n

WordPress Documentation<\/a><\/p>\n\n\n\n

public function custom_block_category( $categories ) {\n\tarray_unshift(\n\t\t$categories,\n\t\tarray(\n\t\t\t'slug'  => 'theme-or-plugin-slug-block-category',\n\t\t\t'title' => 'BU: Theme Starter Block Category (PHP)',\n\t\t)\n\t);\n\n\treturn $categories;\n}\nadd_filter( 'block_categories_all', 'custom_block_category' );<\/code><\/pre>\n\n\n\n
{\n\t\"$schema\": \"https:\/\/schemas.wp.org\/trunk\/block.json\",\n\t\"apiVersion\": 3,\n\t\"name\": \"theme-or-plugin-slug-block-collection\/example-block\",\n\t\"version\": \"0.1.0\",\n\t\"title\": \"BU: Theme Starter 1\",\n\t\"category\": \"theme-or-plugin-slug-block-category\"\n}<\/code><\/pre>\n\n\n\n
Collections<\/h2>\n\n\n\n
Collections allow specific block types to be grouped together for added visibility in the editor\u2019s Inserter menu, regardless of their categories. A block can only be registered to one collection.<\/em><\/p>\n\n\n\n
For instance take two different BU Blocks; the Lead-In block could be registered to the Layout category and the BUniverse block might be registered under the Embeds category. By registering a collection for the BU Blocks namespace, these blocks would appear in the Inserter under their respective categories but also grouped under a BU Blocks collection. So while a block is registered to one Category, it can appear under multiple areas of the Inserter Menu thru the use of Collections.<\/p>\n\n\n\n
\"\"
Example blocks assigned to custom collections.<\/figcaption><\/figure><\/div>\n\n\n\n
Collections are created in js<\/code> and assigned via the “namespace” node in block.json (must match the first argument of “registerBlockCollection”). The collection will have all blocks registered as namespace\/*<\/code>.<\/p>\n\n\n\n
WordPress Documentation<\/a><\/p>\n\n\n\n
registerBlockCollection( 'theme-or-plugin-slug-block-collection', {\n\ttitle: 'BU: Theme Starter Blocks Collection (JS)',\n} );<\/code><\/pre>\n\n\n\n
Block Icon<\/h2>\n\n\n\n
To keep BU developed block consistent and recognizable in the block selection panel, we’ve provided a template for creating their SVG icons.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
\n
Download Template<\/a><\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"
Naming The Name of a block is the primary namespace and identifier for a given block. Though it might be tempting to include the plugin name as part of the block name, this should be avoided since a Collection can be used to denote that grouping. Ideally the name of a BU block should be […]<\/p>\n","protected":false},"author":3670,"featured_media":0,"parent":575,"menu_order":6,"comment_status":"closed","ping_status":"closed","template":"","meta":[],"status-is-a-reserved-term":[],"assignee":[],"_links":{"self":[{"href":"https:\/\/id-developer-upgrade-58.cms-devl.bu.edu\/gutenberg\/wp-json\/wp\/v2\/pages\/179"}],"collection":[{"href":"https:\/\/id-developer-upgrade-58.cms-devl.bu.edu\/gutenberg\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/id-developer-upgrade-58.cms-devl.bu.edu\/gutenberg\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/id-developer-upgrade-58.cms-devl.bu.edu\/gutenberg\/wp-json\/wp\/v2\/users\/3670"}],"replies":[{"embeddable":true,"href":"https:\/\/id-developer-upgrade-58.cms-devl.bu.edu\/gutenberg\/wp-json\/wp\/v2\/comments?post=179"}],"version-history":[{"count":11,"href":"https:\/\/id-developer-upgrade-58.cms-devl.bu.edu\/gutenberg\/wp-json\/wp\/v2\/pages\/179\/revisions"}],"predecessor-version":[{"id":251,"href":"https:\/\/id-developer-upgrade-58.cms-devl.bu.edu\/gutenberg\/wp-json\/wp\/v2\/pages\/179\/revisions\/251"}],"up":[{"embeddable":true,"href":"https:\/\/id-developer-upgrade-58.cms-devl.bu.edu\/gutenberg\/wp-json\/wp\/v2\/pages\/575"}],"wp:attachment":[{"href":"https:\/\/id-developer-upgrade-58.cms-devl.bu.edu\/gutenberg\/wp-json\/wp\/v2\/media?parent=179"}],"wp:term":[{"taxonomy":"status-is-a-reserved-term","embeddable":true,"href":"https:\/\/id-developer-upgrade-58.cms-devl.bu.edu\/gutenberg\/wp-json\/wp\/v2\/status-is-a-reserved-term?post=179"},{"taxonomy":"assignee","embeddable":true,"href":"https:\/\/id-developer-upgrade-58.cms-devl.bu.edu\/gutenberg\/wp-json\/wp\/v2\/assignee?post=179"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}