Summary of the WordPress Developer Blog (versus network, site) meeting, which took place in the #core-dev-blog channel on the Make WordPress Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.. Start of the meeting in Slack.
Attendees: @greenshady @webcommsat @oglekler @ndiego @zeelthakkar @jagirbahesh @bcworkz (async) and @bph (facilitator).
Last meeting notes: Developer Blog editorial meeting summary 1 August 2024
Contributor updates
- Congrats to @ajlendelende and @aljullu to receiving their Documentation Contributor badges for their contributions to the Developer Blog.
- Call for contributors to take on What’s new for Developers roundup post for November? @greenshady @ndiego or I (@bph) will be right with you to guide you through the research as well as the writing part. If you want to take it on, come to the #core-dev-blog channel or DM either one of us.
Newly published posts since last meeting
Since the last meeting, we published the following articles
- Registering custom aspect ratios in WordPress 6.6 by @greenshady, reviewed by @marybaum and @welcher
- How to extend a WordPress block by @ndiego, reviewed by @fabiankaegy, @juanmaguitar, @welcher, and @greenshady
- Using Data Views to display and interact with data in plugins by @juanmaguitar, reviewed by @greenshady @welcher, @bph, @marybaum, @oandregal, and @eidolonnight
- What’s new for developers? (August 2024) by @greenshady, reviewed by@ndiego and @welcher
- Registering block templates via plugins in WordPress 6.7 by @greenshady reviewed by @aljullu, @ndiego, and @bph
Huge Thank You to the writer and reviewers!
Project status
The project board for Developer Blog content is on GitHub 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 be the repository owner. https://github.com/.
Issues closed
In review
In progress
On the to-do-list, assigned to writers
Topics approved, in need of a writer
If you are interested in taking on a topic from this list or know someone who would be a good person to write about them, comment on the Issue or ping The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” @bph in Slack either in the #core-dev-blog channel or in a DM.
New topics approved
The topic idea Modifying text with the HTML API in WordPress 6.7 needs to simmer some more to see if there will be more elaborate examples coming in the next major WordPress version. Justin will bring it back to the October meeting should the topic deemed mature enough for a blog post.
Open floor
@greenshady inquired about the possibility of translating the content of the Developer blog into other languages. Currently, there isn’t a formal proposal for a process and tools. It’s worth exploring, though. It was stated that it’s complicated for Rosetta sites, and it might not be easy to translate. It would be better if the translation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. can be put right into the admin (and super admin). If there is someone who translated an article, we could publish it on the Dev Blog under “other languages” and once we have a critical mass, we can create categories for Spanish, German etc. The bigger issue than the technological implementation is the recruiting and onboarding of translators to be contributors.
@bph is to reach out to the training team, to learn about their process, as they are a few steps ahead in working with translators.
@greenshady will open an issue, where we can follow up on discussion and progress.
Next meeting: October 3rd, 2024, at 13:00 UTC in the #core-dev-blog channel
Props to @greenshady for the review of the post.
#meeting, #meta, #summary
(published already )