This month’s update from our core contributors. Here’s how Jessica and Tammie are helping shape the future of WordPress.
At Greyd, we don’t just build on top of WordPress. We actively invest in the future of the platform itself. That’s why we sponsor contributors who are deeply involved in core development and design. This isn’t about marketing. It’s about long-term reliability, better tools for everyone, and helping shape a platform that serves both users and professionals.
Contributing to WordPress Core means helping improve the open-source software that powers over 40% of the web. For us, it’s not just about giving back. It’s also about fixing real issues that affect product development, improving accessibility, and making sure WordPress evolves in a sustainable direction.
At WordCamp Europe: Contributor Day
Both Jessica and Tammie joined Contributor Day this year.
Jessica
Published a series of long-overdue “What’s new in Gutenberg?” updates for several recent releases. These summaries are essential for developers, designers, and agencies to stay aligned with changes in the editor.
She also joined group discussions on extensibility, an area critical to maintaining flexibility for developers and plugin creators.
Tammie
- Focused on design triage and backlog cleanup to keep the flow of design-related contributions moving.
- Participated in discussions on extensibility and triage best practices
- Reviewed, merged, and collaborated on pull requests
- Fixed a problem with dynamic templates and the Query Loop block
Ongoing work in June
- Cleared blockers and helped maintain momentum on shared tickets with Jessica
- Triaged extensibility-related issues and labels
- Ran exploratory tests on DataViews with multiple custom post types. This kind of hands-on investigation helps surface opportunities for improvement
- Confirmed technical limitations in the Site Editor (styling menus with CSS is not currently possible without JavaScript) and contributed to ongoing discussions
- Reported a new issue in the Gutenberg Stylebook regarding default content handling: GitHub Issue 70555
Why this matters
This is what contribution looks like in practice: critical maintenance, exploratory work, and pushing for better outcomes. We’re proud to support it.
These contributions help us make Greyd.Suite better, but they also address broader issues that affect other developers, theme authors, and agencies. Whether it’s improving accessibility, fixing edge-case bugs, or helping others build more flexible solutions, our contributions are meant to ripple outward.
And like all contributions to open source, it’s not always simple. Coordination, clear communication, and alignment with the larger project are key. We’re proud to be part of that effort.
Stay tuned for next month’s update!
