Last Updated on June 7, 2025 by Neil Murray
Table of Contents #
- Setup for WordPress Contribution
- Key skills you need to learn
- Gutenberg Code Contributions
- Gutenberg Testing
- Communicating with Gutenberg Team
- CF7 Skins Team – Gutenberg Contributions
Here at CF7 Skins we’ve made a decision to get involved & contribute to the development of the Form API in WordPress core.
We offer all contractors working 20+ hours per week to contribute 10% of their time to the WordPress Gutenberg project. We focus all our efforts on the Form API.
1. Setup for WordPress Contribution #
Work through the Readme links to get setup for WordPress Contribution.
Readme links:
While there are many options you can use for your local development environment, the recommended way is to use Docker & wp-env.
Further reading:
2. Key skills you need to learn #
To contribute to the Gutenberg project you will need to have (or learn) the following key skills.
Readme links:
Here at CF7 Skins we expect you to put in the time you need to learn these skills in your own time when you start contributing. Our pay offer is only for the time you spend constructively contributing to the Gutenberg project.
We believe learning these skills improves significantly your overall skill level as a WordPress developer. They are key part of many professional WordPress development teams.
We don’t at this stage use these processes in our development at CF7 Skins but we plan to move toward this as we convert CF7 Skins to a Gutenberg Block interface.
Further reading:
3. Gutenberg Code Contributions #
Work through the following Readme links to learn how to contribute to the Gutenberg project.
Readme links:
To help you contribute effectively we recommend you do the following:
- Look through the Gutenberg code structure
- Check out recent commits on the GitHub Repo
- Read through all Form related issues (open & closed)
- Keep up to date on Form related issues – add comments where appropriate
4. Gutenberg Testing #
All Pull Requests to the Gutenberg project are required to include .. for testing. Work through the following Readme links to learn how to add suitable testing to your Pull Requests.
Readme links:
- Testing Overview
- Writing Tests
- Gutenberg Testing
- Get Setup for Testing
- Testing Bugs
- Accessibility Testing
5. Communicating with Gutenberg Team #
The Make WordPress Core blog is the primary spot for the latest information around WordPress development: including announcements, product goals, meeting notes, meeting agendas, and more.
Real-time discussions for development take place in #core-editor and #core-js channels in Make WordPress Slack (registration required).
Weekly meetings for the editor component are on Wednesdays at 14:00UTC, and for the JavaScript component on Tuesday at 15:00UTC, in their respective Slack channels.
Readme links:
Be sure to read the Contributing Guidelines before you start.
6. CF7 Skins Team – Gutenberg Contributions #
We record work done by the CF7 Skins Team on the Gutenberg project at the following links:
Key this up to date as your work so other team members have an ongoing record of the work we have done.
Further Reading
Notes:
ADD notes here.
Save all Images to Sync – use ..\Sync\..\Form API\Guidelines\Getting Started – Form API\