Gutenberg

The name is commonly used for the Block Editor and related block-development features, although block functionality is now part of WordPress core. In practical terms, Gutenberg belongs to the publishing and site-management layer. Knowing that layer is important because it tells you what the term can change, what it cannot change, and where to look when something behaves unexpectedly.

The common mistake is to use Gutenberg as if it also meant Block Editor. That blurs two separate decisions and usually sends troubleshooting in the wrong direction. A better test is practical: Distinguish the Gutenberg plugin/project from the block editor features already included in WordPress core.

In day-to-day work, Gutenberg matters when the concept needs to be identified precisely instead of being grouped with a nearby term. The practical value is not the vocabulary itself; it is being able to identify the right control, file, setting or decision when the concept becomes relevant.

Gutenberg is the broader WordPress block-editing project that introduced block-based content and expanded into site editing. That example is useful because it turns the definition into something you can recognize, test and discuss with other people working on the same project.

Use these references when you need documentation-level detail, specifications or product-specific behavior beyond the plain-English explanation above.