Skip to main content
Welcome to the Gutenberg project! We’re excited to have you join us in creating the future platform for publishing. All are welcome here, and there are many ways to contribute.

How Can I Contribute?

The Gutenberg project welcomes contributions of all kinds:

Code Contributions

Contribute to the JavaScript packages, PHP code, or React Native mobile editor. See the Code Contribution guide to get started.

Design

Help shape the user experience and visual design of the block editor. Design contributions include interface design, iconography, and user experience improvements.

Documentation

Improve the documentation you’re reading right now! Documentation contributions help developers understand and use the Gutenberg framework effectively.

Triage

Help review existing issues to make sure they’re relevant and actionable. Triage is an important contribution because it allows the project to work on the highest priority issues.

Development Hub

The Gutenberg project uses GitHub to manage code and track issues:
  • Main Repository: https://github.com/WordPress/gutenberg
  • Issues List: Browse issues to find work
  • Good First Issue: Look for the “Good First Issue” label for beginner-friendly tasks
  • Good First Review: The “Good First Review” label marks pull requests suitable for new reviewers

Community and Discussions

Stay connected with the Gutenberg community:
  • Make WordPress Core Blog: The primary spot for announcements, product goals, meeting notes, and agendas
  • Slack Channels: Real-time discussions happen in #core-editor and #core-js on Make WordPress Slack

Guidelines

All contributors are expected to follow these guidelines:

Code of Conduct

As with all WordPress projects, we want to ensure a welcoming environment for everyone. All contributors must follow the WordPress Code of Conduct.

Coding Standards

Contributors should adhere to:

Pull Request Best Practices

Review the overall process and best practices for pull requests, including:
  • Keeping changes focused and atomic
  • Writing clear commit messages
  • Ensuring tests pass
  • Following accessibility testing guidelines

Accessibility First

Accessibility should be top of mind and thoroughly tested. Follow the accessibility testing instructions to ensure your contributions are inclusive.

React Native Compatibility

Verify that changes affecting function/class/variable names are mirrored in corresponding .native.js versions to avoid breaking changes in the React Native Mobile Editor. You maintain copyright over any contribution you make. By submitting a pull request, you agree to release that code under Gutenberg’s License.

Reporting Security Issues

Please see the SECURITY.md file for information on reporting security vulnerabilities.

Next Steps

Ready to start contributing? Check out these resources:

Build docs developers (and LLMs) love