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 on Slack.
Summary from last meeting on September 5, 2024 – props to @bph
Agenda
Site updates and new posts
Project Board
- In Progress
Topics needs review
Topics need writer
- Topics to be approved
Open Floor
Thanks to everyone who has contributed to the last meeting: Summary of the Developer Blog editorial meeting on 5 September 2024. Thanks to @bph for putting these together.
No comments on the previous meeting actions and notes.
Site updates and new posts
Updates
Congratulations to Troy Chaplin (@areziaal ) for his first Developer Blog article and obtaining the Documentation Contributor badge.
The Dev Blog is always keen to welcome new contributors.
New posts
A big thank you was shared to both writers and reviewers. Also a thank you to everyone who comments on a proposal and helps move it forward to publication. It really is a community effort.
Project board status
@webcommsat: To encourage async contribution and those who are unable to join, as well as gather wider feedback, do add comments after the meeting to the 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/ tickets that items in this section are linked to.
Optimizing your WP_Query queries for better performance
On the first item, optimizing your WP_Query queries for better performance, the second version is available to review. I have it down as a task for later today. Is anyone else also planning to go through it?
Birgit and I have been going through this last week, and I am hoping to catch up with Olga about it too.
Aware that WCUS has been in the middle. Thanks Justin and Milana for your comments on this too. Justin and Milana have offered additional assistance on GitHub.
Create Figma designs for WordPress Block Theme
There are some comments already on the ticket Created for both bug reports and feature development on the bug tracker.. Birgit has suggested some actions.
If anyone else has comments, please can you add them to the ticket.
Posts: in progress
- Case Study: How Pew Research Center is using the interactivity api to use blocks as interactive components
- Why you might not need a child theme
- Customizing and extending the Formatting Toolbar
- How to build a theme demo with WP Playground blueprints
- Tutorial on how to create custom components
- An overview of available directives for the Interactivity API
- Classic themes: tutorial on moving away from widgets to template parts
@ndiego will follow up on Customizing and extending the Formatting Toolbar.
@greenshady: there has been a roadblock with the Playground blueprint one. There’s a bug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. that’s likely to hold up its progress for a bit. The issue has already been reported and some discussion around it.
Posts: to-do column, assigned to writers
- Overview of the coding standards tooling available to WordPress developers
- Tour Guide for First-time writers on the Developer Blog
- Migrate classic sidebars and widgets to block for themers
- Overview of “block theme” stuff you can do with classic/hybrid themes
- Performance best practices
- Creating a low-code block theme development workflow with WordPress Playground and the Create Block Theme plugin
- You don’t need CSS for that: All the ways you can use theme.json for styling – @greenshady will be looking into this.
- Exploring post formats in a block theme world (maybe with 6.7 additions) – this relies on some things that may not be part of WordPress 6.7. @greenshady doing a progress check on it, and believes it’s possible to still do a good walkthrough of what you can do without the extra changes in Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
- How to add `contentOnly` editing support to a custom block – @ndiego: will start working on the contentOnly one once 6.7 RC1 has passed.
Approved topics that require a writer
To be approved
Lots of new ideas coming in.
The discussion in this section of the meeting focus on the topic in general and not a review of the proposal.
Modifying text with the HTML API in WordPress 6.7 (not approved, about to be closed in favor of this new topic/idea by Nick Diego N ways to use the HTML API in WordPress#313
To give more context from the last meeting:
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. @greenshady has brought it back to the October meeting should the topic be deemed mature enough for a blog post.
Justin commented on the discussion: “I’m leaning toward closing this one in favor of N ways to use the HTML API in WordPress #313
Let’s get some of those foundational examples in place and wait for set_inner_html() for some ideas around this.“
The ticket was left open in case anyone had additional ideas, and will be closed shortly.
Two new topic proposals from @greenshady before this meeting:
@greenshady: On those two topics, particularly Block 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. Bindings, they came up late in the Dev Cycle. I think they’d be solid additions to showcase WP 6.7 features. I need to do some more testing myself to roll out better outlines. But anyone is free to pick them up before I get to them (as always).
@webcommsat thanked everyone for participating. @bph will create issues for each of the approved topics, so they can get on the to do-list.
Open floor
Proposal for new content type:
- @greenshady raised a separate proposal about a content type rather than a specific topic: Snippets/shorts/bite-sized tutorials. “I have a ton of code that doesn’t make sense for long-form tutorials, but they’d make great quick tutorials that’d only take a couple of paragraphs and a single code block to explain. I think they have a place on the Dev Blog, but I wanted to get feedback from you all.”
- The approved conditional pattern topic would be ideal for this sort of thing.
- He asked if anyone was opposed to doing some of these smaller tutorials and adding a custom category The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging./tag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) for them (snippets? shorts?).
- @meszarosrob felt there was value in this idea. Many times I have been inspired by seeing what somebody did.
- @greenshady: if necessary, offered to write the conditional patterns one as a proof of concept and get feedback from the group
@webcommsat reminded people to continue to comment on the tickets on GitHub and add ideas for future pieces. Thank you to all contributors during the last month.
Next meeting
The next Developer Bog editorial group meeting will be on November 7, 2024, at 13:00 UTC in the #core-dev-blog channel.
Props to @bph for reviewing the notes.
#dev-blog, #summary