Title: Proposal to Start a News blog on developer.WordPress.org Author: Birgit Pauli-Haack Published: February 25, 2022 Last modified: December 1, 2022 --- [ ](https://profiles.wordpress.org/bph/) [Birgit Pauli-Haack](https://profiles.wordpress.org/bph/) 10:22 pm _on_ February 25, 2022 Tags: [core ( 756 )](https://make.wordpress.org/core/tag/core/), [core-dev-blog ( 30 )](https://make.wordpress.org/core/tag/core-dev-blog/), [core-editor ( 761 )](https://make.wordpress.org/core/tag/core-editor/), [developer news ( 2 )](https://make.wordpress.org/core/tag/developer-news/), [docs ( 11 )](https://make.wordpress.org/core/tag/docs/), [proposal ( 40 )](https://make.wordpress.org/core/tag/proposal/)    # Proposal to Start a News blog on developer.WordPress.org _Update Dec 1, 2022: The Developer Blogblog (versus network, site) went live as public betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. on November 18, 2022 and was announced on this blog the following Monday [WordPress Developer Blog is in public beta](https://make.wordpress.org/core/2022/11/21/wordpress-developer-blog-is-in-public-beta/)_ --- Staying on top of the new features coming to the WordPress open-source project is one of the main barriers expressed by developers. The Make CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blog has a heavy emphasis on meeting notes for the various core teams, rather than highlighting new features. This makes it difficult for developers who are not contributors or who just occasionally contribute to find the relevant information among the team-related posts.  To achieve one of the [big-picture goals for 2022](https://make.wordpress.org/project/2022/01/21/big-picture-goals-2022/)(“ _Create a developer-focused communications site_“), this is a proposal for creating a Developer News blog. The content focuses on updates for developers, extenders creating plugins and themes, and those who work with WordPress at an agency or as freelancers.  ## Preliminary Timeline * Proposal and request for comment period: February 25 – March 18, 2022 * Coordinate with Design and MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. Teams for theme (the _News_ theme would be spectacular)  * Brainstorm meeting with team representatives: End of March * Content creation and first post: early April 2022  * Start-up phase: Through mid-July * Review and expansion to regular topics for developers: Fall 2022 ## Problem to be Solved  The current [developer.wordpress.org](http://developer.wordpress.org) holds a ton of comprehensive documentation with examples, tutorials, getting started guides, and more. That being said, there are various improvements that could be made to make the site much more impactful. Some of these areas for improvement are outlined below.  **What’s missing: ** * There is no changelog to signal various changes including when pages are updated or when new APIs appear or existing ones are augmented with new filters, hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same., and configuration.  * There is no mechanism to subscribe to updates. A blog would provide this feature. * Outside [#core-editor](https://make.wordpress.org/core/tag/core-editor/) meetings and GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. [https://github.com/](https://github.com/), there is no single place to keep up with  ongoing discussions. For example, to learn about the new styling engine, a developer needs to visit three sites: [Discussion](https://github.com/WordPress/gutenberg/discussions/37495), [Tracking Issues](https://github.com/WordPress/gutenberg/issues/38167), and the [first PR](https://github.com/WordPress/gutenberg/pull/37978). ## Start-Up Phase As a first step, the Developer News can tackle the above pain points by: * Surfacing updates to documentation,  * Highlighting new tutorials, and,  * Providing a way for developers to subscribe to stay up to date  The Developer News blog can also be added to the [Planet WordPress](https://planet.wordpress.org/) feed, so post titles also appear in the WordPress News WidgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. in the WP Adminadmin ( and super admin) Dashboard.  This initiative requires cross-team collaboration among contributors from the Documentation, Core (core-css, core-js, core-editor etc.), Training, and Support teams.  These teams could use an existing WP SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) channel for synchronous meetings, such as [#docs](https://make.wordpress.org/core/tag/docs/) or [#core](https://make.wordpress.org/core/tag/core/). During the meeting, team reps and other contributors can make editorial suggestions for topics and links that could be included in the next edition of an update post. An editorial calendar can be an early agenda item for the meetings.  After the initial start-up phase, the blog would be extended to regular topical posts relevant to developers.  ## Possible Ideas for Future Expansion * Summaries from GitHub Discussions  * Excerpts from meeting discussions for distribution to a wider audience of developers * A post consisting of a summary of multiple dev updates  * Useful questions/solutions found on StackOverflow/StackExchange  * Reviews of existing documentation to identify gaps  A possible future expansion would include a regular revision process to update content with new information and changelog recording.  I recommend that contributors to this initiative comply with the [Make Core Post and Comment Guidelines](https://make.wordpress.org/core/handbook/best-practices/post-comment-guidelines/). Should the editorial group decide to also include highlights of example plugins or themes, all products must adhere to the [Community Team’s guidelines](https://make.wordpress.org/community/handbook/wordcamp-organizer/planning-details/fundraising/local-wordcamp-sponsorship/) regarding GPLGPL GNU General Public License. Also see [copyright license](https://make.wordpress.org/core/2022/02/25/proposal-to-start-a-news-blog-on-developer-wordpress-org/?output_format=md#copyright-license). compliance of the products, including premium products.  As mentioned above, these are just some initial steps to get processes and contributors in place. Reader comments and discussion in the Slack channel will surface opportunities for further enhancements.  **What do you think?** **How could this proposal be improved?** Please share  your comments, your thoughts, and content ideas. If you’d like to contribute to the Developer News, mention this also in the comments. The comment period on this proposal will end on March 18, 2022.  _Props to Dion Hulse_ ([@dd32](https://profiles.wordpress.org/dd32/)), _Destiny Fox Kanno_ ([@piyopiyofox](https://profiles.wordpress.org/piyopiyofox/)), _Tara King (@sparklinerobots), Anne McCarthy_ ([@annezazu](https://profiles.wordpress.org/annezazu/)),_ Tonya Mork (_[@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/))_, Daisy Olsen (_[@daisyo](https://profiles.wordpress.org/daisyo/)_), Dan Soschin ( [@dansoschin](https://profiles.wordpress.org/dansoschin/)_)_, and Anjana Vasan ( [@anjanavasan](https://profiles.wordpress.org/anjanavasan/)_) _for fruitful collaborating on this proposal. _ Props to Mary Baum ([@marybaum](https://profiles.wordpress.org/marybaum/)) and Jean-Baptist Audras ([@audrasjb](https://profiles.wordpress.org/audrasjb/)) for final review [#core-dev-blog](https://make.wordpress.org/core/tag/core-dev-blog/), [#developer-news](https://make.wordpress.org/core/tag/developer-news/), [#proposal](https://make.wordpress.org/core/tag/proposal/) ### Share this: * [ Threads ](https://make.wordpress.org/core/2022/02/25/proposal-to-start-a-news-blog-on-developer-wordpress-org/?share=threads) * [ Mastodon ](https://make.wordpress.org/core/2022/02/25/proposal-to-start-a-news-blog-on-developer-wordpress-org/?share=mastodon) * [ Bluesky ](https://make.wordpress.org/core/2022/02/25/proposal-to-start-a-news-blog-on-developer-wordpress-org/?share=bluesky) * [ X ](https://make.wordpress.org/core/2022/02/25/proposal-to-start-a-news-blog-on-developer-wordpress-org/?share=x) * [ Facebook ](https://make.wordpress.org/core/2022/02/25/proposal-to-start-a-news-blog-on-developer-wordpress-org/?share=facebook) * [ LinkedIn ](https://make.wordpress.org/core/2022/02/25/proposal-to-start-a-news-blog-on-developer-wordpress-org/?share=linkedin) 1. ![](https://secure.gravatar.com/avatar/e7b27b178ff5a141aa26976d2f17272a6483508f92d4fc6a210bcf8df560921f? s=32&d=mm&r=g) 2. [Courtney Robertson](https://profiles.wordpress.org/courane01/) 10:54 pm _on_ February 25, 2022 3. +make.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. [https://wordpress.org/](https://wordpress.org/)/training/ +make.wordpress.org/docs 4. ![](https://secure.gravatar.com/avatar/e7b27b178ff5a141aa26976d2f17272a6483508f92d4fc6a210bcf8df560921f? s=32&d=mm&r=g) 5. [Courtney Robertson](https://profiles.wordpress.org/courane01/) 10:54 pm _on_ February 25, 2022 6. +make.wordpress.org/training 7. * ![](https://secure.gravatar.com/avatar/a7873a730eebbbf667e941eaefba2f3f16ee7fe49a5661507569ada7f46b94dc? s=32&d=mm&r=g) * [Birgit Pauli-Haack](https://profiles.wordpress.org/bph/) 1:55 pm _on_ February 26, 2022 * Thank you for cross-posting [@courane01](https://profiles.wordpress.org/courane01/) 8. ![](https://secure.gravatar.com/avatar/6f505c6be9a951929a99becb6b413dcfa583a5ca3dd0f7320766fee1481f0f82? s=32&d=mm&r=g) 9. [Jb Audras](https://profiles.wordpress.org/audrasjb/) 11:04 pm _on_ February 25, 2022 10. We’ll have to find a way to coordinate the work done on this new blogblog (versus network, site) and the Make P2P2 A [free theme for WordPress](http://p2theme.com/), known for front-end posting, used by WordPress for development updates and project management. See our [main development blog](https://make.wordpress.org/core/) and [other workgroup blogs](https://make.wordpress.org/).(s), but I support the initiative of having a more accessible dev blog for WordPress developers who are not actively contributing to the project. 11. * ![](https://secure.gravatar.com/avatar/a7873a730eebbbf667e941eaefba2f3f16ee7fe49a5661507569ada7f46b94dc? s=32&d=mm&r=g) * [Birgit Pauli-Haack](https://profiles.wordpress.org/bph/) 1:59 pm _on_ February 26, 2022 * Thank you for your support, [@audrasjb](https://profiles.wordpress.org/audrasjb/). It means a lot! Currently, I see that the work on the team blogs continues, and a round-up of developer relevant information is collected every other week. The decision of ‘relevant’ need coordinating, and we could mostly err on the side of too much 🙂 12. ![](https://secure.gravatar.com/avatar/120b2dbc332ea0daf46d432e7d1fd3bf9a2b98955f9bad07dfd3ff8eb0fdfc87? s=32&d=mm&r=g) 13. [Stephen Edgar](https://profiles.wordpress.org/netweb/) 2:15 am _on_ February 26, 2022 14. +make.wordpress.org/test/ 15. * ![](https://secure.gravatar.com/avatar/a7873a730eebbbf667e941eaefba2f3f16ee7fe49a5661507569ada7f46b94dc? s=32&d=mm&r=g) * [Birgit Pauli-Haack](https://profiles.wordpress.org/bph/) 1:59 pm _on_ February 26, 2022 * Thanks for the cross-post [@netweb](https://profiles.wordpress.org/netweb/) 🙂 16. ![](https://secure.gravatar.com/avatar/b96ae893f08f53cabb650f2eea21219aa0a7cb12a4680fbe31e2ba1d50c2fecb? s=32&d=mm&r=g) 17. [Alan Smodic](https://profiles.wordpress.org/asmodic/) 3:50 am _on_ February 27, 2022 18. Yes, please to this idea. Your comment here really drives it home: 19. > Outside #coreCore Core is the set of software required to run WordPress. The > Core Development Team builds WordPress.-editor meetings and GitHubGitHub GitHub > is a website that offers online implementation of git repositories that can > easily be shared, copied and modified by other developers. Public repositories > are free to host, private repositories require a paid subscription. GitHub introduced > the concept of the ‘pull request’ where code changes done in branches by contributors > can be reviewed and discussed before being merged by the repository owner. [https://github.com/](https://github.com/), > there is no single place to keep up with ongoing discussions. For example, to > learn about the new styling engine, a developer needs to visit three sites: > Discussion, Tracking Issues, and the first PR. 20. For newbies wanting to follow a little more closely, it can certainly be overwhelming. Anything to bring all of this together and surface better developer information in a more consumable fashion is a plus for everyone involved. 21. * ![](https://secure.gravatar.com/avatar/a7873a730eebbbf667e941eaefba2f3f16ee7fe49a5661507569ada7f46b94dc? s=32&d=mm&r=g) * [Birgit Pauli-Haack](https://profiles.wordpress.org/bph/) 3:36 pm _on_ February 28, 2022 * Thank you, [@asmodic](https://profiles.wordpress.org/asmodic/)! Appreciate your encouragement. Are there any specific information you found missing, to get started? 22. ![](https://secure.gravatar.com/avatar/72d658e259fa6f8cc3e9f751ec1e0ab721ccb49ac70bbb2343314db0b1216483? s=32&d=mm&r=g) 23. [Nalini Thakor](https://profiles.wordpress.org/nalininonstopnewsuk/) 11:42 am _on_ February 27, 2022 24. +make.wordpress.org/marketing/ 25. * ![](https://secure.gravatar.com/avatar/72d658e259fa6f8cc3e9f751ec1e0ab721ccb49ac70bbb2343314db0b1216483? s=32&d=mm&r=g) * [Nalini Thakor](https://profiles.wordpress.org/nalininonstopnewsuk/) 11:52 am _on_ February 27, 2022 * Thank you for this very interesting proposal [@bph](https://profiles.wordpress.org/bph/). I cross-posted this to marketing as I had not seen this discussion surfacing in that channel or mentioned in recent meetings. We can add a link to it in this week’s meeting to encourage feedback too. * Previously, the marketing team has highlighted the need for some kind of central aggregator of updates/ news specifically for developers. Suggestions included the better use of tags on posts, ability to signpost and share links more easily from the weekly devchat agendas, a monthly round-up. * This is a good initiative to particularly address the pain points that exist. It would assist the various newsletters as a one place to link to. * I am hesitant about it being termed ‘developer news’. Would ‘developer updates’ be more in keeping with the kind of updates mentioned? It may also reach an audience who may not be interested in what they may perceive ‘developer news’ to be about, eg not specific to helping them. The key will be to help developers who are not engaged to visit, return and use the information from the perspective of ‘how does this benefit me’. - ![](https://secure.gravatar.com/avatar/a7873a730eebbbf667e941eaefba2f3f16ee7fe49a5661507569ada7f46b94dc? s=32&d=mm&r=g) - [Birgit Pauli-Haack](https://profiles.wordpress.org/bph/) 3:48 pm _on_ February 28, 2022 - Thank you, [@nalininonstopnewsuk](https://profiles.wordpress.org/nalininonstopnewsuk/) for your thoughtful comment. I only see much difference between “Updates” and “News”, apart from “updates” excluding new pages, or new tutorials 🙂 But honestly, they are all updates. - The big distinction from other WordPress updates/news is probably the word“ developer”, that might make a person hesitate and consider relevancy. - Even if the information in not relevant at the time it is posted, having a single place for search to surface the relevant information when it is needed, will – that is the hope – engage developers eventually. - This proposal doesn’t have a ‘marketing’ aspect to it yet, so your input would be certainly needed once content creation is on its way, and we need assistance with SEO, categorizing and amplification via the channels. * ![](https://secure.gravatar.com/avatar/6982bc7e3ac13f1d0603975101c92574b7b0b49baeebe9d8a711ac501ed0cdc8? s=32&d=mm&r=g) * [Nicholas Garofalo](https://profiles.wordpress.org/eidolonnight/) 4:00 pm _on_ March 3, 2022 * Thanks for the cross-post [@nalininonstopnewsuk](https://profiles.wordpress.org/nalininonstopnewsuk/)! * [@bph](https://profiles.wordpress.org/bph/) I think this is an excellent idea, and makes Marketing this content significantly easier. - ![](https://secure.gravatar.com/avatar/c81957e39d5dc165328739c2fdf0bef2719777708279e843c28a89d7e19879f2? s=32&d=mm&r=g) - [Meg Phillips](https://profiles.wordpress.org/megphillips91/) 4:38 pm _on_ March 18, 2022 - Just a +1 – [@bph](https://profiles.wordpress.org/bph/) I think this is an excellent idea, and makes Marketing this content significantly easier. * ![](https://secure.gravatar.com/avatar/a7873a730eebbbf667e941eaefba2f3f16ee7fe49a5661507569ada7f46b94dc? s=32&d=mm&r=g) * [Birgit Pauli-Haack](https://profiles.wordpress.org/bph/) 8:54 pm _on_ March 18, 2022 * Thank you for your support! Yes, spreading the word might be a bit easier with a more central place. 26. ![](https://secure.gravatar.com/avatar/9100789a9a960b5f6e2d4e77670647ca82222f268e853923d43c36bc3a9e114c? s=32&d=mm&r=g) 27. [Ahmed Chaion](https://profiles.wordpress.org/chaion07/) 11:46 am _on_ February 27, 2022 28. Cross posting for [Design](https://make.wordpress.org/design/) +[make.wordpress.org/design](https://make.wordpress.org/design/) 29. ![](https://secure.gravatar.com/avatar/db79d5416d942e5fd9415b136feefd2da7929cc39853b4c30bafff4ceb8ef219? s=32&d=mm&r=g) 30. [Daniele Scasciafratte](https://profiles.wordpress.org/mte90/) 2:43 pm _on_ February 27, 2022 31. Honestly I am doing it already with the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blogblog (versus network, site) (I have email notifications with a filterFilter Filters are one of the two types of Hooks [https://codex.wordpress.org/Plugin_API/Hooks](https://codex.wordpress.org/Plugin_API/Hooks). They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. to ignore email from stuff that I don’t care like GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/) for example). The _field guideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the [WordPress release cycle](https://make.wordpress.org/core/handbook/about/release-cycle/). The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page._ at every release as developer and contributor in a web agency that sells also plugins to me is enough to get the latest updates. That page at every release is the best guide to know what are the updates in every release, with tickets and example also because often include a blog post of a feature, so I am not sure what is the purpose of this initiative. 32. Maybe get this information in another blog? So there is less noise? Add a follows button for changes in the developer website for specific functions, like many docs or wiki have? Promote better what already is written for every release here in this blog? 33. Because to me the blogpost on the core blog (meeting recaps, proposal like this etc) are the only thing in the WP ecosystem that works, after all issues from less committers compared years ago as example and I don’t want to lose also them. 34. * ![](https://secure.gravatar.com/avatar/a7873a730eebbbf667e941eaefba2f3f16ee7fe49a5661507569ada7f46b94dc? s=32&d=mm&r=g) * [Birgit Pauli-Haack](https://profiles.wordpress.org/bph/) 10:10 pm _on_ March 1, 2022 * Thank you [@mte90](https://profiles.wordpress.org/mte90/) for your review. Especially for new comers into the WordPress developer space or people that are not so tuned into the Make Blogs. * This is not a proposal to replace any of the existing avenues, so the make blogs won’t go away. That’s how the various team organize themselves. * The Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the [WordPress release cycle](https://make.wordpress.org/core/handbook/about/release-cycle/). The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. is a tried and true publication that helps many developers to find out what is new to the last version. * It is a bit harder to find all the changes in the last four version about blocks or scripts etc. We heard from many developers, new to the eco system, and/ or new to the blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor that it hard to keep up. This will be a place where they can get started with their research. - ![](https://secure.gravatar.com/avatar/db79d5416d942e5fd9415b136feefd2da7929cc39853b4c30bafff4ceb8ef219? s=32&d=mm&r=g) - [Daniele Scasciafratte](https://profiles.wordpress.org/mte90/) 11:43 am _on_ March 2, 2022 - So I don’t understand what is the difference right now with the new proposal. Just a way for newcomers to find the new dev stuff in every wordpress release? Maybe is the opportunity to involve more people in contributing if we forward them to the Make blogs? - ![](https://secure.gravatar.com/avatar/a7873a730eebbbf667e941eaefba2f3f16ee7fe49a5661507569ada7f46b94dc? s=32&d=mm&r=g) - [Birgit Pauli-Haack](https://profiles.wordpress.org/bph/) 7:46 pm _on_ March 2, 2022 - Yes, it’s a way for newcomers to find new and old stuff. - > Maybe is the opportunity to involve more people in contributing if we > forward them to the Make blogs? - Forward them from where? - One of the assumptions for developer experience is that someone who wants to look up something about WordPress they would go to developer.WordPress. orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. [https://wordpress.org/](https://wordpress.org/). Presently, it doesn’t offer much for orientation on regarding releases or updates at first site. Adding a blogblog (versus network, site) to the site would get new people oriented to find their way. - I understand [@mte90](https://profiles.wordpress.org/mte90/) that you certainly wouldn’t need orientation or someone to guide you along your journey. I definitely could learn from you. You have been participating and contributing to WordPress for a decade already. Thank you! - A non-contributing WordPress developer won’t consider searching the make blogs at all, so this site will give context on updates and link to the relevant places. * ![](https://secure.gravatar.com/avatar/db79d5416d942e5fd9415b136feefd2da7929cc39853b4c30bafff4ceb8ef219? s=32&d=mm&r=g) * [Daniele Scasciafratte](https://profiles.wordpress.org/mte90/) 10:47 am _on_ March 3, 2022 * If this new blogblog (versus network, site) on developer help to promote make is fine to me. Looking at the wp development there are less contributors compared to the past and we need to advocacy that fact that we need skilled/ motivated dev. * I want to avoid just a duplication of stuff between this blog and the make posts. - ![](https://secure.gravatar.com/avatar/a7873a730eebbbf667e941eaefba2f3f16ee7fe49a5661507569ada7f46b94dc? s=32&d=mm&r=g) - [Birgit Pauli-Haack](https://profiles.wordpress.org/bph/) 3:36 pm _on_ March 3, 2022 - Cheers, Daniele, You raised an important point. Thank you. It’s absolutely a big goal not to duplicate content but augment it. As the keeper of the [Keeping up with Gutenberg page](https://make.wordpress.org/core/handbook/references/keeping-up-with-gutenberg-index/), I know how valuable the teams’ work is. The Developer News blogblog( versus network, site) is another path for discovery of salient information for developers. And who know they will become contributors in the near future. 35. ![](https://secure.gravatar.com/avatar/8c89447051442fa67f733cd23f299ed361f51e5129ee4b00a1f5d83fc2178a09? s=32&d=mm&r=g) 36. [Milana Cap](https://profiles.wordpress.org/milana_cap/) 11:44 am _on_ February 28, 2022 37. I support and volunteer to be a part of this initiative in any way I can be helpful. 38. * ![](https://secure.gravatar.com/avatar/a7873a730eebbbf667e941eaefba2f3f16ee7fe49a5661507569ada7f46b94dc? s=32&d=mm&r=g) * [Birgit Pauli-Haack](https://profiles.wordpress.org/bph/) 10:01 pm _on_ March 1, 2022 * Thank you so much [@milana_cap](https://profiles.wordpress.org/milana_cap/) I will take you up on that offer for sure! 😄 39. ![](https://secure.gravatar.com/avatar/241584c8900ae5ccd62ff4c9db7d58e58bc9e0dc0162d4bdcac2a916d586c7ed? s=32&d=mm&r=g) 40. [Francesca Marano](https://profiles.wordpress.org/francina/) 7:55 am _on_ March 5, 2022 41. A big +1 for this proposal. [@bph](https://profiles.wordpress.org/bph/) thank you for putting it together. I share some of [@mte90](https://profiles.wordpress.org/mte90/) concerns but it seems like you are aligned on that too so kudos and let’s do this! I have a few of hours to work on this if you need me. 42. * ![](https://secure.gravatar.com/avatar/a7873a730eebbbf667e941eaefba2f3f16ee7fe49a5661507569ada7f46b94dc? s=32&d=mm&r=g) * [Birgit Pauli-Haack](https://profiles.wordpress.org/bph/) 9:34 pm _on_ March 8, 2022 * [@francina](https://profiles.wordpress.org/francina/) Thank you so much for your encouragement! Looking forward to getting you involved in this endeavor! 43. ![](https://secure.gravatar.com/avatar/0834bbc8f633be70e8ea506846aa93626588edb8605217aafc645e4ba02e34d7? s=32&d=mm&r=g) 44. [Steve Stern (sterndata)](https://profiles.wordpress.org/sterndata/) 2:09 pm _on_ May 13, 2022 45. +make.wordpress.org/support 46. ![](https://secure.gravatar.com/avatar/c9e80daf45ce5431f9271b34fe7d227b68f962c30ff439150e453baa543effdd? s=32&d=mm&r=g) 47. [Nilesh Kantak](https://profiles.wordpress.org/nileshkantak/) 3:04 pm _on_ May 13, 2022 48. Yes, This is a perfect proposal and will help everyone. I am interested working together. 49. ![](https://secure.gravatar.com/avatar/a7873a730eebbbf667e941eaefba2f3f16ee7fe49a5661507569ada7f46b94dc? s=32&d=mm&r=g) 50. [Birgit Pauli-Haack](https://profiles.wordpress.org/bph/) 4:49 pm _on_ May 13, 2022 51. Thank you, [@nileshkantak](https://profiles.wordpress.org/nileshkantak/) I keep you in mind for the next phase! 52. ![](https://secure.gravatar.com/avatar/d83d084ee0387ee8c0314fbedc2bc28d017efbb3b724031c93b23bd7ace0cc01? s=32&d=mm&r=g) 53. [bcworkz](https://profiles.wordpress.org/bcworkz/) 3:10 am _on_ May 14, 2022 54. I provide a lot of support to amateur developers in the forums and am one of the Support Team moderators. I love this proposal! It’ll help me keep abreast of on going changes to WP so I can better help others in the forums. I’m not sure how I can help with this endeavor, but I’m willing to put some time in. This probably means I’ve just volunteered to at least represent the Support Team where any coordination is needed. 55. ![](https://secure.gravatar.com/avatar/a7873a730eebbbf667e941eaefba2f3f16ee7fe49a5661507569ada7f46b94dc? s=32&d=mm&r=g) 56. [Birgit Pauli-Haack](https://profiles.wordpress.org/bph/) 11:54 am _on_ May 14, 2022 57. Hi @bcworkz, thank you so much for your comments. And being a great resource for the WordPress developers in the forums. You would be a fantastic resource! Thank you for volunteering. I will connect with you on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) to coordinate more. Comments are closed. # Post navigation [← Dev chat summary, February 23, 2022](https://make.wordpress.org/core/2022/02/24/dev-chat-summary-february-23-2022/) [Editor chat summary: Wednesday, February 23 2022 →](https://make.wordpress.org/core/2022/02/28/editor-chat-summary-wednesday-february-23-2022/)