Summary of the Developer Blog editorial meeting on 9 January 2025

Summary of the WordPress Developer Blogblog (versus network, site) meeting, which took place in the  #core-dev-blog channel on the Make WordPress SlackSlack 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: @areziaal, @oglekler, @greenshady, @bcworkz (async) @cwhitmore (async) @annezazu (async) and @bph (facilitator).

Last meeting notes: Summary of the Developer Blog editorial meeting on 5 December 2024



Updates on the site

We started implementing a suggestion we received over the last few months for two more content post types: Snippets and Videos. You can see a list of available snippets here. They are shorter posts and solve one particular task/problem. There is also a separate async meeting format for Snippet approval between the monthly meeting

Video CPT only has one post for now: the recording of Developer Hours: Improve your workflows with WordPress development tools. There is the hope that over the following months, we can start a design process to integrate those two additional custom post types more prominently on the developer blog.

Newly published posts since last meeting

Huge thank you to the writer and reviewers! 🎉👏

Project status

The project board for Developer Blog content is on 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 be the repository owner. https://github.com/.

In review

In progress

On the to-do-list, assigned to writers

We have approved topics that still require a writer:

If you know someone who could tackle any of those topics, please comment on the particular issue

New topics approved

Open Floor

New leadership

@bph “After two years of leading the WordPress Developer Blog, it’s time for me to step back and let others take the reins! I’ve enjoyed creating and managing processes, running meetings, and working with all of you. However, due to other commitments, I need to pass the torch.

This is a fantastic opportunity for someone (or a few someones!) to take on a leadership role within the WordPress open-source project. Here are some of the responsibilities involved:

  • Facilitate monthly meetings (tentatively shifting to 15:00 UTC).
  • Manage the editorial calendar and content pipeline.
  • Onboard and support new contributors.
  • Guide reviewers and writers through the review process.
  • Oversee content publishing, ensuring quality and adherence to standards.

By taking on this role, you’ll gain valuable leadership experience, contribute to a vital resource for WordPress developers, and expand your networknetwork (versus site, blog) within the community.

I’ve already spoken with @marybaum, who is potentially interested in helping out. Announcement on the channel of January 10th, 2025:

I am happy to announce that @marybaum has agreed to take on the project WordPress Developer blog. She is a long-time WordPress contributor on the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team and a brilliant editor. I am very grateful to see the project in such good hands. Please support her as enthusiastically as you supported me in the project.

But, ideally, we’d have a few people sharing the responsibilities. If you’re interested, please contact me on WPSlack by January 23rd or leave a comment on the summary post of this meeting with a brief explanation of your relevant experience and why you’d be a good fit. (edited) 

What’s new for developers Round up post

@greenshady

“In other news, I’d love to have someone (or multiple someones) to volunteer for the What’s new for developers? monthly roundup.

The goal was to always rotate this through various writers so that it would be written from different viewpoints. I’m writing the January 2025 edition, and I’m happy to onboard anyone for February 2025 and set up the doc (we have a reasonably standard formula for it at this point).  I won’t be able to write this for February for sure and possibly afterward for a couple of months at least. Feel free to DM me, pingPing 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.” me here, or reply to the meeting summary post when it’s published if you’re interested in pitching in here

Upcoming meetings

  • Next Editorial Group meeting February 6th, 2025, at 15:00 UTC (!)📣
  • Next Async Snippet Approval meeting on January 22/23, 2025

Both happening in the #core-dev-blog channel

Props to @greenshady for review.

#dev-blog

#meeting, #summary

Summary of the Developer Blog editorial meeting on 5 December 2024

Summary of the WordPress Developer Blogblog (versus network, site) meeting, which took place in the  #core-dev-blog channel on the Make WordPress SlackSlack 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: @ndiego @areziaal, @webcommsat (async) @bcworkz (async) @milana_cap (async) @oglekler (async) and @bph (facilitator).

Last meeting notes: Summary of the Developer Blog editorial meeting on 7 November 2024



Updates on the site

Updates

Newly published posts since last meeting

Since the last meeting, we published the following articles

Huge Thank You to the writer and reviewers! Awesome work around!

Project status

The project board for Developer Blog content is on GitHub.

Closed, not planned. 

Not all good ideas come to fruition. Sometimes plans just don’t work out.  After some conversation, the following issues/discussions were closed: 

In review

In progress

On the to-do-list, assigned to writers

We have approved topics that still require a writer:

If you know someone who could tackle any of those topics, please comment on the particular issue

