An object describing the attributes shape of a block. The keys can be named as most appropriate to describe the state of a block type. The value for each key is a function which describes the strategy by which the attribute value should be extracted from the content of a saved post’s content. When processed, a new object is created, taking the form of the keys defined in the attribute sources, where each value is the result of the attribute source function.
The object representation of the current state of a block in post content. When loading a saved post, this is determined by the attribute sources for the block type. These values can change over time during an editing session when the user modifies a block, and are used when determining how to serialize the block.
The abstract term used to describe units of markup that, composed together, form the content or layout of a webpage. The idea combines concepts of what in WordPress today we achieve with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.
The CSS styles that are part of the block, either via its stylesheet or via the block markup itself. For example, a class attached to the block markup is considered block styles.
Learn more about Block Styles.
An API for blocks to declare what features they support. By declaring support for a feature, the API would add additional attributes to the block and matching UI controls for most of the existing block supports.
See Block Supports reference documentation for a deep dive into the API.
A theme built in block forward way that allows Full Site Editing to work. The core of a block theme are its block templates and block template parts. To date, block theme templates have been HTML files of block markup that map to templates from the standard WordPress template hierarchy.
These are not a WordPress taxonomy, but instead used internally to sort blocks in the Block Library.
Primary interface for selecting from the available blocks, triggered by plus icon buttons on Blocks or in the top-left of the editor interface.
A unique identifier for a block type, consisting of a plugin-specific namespace and a short label describing the block’s intent. e.g.
A template is a pre-defined arrangement of blocks, possibly with predefined attributes or placeholder content. You can provide a template for a post type, to give users a starting point when creating a new piece of content, or inside a custom block with the
InnerBlocks component. At their core, templates are simply HTML files of block markup that map to templates from the standard WordPress template hierarchy, for example index, single or archive. This helps control the front-end defaults of a site that are not edited via the Page Editor or the Post Editor. See the templates documentation for more information.
Building on Block Templates, these parts help set structure for reusable items like a Footer or Header that one typically sees in a WordPress site. They are primarily site structure and are never to be mixed with the post content editor. With Full Site Editing and block based themes, users can create their own arbitrary Template Parts, save those in the database for their site, and re-use them throughout their site. Template parts are equivalent – in blocks – of theme template parts. They are generally defined by a theme first, carry some semantic meaning (could be swapped between themes such as a header), and can only be inserted in the site editor context (within “templates”).
In contrast with the blocks composing a particular post, a block type describes the blueprint by which any block of that type should behave. So while there may be many images within a post, each behaves consistent with a unified image block type definition.
A block which embeds the TinyMCE editor as a block, TinyMCE was the base of the previous core editor. Older content created prior to the block editor will be loaded in to a single Classic block.
This refers to a collection of features that ultimately allows users to edit their entire website using blocks as the starting point. This feature set includes everything from block patterns to global styles to templates to design tools for blocks (and more). First released in WordPress 5.9.
The CSS styles generated by WordPress and enqueued as an embedded stylesheet in the front end of the site. The stylesheet ID is
global-styles-inline-css. The contents of this stylesheet come from the default
theme.json of WordPress, the theme’s
theme.json, and the styles provided by the user via the global styles sidebar in the site editor.
Compare to block styles.
Deprecated term. See Settings Sidebar.
See Block Styles.
A block that allows you to edit a site’s navigation menu, both in terms of structure and design.
Patterns are predefined layouts of blocks that can be inserted as starter content that are meant to be changed by the user every time. Once inserted, they exist as a local save and are not global.
A sidebar region containing metadata fields for the post, including scheduling, visibility, terms, and featured image.
A block that replicates the classic WP_Query and allows for further customization with additional functionality.
A block that is saved and then can be shared as a reusable, repeatable piece of content.
A common component enabling rich content editing including bold, italics, hyperlinks, etc.
The process of converting a block’s attributes object into HTML markup, which occurs each time a block is edited.
The panel on the right that contains the document and block settings. The sidebar is toggled using the Settings gear icon. Block settings are shown when a block is selected, otherwise document settings are shown.
The cohesive experience that allows you to directly edit and navigate between various templates, template parts, styling options, and more.
A type of block where the content of which is known at the time of saving a post. A static block will be saved with HTML markup directly in post content.
A scaled down direct editing experience allowing you to edit/change/create the template a post/page uses.
Blocks that accomplish everything possible in traditional templates using template tags (ex: Post Author Block). A full list can be found here.
A set of button controls. In the context of a block, usually referring to the toolbar of block controls shown above the selected block.