Gutenberg: the WordPress block editor and development plugin
The Block Editor project for WordPress and beyond. Plugin is available from the official repository.
At a glance
- What is it?
- Gutenberg is the WordPress block editor project. WordPress includes the block editor in core; the separate Gutenberg plugin gives users an opportunity to test newer development work.
- Who is it for?
- Most WordPress users can use the block editor already included in core. Install the separate Gutenberg plugin when you want to test its newer features, preferably on a staging copy with a verified backup and recovery plan.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- What is it written in?
- Mainly JavaScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 14, 2026, and from our analysis. They are not legal advice.
Star history
- WordPress/gutenberg11,795 ★ · +38
| Repository | 2026-09-22 | 2026-11-14 |
|---|---|---|
| WordPress/gutenberg | 11.8k | 11.8k |
38 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Core editor and the plugin
The block editor is part of WordPress core; post block editing arrived in 2018, and site editing followed in WordPress 5.9. The separately installed Gutenberg plugin provides a way to test newer editor development before it reaches a core release. The plugin directory and project documentation describe the current release and requirements.
Before testing a plugin update on a live site, use a staging copy, verify backups and practice restoring the site. Plugin and core versions are related but are not interchangeable; consult the official versions-in-WordPress table.
Project roadmap
The project describes a four-part roadmap: editing, customization, collaboration and multilingual work. These are broad areas of development, not proof that all related code is absent or that non-English publishing is unavailable today. Check current project updates and the specific feature’s status before planning a deployment.
Developer toolchain
The repository has Node and npm requirements for contributors building from source. These requirements can change with the branch and are distinct from the requirements for a site administrator installing a published plugin. Read the current package manifest and contributor setup guide for the exact revision you build.
Capabilities and editor access
WordPress capabilities affect access to administrative functions, and experimental features may have additional conditions. Roles, capabilities, site configuration, theme and plugin version can all affect what an account sees. Test the actual accounts and screens in a staging environment rather than assuming a manifest entry describes every editor permission.
Plugin builds and WordPress packages
The repository builds the Gutenberg plugin and also contains numerous WordPress packages. A private root package does not mean that no related packages are published to npm. Developers should use the package-specific documentation and versions when consuming individual packages.
Versions and releases
The plugin directory links current release notes, and WordPress publishes a table connecting Gutenberg plugin versions to core releases. Pin and test the version appropriate to your environment; review compatibility with themes and other plugins before updating.
Local development
The repository supplies local development and test configuration. Follow the contributor guide for the selected checkout, including its current Node, npm and environment requirements. Run the checks relevant to your changes rather than assuming a historical dependency version remains current.
Support and contributions
The project directs users to its support forums and asks bug reporters to search existing issues before filing a new one. Contributors can use the handbook and repository contribution guide. Include the WordPress and plugin versions, steps to reproduce and relevant environment details in a report.
Editorial conclusion
Most WordPress users can use the block editor already included in core. Install the separate Gutenberg plugin when you want to test its newer features, preferably on a staging copy with a verified backup and recovery plan. Developers should check the repository’s current contributor instructions and toolchain requirements for their chosen revision.
Frequently asked questions
how to install gutenberg in wordpress
WordPress includes the block editor in core. To test the separate Gutenberg plugin, install it from Plugins in wp-admin or from the WordPress.org plugin directory; try it on staging first and keep a restorable backup.
how to use gutenberg editor in wordpress
Open a post or page in the WordPress block editor, add blocks with the inserter and arrange or edit them. The separate Gutenberg plugin is not required for the core block editor.
how to use gutenberg block editor
The WordPress Editor documentation covers using the editor as an author creating posts and pages. For a first hands-on pass the project points to the block editor live demo, which needs no install at all.
how to use gutenberg blocks
Extending the editor with your own blocks is done through plugins, and the Quick Start Guide is the fastest documented route in. The Block Editor Handbook holds the tutorials, documentation, and API references.
how to use gutenberg blocks in elementor
The README does not mention Elementor or other third party page builders. It describes the editor as extended by third-party developers using plugins.
Official sources
Was this useful?