New topics approved

There was no Open Floor discussion

  • Next Editorial Group meeting January 9th, 2025, at 13:00 UTC .
  • Next Async Snippet Approval meeting on January 22/23, 2025

Both happening in the #core-dev-blog channel

#dev-blog

#meeting, #summary

Dev Blog editorial meeting summary, October 3, 2024

Summary of the WordPress Developer Blogblog (versus network, site) meeting which took place in the  #core-dev-blog channel on the Make WordPress SlackSlack 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 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 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 ticketticket 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

  1. Case Study: How Pew Research Center is using the interactivity api to use blocks as interactive components
  2. Why you might not need a child theme
  3. Customizing and extending the Formatting Toolbar
  4. How to build a theme demo with WP Playground blueprints
  5. Tutorial on how to create custom components 
  6. An overview of available directives for the Interactivity API
  7. 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 bugbug 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

  1. Overview of the coding standards tooling available to WordPress developers
  2. Tour Guide for First-time writers on the Developer Blog
  3. Migrate classic sidebars and widgets to block for themers
  4. Overview of “block theme” stuff you can do with classic/hybrid themes
  5. Performance best practices
  6. Creating a low-code block theme development workflow with WordPress Playground and the Create Block Theme plugin
  7. You don’t need CSS for that: All the ways you can use theme.json for styling@greenshady will be looking into this.
  8. 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 CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
  9. 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 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. 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 categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging./tagtag 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

Dev Blog editorial meeting summary, December 14, 2023

Summary of the WordPress Developer Blogblog (versus network, site) meeting which took place in the  #core-dev-blog channel on the Make WordPress SlackSlack 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: @bph, @marybaum, @ndiego, @webcommsat, @greenshady, @ironnysh. Apologies: @milana_cap

Last meeting links: summary from last meeting on November 2, 2023 – props to @milana_cap for facilitating and @webcommsat for the summary.

Updates on the Developer Blog site 

  1. Central documentation area
    • Following up on a previous discussion for a central area for documentation for writers, reviewers and admins, @bph has opened the Wiki space on the GitHub Repository. This will put all the little details into one place and an excellent way to organize the pieces.
    • In early 2024, she will provide a tracking issue for all the updates and new docs that need to be added, and a request for a few of the editorial group to assist in writing and reviewing. 
  2. Redesign
    • The Developer Blog is part of the Redesigning Developer Resources and a call for testing.
    • @ndiego has addressed some 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. feedback on the PR yesterday, and it is nearly complete. This update will standardize the Blog to match the pending updates to Developer Resources and provide a solid platform for additional iterations in the future. He highlighted this update will make easier future updates. By using a 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. theme, future changes to the templates can be done more easily and directly. In addition, the Blog will inherit all the new functionality that has been developed for the Developer Resources site, such as, consistent spacing sizes, font sizes, local navigation, etc. Any further feedback is welcome.
    • The meeting thanked @ndiego, the Meta team and all involved for all their work on this.
    • Latest start of production expected early next week. Developer Resources will launch first, then the Blog updates. Further updates can be followed in the #website-redesign channel on Slack. 

Project board and status

Project Board on the Blog repo in 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 be the repository owner. https://github.com/.

New posts

Six new Posts published since the last editorial meeting.

@bph said: “A huge thank you to the writers, and their reviewers!! Fantastic job!”

Actions:

  • Proposed by @webcommsat to include co-authors, editors and detailed reviewers names in this list in future meetings/ summary to reflect their input and time. This will also help to encourage more people to volunteer their skills to review, edit and writers to work together on a post. @marybaum and others confirmed the time commitment for a co-author or editor can be considerable, and this can be reflected in the inclusion of their 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/ ID. The inclusion of this additional detail was agreed to be added at the meeting. In the existing checklist, the principal writer of a post adds props to those who have been involved in the props channel on Slack.
  • Suggestions for people who are good copy editors from other WordPress contributor teams to be shared with @bph for onboarding in 2024 when some additional documentation on expectations and tools is ready.

Posts in progress

In this and the following sections of the meeting summary, the links go to the WordPress Developer Blog repo on GitHub.

To-do list

In the last few months there has been a slowing down of writing and reviewing, due to contributors’ other demands, the release, and their own work commitments. Increasing the number of volunteers in these areas will help address this. Action, as above, on identifying good copy editors from other teams.

