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, @ndiego, @webcommsat, @psykro, @colorful-tones, @milana_cap, @mobarak, @magdalenapaciorek, @juanmaguitar, @bph (as facilitator). @ironnysh and @bcworkz (async)
Last meeting notes: Developer Blog editorial meeting summary, May 2, 2024
Updates on the site
The site has passed the first 1,000 subscribers Don’t want to miss the next blog post? Subscribe. And please share the links with your network (versus site, blog) as well. @webcommsat volunteered to submit an amplification request to the WordPress marketing team to celebrate the milestone with the community.
Newly published post since the last meeting:
Since the last meeting, we published four articles.
- Building a book review site with Block Bindings, part 2: Queries, patterns, and templates (published after the meeting) by Justin Tadlock, reviewed by Nick Diego and Birgit Pauli-Haack
- Setting up a multi-block plugin using InnerBlocks and post meta by Nate Finch, reviewed by Birgit Pauli-Haack, Reyes Martinez, Nick Diego and Ryan Welcher.
- Building a book review site with Block Bindings, part 1: Custom fields and block variations by Justin Tadlock, reviewed by Birgit Pauli-Haack, Nick Diego and Ryan Welcher
- What’s new for developers? (May 2024) by Justin Tadlock, reviewed by Nick Diego and Ryan Welcher.
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/.
In review
In Progress:
Post 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
Topic not approved:
The WordPress Developer Survey – A regular survey could give “the whole project a lot of useful data” There were concerns about logistical challenges and needs further discussion with core Core is the set of software required to run WordPress. The Core Development Team builds WordPress., the marketing team in its new media focus, and with Learn WP. The next step as identified as “to define the purpose of the survey, and what questions would be included/not included.” The discussion continues on GitHub
Open Floor
@webcommsat Inquired about topics schedule around the WordPress 6.6 release. There are a few posts already on the list or were just approved. As almost all topics are assigned to writers. Contributor’s bandwidth will determine the publishing timeline.
@colorful-tones requested input and possible resources on using Playground for his upcoming post on the developer Blog: a Good starting point is the Blueprint Gallery and an example from @greenshady on GitHub.
@colorful-tones has slightly changed the topic of his post he has been working on. It was originally thought to be an Interactivity API An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. tutorial, but as you can read in the issue he went a different route. It was concluded that “it’s still a valuable post for the Dev Blog”, “the new focus is still really useful” and “the underlying method doesn’t need to be the same as the originally proposed method”
Next meeting: July 4, 2024, at 13:00 UTC in the #core-dev-blog channel
Props to @greenshady for review of the post.
#meeting, #meta, #summary