Actions:

  • As Dev Chat has now concluded for 2023 and will be back in the second week of 2024, instead of @webcommsat sharing the monthly call out of posts that need writers in that meeting, it was agreed to wait until the next editorial meeting on January 4, 2024. 
  • @webcommsat will include a link to the summary of the meeting in a comment on the Dev Chat summary when published.

Future topic ideas for approval

Many new ideas for topics have come through or are in the pipeline. They are not all ready to proceed.

All the topics below were given a positive vote. Further scoping and drafting to follow. Any other comments can be added on the individual GitHub tickets listed.

Discussion on advance review of the approval list:

  • the list is now shared in the agenda reminder earlier on the day of the meeting; however, this may not give non-sponsored contributors or those in other timezones or unable to read the items that day the ability to comment most usefully or raise questions
  • the topic areas are available on the GitHub repo as live tickets and can be reviewed there at any time of the month, and comments added in advance of the Editorial meeting
  • the aim is to encourage some discussion of those topics and to flesh out an article and identify different angles
  • Actions:
    • agreed for a link to new topics to be shared regularly in the Dev Blog slack channel to raise awareness and interest in the topics and potential writers stepping forward
    • to encourage those putting ideas together to have them on the GitHub project board by a certain date (if possible) before each meeting. It may not always be possible, but in principle, encouraging this will improve the process, a more informed discussion, allow for more asynchronous contributions, and a way of encouraging engagement in the channel and discussion on GitHub. 

Open floor

  1. Idea for a potential post: @marybaum – “From no-code to no-hands: three ways to generate posts in a taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. term” case study
  2. @webcomms raised a previous discussion in the Slack channel. She, like many others in the group, receives requests from developers wanting to know what order to learn WordPress development, tips to help become or familiarize with WP development, etc.
    • Actions: for a discussion to be created in GitHub spaces.
    • It fits our scope
    • Similar posts to be identified from the Dev Blog
    • This will fit well with the discussion of learning paths, the Training team is tackling..

Next meeting

The next Developer Bog editorial group meeting will be on January 4, 2024, at 13:00 UTC in the #core-dev-blog channel.

#dev-blog, #summary

Developer Blog editorial meeting summary: November 2, 2023

complete transcript of the meeting can be found in the #core-dev-blog channel in Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

Agenda

  • Site updates and new posts
  • Project Board
  • In Progress
  • Today
  • Needs Review
  • To be approved
  • Open Floor

Notes of the last editorial meeting on October 5, 2023 – props to @webcommsat

Props to @milana_cap for facilitating the meeting.

Attendees for Nov 2, 2023 meeting: @milana_cap, @greenshady, @marybaum, @webcommsat, @oglekler, @ndiego .@bph was unable to attend – thanks to Birgit for preparing items in advance for the meeting.

Site updates and new posts

New Posts published since the last meeting:

@milana_cap shared: “A huge thank you to the writers, and their reviewers! Fantastic job!”

Project Status

Posts In progress

To-do list

  1. A tutorial about the highlights of the browser and focus modes of the Navigation Block
  2. Using the Grid layout type for theme creators Justin Tadlock: this will wait as it is still in experimental phase.
  3. How to manage block governance
  4. Tutorial on building block-based templates in classic themes
  5. Tutorial on building patterns and block styles with Details/Summary block Justin Tadlock will be working on this.
  6. Optimizing your WP_Query queries for better performance Olga Gleckler
  7. How to disable specific blocks in WordPress
  8. How to add commands to the command palette Writers needed, Justin volunteered if needed.
  9. Creating a custom External Template for the @wordpress/create-block package
  10. Overview of the coding standards tooling available to WordPress developers
  11. An overview of the “Auto-inserting Blocks” feature coming in 6.4. This initial proposal is now being discussed in this ticket – Note timescale for this post will be post 6.5.

@marybaum is revising the long-form type post. @greenshady to support with code samples and @webcommsat with proofing.

Writers are needed for the remainder of the items on the to-do list. Call to be shared in dev chat when possible.
Wider calls to encourage people to add to the relevant 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 be the repository owner. https://github.com/ issue if they can assist with collaborating on these items.

Actions: If you know someone or want to write one of these posts yourself, comment in the Developer-Blog channel on Slack.

Reviews needed

There are no posts currently in the queue marked ready for review. More are expected with the release slated for November 7, 2023.

To be approved

  • At the moment, the queue for items for discussion or topics for approval is empty.
  • @greenshady to add some new topics for next month’s meeting.
  • @webcommsat: From early signs of what could be in 6.5, I think there will be quite a few use case blogs to come out of there in the future.
  • @milana_cap: to propose a few WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ topics.
  • @marybaum: potentially one on using the post-content 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. inside the Cover block, and a topic related to a block theme.
  • @ogleckler: proposed a topic on design in Figma for blocks. Discussion followed in the meeting: @webcomms suggested sharing the idea with the Design team and with the release contributors who worked with Figma for potential interest in scoping/ key inclusions, or to take it up to write. Strong interest in the editorial group about a post on designing a block theme in Figma. New issue created for the Dev Blogblog (versus network, site) to take this forward.

@webcommsat proposed that in general, adding ideas for topics to the board makes it:

  • easier to raise awareness and target potential contributors 
  • adding a basic scope /inclusions from discussions in the editorial group
  • there have been a couple of discussions in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and documentation during the release journey about use case of features. Some of these would be potentially good dev blogs. Helping scope out some of these topics can help people commit to taking them on or to better understand the next steps. This has been seen with other new topic proposals
  • agreement from the group on this and promoting potential contributors to add ideas to the board
  • @webcommsat with @codente and @nalininonstopnewsuk have been marking items up from the 6.4 release documentation tracker where there has been some interest already in writing about particular items and will encourage these ideas for the Dev Blog board.

Open floor

1) @greenshady raised a conversation about resolving how writers upload images to their draft posts.  

Issue: Slack convo. In this instance, the published post was missing two images. They later had to be pulled from the original Google Doc and the post updated. Two older posts needed the same solution too where an image URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org was added which was no longer valid.

Solution: make sure folks are uploading images to the Developer Blog WordPress install and not hotlinking from Google Docs or elsewhere. I updated two older posts in the past week where this was done and the image URL was no longer valid. 

Further questions: any guidance needed on checking images uploaded have been checked for virus/malware? The system does not allow upload of svg files for this reason.

Actions:

  • add further instruction in the contributing guide for writers, the checklist on GitHub, and to prompt checks when they are ready for the post to be edited. @greenshady to add a ticketticket Created for both bug reports and feature development on the bug tracker. for these additions.
  • @webcommsat requested to add to the checklist/ guide for images to be given a useful name and alt text to be added when uploaded. All agreed and a sub section on images suggested, and to include guidance on image sizes, image naming and alt attributes.

2) Discussion around using using the /blog URL instead of /news for the Dev Blog

Clarification shared that this would not change the URL, just add a redirect from /news to /blog.

@ndiego shared: The reasoning behind using /blog is to match the brand name, “WordPress Developer Blog”. This would be too build on the branding cultivated in the past year around this name.

Discussion points:

  • only news items on the blog are the round-ups
  • concern that ‘blog’ url might give an impression that it is personal opinion rather than posts from the project WordPress. Alternative suggestions for its name were suggested, including “guides”, “tutorials”, “guidelines”, “journal”, “writings”, “Developments”, but not felt to cover the breadth of content, would need a rebranding exercise, and would mean potential duplication/ overlap with Learn WP content. Suggested a way of addressing reservations about url ‘blog’ could be to add further clarification in the purpose and writing guidelines so that it was clear to potential writers that articles were not personal blogs.
  • @webcommsat highlighted that there is a wider discussion to be continued on overlap and working alongside Learn WordPress in both directions.
  • @ndiego clarified the specific aim of the redirect question is to help people find the Developer Blog not to change or widen its current scope. He confirmed it is about search and helping people find it. There are people typing in developer.wordpress.org/blog and wonder why it didn’t go to the WordPress Developer Blog.
  • @greenshady raised that /news was not the preferred option originally to match the scope, but there was an issue early on where there was a potential plan to reserve /blog . The option to use /blog is now possible from the information shared by Nick.

Solution proposed:

  • to go ahead with the redirect and there by keep both /news and /blog in use, subject to further discussion with @bph on her return
  • relook at the published purpose/ guidelines for writers to make sure there is no potential misunderstanding for submissions/ writing. This is turn would save time for this group, writers and reviewers. Add a list of the type of articles that appear on the blog to assist contributors to know how to target pitches, articles and language, as well as helping give some next steps for new writers.

3) Trying to avoid duplications of series names in the Developer Blog and other parts of the project, e.g. Learn WP
@webcommsat highlighted this topic to avoid confusion from both audience and search engine perspectives, especially where items are not cross-linked.

For example, there is a “What’s New for Developers” series on the Blog, so it would be better to avoid having the exact replica title in other public-facing resources from the project. Where one communication is a follow-up to an existing one elsewhere in the project, it should reference it to help people find similar resources and help their learning journey. There may need to be some manual proactive cross-linking.

Solution proposed:

  • cross-linking to be encouraged, and this can help for search in terms of authenticity and credibility of information about WordPress, and in terms of readers’ journeys.
  • avoiding exact duplication or too similar naming of titles. Specific titles that cross link should be less likely to cause confusion, eg Hallway hangout – What’s New for Developers in 6.4 covered topics from the article series on the Blog, and cross-referenced in the event itself. Suggested that posts about a forthcoming event or write-ups would benefit the user / attendee with cross-referencing.
  • the discussion also highlighted how more synchronization between Learn WP and the Dev Blog might be helpful
  • a recommendation to add excerptExcerpt An excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox. to posts, which makes it so much easier for users, and shorter search result descriptions in the P2P2 A free theme for WordPress, known for front-end posting, used by WordPress for development updates and project management. See our main development blog and other workgroup blogs. and the internet too.

Next meeting

Update: change to the next meeting date. It will now take place on December 14, 2023 at 13:00 UTC.

#core, #core-dev-blog, #dev-blog, #meeting

Developer Blog editorial meeting summary: October 5, 2023

complete transcript of the meeting can be found in the #core-dev-blog channel in Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

Notes of the last editorial meeting on September 7, 2023 – thanks to @bph

Attendees: @bph, @milana_cap, @greenshady, @marybaum, @webcommsat, @oglekler

Site updates and new posts

Since the last editorial meeting, the following posts have been completed by writers and reviewers.

@bph shared a huge thank you to the writers, and their reviewers! Fantastic job!

Project board

Posts in progress

Posts for review

At the time of the meeting time, these posts were in need of review.

2nd review: New developer focused workflow article about how the login and registration works in WordPress.
1st review: A tutorial about the highlights of the browser and focus modes of the Navigation Block
1st review: #151 Type series post 3: Setting body-conscious type for long-form text#156

Action: comment on the 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 be the repository owner. https://github.com/ issue if you can review.

Posts on the to-do list

These were all approved topics, with writers assigned:

On the to-do list

@webcommsat to look at how to highlight call for writers on Dev Chat agendas post 6.4.

Posts that need writers

Two topics are still looking for writers:

Actions: If you know someone or want to write it yourself, post in the Developer-Blog channel on Slack.

Posts for approval

The group approved one new topic:

Open floor

Discussion to encourage writers to share GitHub tickets, Google Docs, public preview links to accompany a call for review in Slack to help reviewers. When writers and reviewers contributing in opposite time zones, these links can be particularly helpful.
Action: to guide contributors to use GitHub to capture comments/ changes, including when posts have moved to the CMS phase.

In the last quarter, many new writers have been inducted to the Dev Blogblog (versus network, site). Proposed a post for new writers with input from contributors recently joined.
Action: @webcommsat and @bph to take forward the post.

Agreement to allocate Documentation badges to contributors for writers and reviewers of the Dev Blog.
Action: @bph and @milana_cap

#core, #core-dev-blog, #dev-blog, #meeting

Developer Blog editorial meeting summary: August 2, 2023

Site updates and new posts

Updates

The dev blogblog (versus network, site) is going to use the Learn WordPress organization repository on 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 be the repository owner. https://github.com/ to host code samples, gists and the like. That will save writers and editors from having to use their personal GH accounts. @greenshady has volunteered to be the first to use it, and the board will develop some processes and guidelines from his experience. If you have thoughts on anything surrounding these repositories, please share on this GitHub issue.

The Marketing team as of August 2, the Marketing team is sharing Developer Blog posts on the official WordPress social profiles.That means a post author has one more step on the post-publish checklist—write some copy for the social-media post and add it to the issue for the post.

New posts

Project board

Posts in progress

At meeting time, these posts were in review:

And the second of @marybaum‘s type series was In Progress.

Those posts are all now live on the blog.

Posts on the to-do list

These were all approved topics, with writers assigned:

One topic needed a writer: Optimizing your WP_Query queries for better performance

And A tutorial about the highlights of the browser and focus modes of the Navigation was on hold pending the publication of the 6.3 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. 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..

New topics

The group approved two new topics:

Open floor

@webcommsat pointed the group to a Slack discussion on sustainability.

The group needs some ways to approve topics outside the monthly meetings. As it stands, potential authors are having to wait more than a month for a green light. See the discussion.

#core, #dev-blog, #meeting, #core-dev-blog