Developer Blog editorial meeting summary, May 2, 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: @greenshady, @ironnysh, @ndiego, @milana_cap @bph (as facilitator), @bcworkz (async)

Last meeting notes: Developer Blog editorial meeting summary, April 4, 2024

Updates on the site

Congrats to our new contributors to get their Documentation Contributor badges: @jsnajdr @beafialho @magdalenapaciorek @ironnysh @jonsurrell @luisherranz @cbravobernal and @flexseth

Newly published post since the last meeting: 

Since the last meeting, we published articles by new writers and received support from more reviewers. (see above)

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 Progress:

Post on the To-do-list, assigned to writers.

Topics, approved in 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 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.” @bph in slack either in the #core-dev-blog channel or in a DM.

Topics closed

  • Learnings from two Site Migrations After consulting Jasmine, it was clear that her idea wasn’t suitable for the developer blog. I offered to assist her to publish some place else.

New Topics approved

Topics not approved:

There were no clear approval signals, and it seems the topics still need to narrow down the proposal to clear problem statements and suggested solutions. The discussions continue.

Open Floor

Next meeting: Jun 6, 2024, at 13:00 UTC in the #core-dev-blog channel

Props to @greenshady for review of the post.

#meeting, #meta, #summary

Developer Blog editorial meeting summary, April 4, 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: @greenshady, @matteoenna, @ironnysh, @colorful-tones, @magdalenapaciorek, @bph (as facilitator),

Last meeting notes: Developer Blog editorial meeting summary, March 7, 2024

Updates on the site

Authors reported a few hiccups with the code 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.. As soon as you wanted to attach a programming language for color coding, extraneous <br> tags appeared and rendered the code block useless. @ndiego, @greenshady and the #meta team are working on it to get this fixed asap.

Newly published post since the last meeting:

Since the last meeting, we published quite a list of articles, and we onboarded new writers and received support from more reviewers. Three first time writers with @meszarosrob, @jsnajdr and @beafialho Thank you! 🎉

Huge “Thank you” to the writers and reviewers for bringing fabulous content to WordPress!

Project Status

Ready to for publishing

Reviews needed

In Progress:

Post on the To-do-list, assigned to writers.

Topics still 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 writer about them, comment on the Issue or 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.” @bph in slack either in the #core-dev-blog channel or in a DM.

New Topics approved

@greenshady mentioned:

“There’s one other topic from last month that was not formally approved, @bph. I feel like with the additional info, we should probably take a look at it. (sorry for not bringing this up earlier): https://github.com/WordPress/developer-blog-content/discussions/230.”

There were no clear approval signals and seems the topic still needs clarification and will be revisited for next meeting.

Open Floor

Some clarification on the Playground articles/topics:

We originally had the topic approved:How to build a theme demo with WP Playground blueprints
Ronny took it on and wrote a fabulous Introduction/Overview of WordPress Playground. There was some discussion on how to proceed next. The consensus was that the Introduction post was a great post to have on the Developer Blog as each subsequent Playground tutorial could refer to it and doesn’t have to cover the basics anymore. Quite a few people from the Editorial group chimed in on the discussion and agreed to have it published. (note: the post is live now)

Ronny also wrote a Tutorial on How to use WordPress Playground for handovers. It was approved earlier. We still need a writer for How to build a theme demo with WP Playground blueprints 

Next meeting: May 2, 2024, at 13:00 UTC in the #core-dev-blog channel

Props to @greenshady for review of the post.

#meeting, #summary

Developer Blog editorial meeting summary, February 1, 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: @marybaum, @milana_cap @greenshady, @oglekler, second half @webcommsat, @bph (as facilitator),

Last meeting notes: Developer Blog editorial meeting summary, January 4, 2024

Updates on the site

Categories

The categories were updated a bit.

  • Blocks Development renamed to Blocks
  •  Visual Design renamed to Design
  • Deleted “Learning” isn’t every article a learning experience?

Since the beginning in 2022, we keep categories very high level, and become more specific with Tags.

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/ Action: label notifier

For the roundup posts, people can get notified when the next issue is available to share their team’s notes with the writer to be included in the next What’s new for developers post. If people want to get GitHub notification, please let me know and I’ll update the GitHub Notifier Action.

Author Profile links

With the redesign, author links now go to the 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/ profiles. 

Newly published post since the last meeting:

Huge “Thank you” to the writers and reviewers for bringing fabulous content to WordPress!

Project Status

Issues Closed as not planned

Seven Posts in Progress:

Eight post on To Do column

The Todo-List is growing, and we need to increase efforts to get them published.

Topics still 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 writer about them, comment on the Issue or 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.” @bph in slack either in the #core-dev-blog channel or in a DM.

Posts in need of reviews:

New Topics approved

Open Floor

@webcommsat brought to the meeting, the discussion from last night’s dev chat meeting about the Proposal to improve the FieldguideField 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. of the WordPress release, to see “what role the dev blog could possibly have in this as well as identifying what the blog already does and could do.

There is a wider discussion needed on communication and education of release features, but it would be good to start a more detailed discussion on potential and what is already aiding these areas within the dev blog. This can then feed into the wider considerations with other teams.”

Relevant links:

@webcommsat:
“The proposal now is not so much about a new version of a 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. appearing in dev blog, but looking at where and how we communicate and educate on a release, and what is needed. With the increased ability to segment to different audiences across the project, this could be a great opportunity. Hence, the wider input from marketing, docs, training, community, and the dev blog.

Being clear what happens in the dev blog already, giving tangible live examples to help those less familiar with the blog materials, and what could be potentially done would be a real cake yo the discussion.  With the segmentation, we have just in levels of developer knowledge, we can add a valuable insight too.”

@greenshady, @webcommsat also brought up concerns on ownership, availability of people during release time and bandwidth of contributors.

Next steps:
@webcommsat suggested: a mapping exercise would help, and happy to try to start one we can add to with ideas. We can then add links to examples of what we have already published.

Action: After WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Asia, schedule a Hallway Hangout with contributors from the editorial group and other teams to kick off work on a basic content map for a release and pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party existing efforts and identify gaps.

Next meeting: March 7, 2024, at 13:00 UTC in the #core-dev-blog channel

Props to@marybaum and @greenshady for review.

#meeting, #summary

Developer Blog editorial meeting summary, January 4, 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: @bph, @marybaum, @webcommsat, @greenshady, @ironnysh, @magdalenapaciorek

Last meeting notes: Dev Blog editorial meeting summary, December 14, 2023, Thank you to @webcommsat for the summary.

Updates and new post

The WordPress Developer Blog redesign is now live on site. It’s easier to read and better connected to the other Developer Resources. Contributors were asked to browse the new site and if they find something quirky, to let developers know via an issue on the GitHub repo.

There was only one post published since our last meeting:
Extending plugins using custom SlotFills by Ryan Welcher, reviewed by Justin Tadlock, JuanMa Garrido and Mary Baum.

Project Status

The project board, to follow along, is available 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/. There is a new column on the project board: “Needs writer”. (see below).

Posts in Progress:

To Do

The Todo-List is growing, and we need to increase efforts to get them published.

Topics 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 writer about them, comment on the Issue or 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.” @bph in slack either in the #core-dev-blog channel or in a DM.

Posts in need of reviews:

New Topics approved

Open Floor

During the project status section, the question was raised if there should be two additional columns on the project board to be more explicit as to the current state of a topic’s progression to publishing.

The discussion made clear that there is a need for more explicit steps between reviews on a writer’s journey to a published article. It also made clear that more details are needed about the first and second review entail and the responsibilities/task for authors and reviewers.

Proposed steps

Birgit will connect with other content producing teams to inquire about their process and learn how they handle reviews in the project boards. Meanwhile, we could test the following workflow for a few articles.

  • Writer writes and moves project card to “Ready for 1st review”
  • When done, reviewer moves the card to “Done w/ 1st Review”, adding comments to Google Doc or to the issue.
  • Writer edits and moves card to Ready for 2nd review
  • When done, Reviewer moves card to “Done w/ 2nd Review”, adding comments to Google Doc or to the issue
  • Writer edits some more and moves content to Blog – “Ready to Publish”
  • “Final Publishing check” – only a separate step for writers getting their first post over the finish line. Experienced writers, use the Pre-publish check list and publish their posts.

The two additional columns are now available on the project board.

Next meeting 1st of February 2024 at 13:00 UTC in the #core-dev-blog channel

Props to @greenshady for review.

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 – 07 September 2023

A 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/..

Attendees: @greenshady @marybaum, @milana_cap, @oglekler, @ndiego, @bph (facilitator) and @webcommsat (async)

Agenda

  • Site updates and new posts
  • Project Board
    • In Progress
    • Today
    • Needs Review
    • To be approved
  • Proposal for modification of 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. 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.
  • In-between meeting approval rounds for time sensitive post around releases.
  • Open Floor

Site updates and new posts

The Social image pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party was migrated to JetPack, and since then, we struggled a little to find a good way to automatically generate a decent Social Image when sharing posts on Social networks. We could use some design help for a universal template, as the current one is not the most attention-grabbing one.

If you want to catch up on the discussion, there is this GitHub Issue for the Theme

  • Request writers to select a feature image that works with the options in Jetpack
  • Set a default template similar to how it worked before, blue background + post title.


Nick Diego and Birgit Pauli-Haack will work on this.

Project Board

New Posts published since the last meeting.

Huge Thank You to the writers and their reviewers!! Fantastic job!

We published in July and August as many articles as in the three months before! So excited to see this! Incredible work! Thank you to all who contributed!

Posts in the works

On the To-Do list:

To be approved

These topics have been converted to issues, and the discussions are closed. Prospective authors who would like to contribute to the Developer Blogblog (versus network, site) are invited to select one of these to work on, that have not already been assigned an author.

In-between meeting approval rounds for time sensitive post around releases.

If there is a time sensitive topic, they will be voted on in an async fashion over two days. If there is further discussion is needed, it ought to happen 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/ discussion thread, and voting is deferred to the next monthly meeting.

Proposal of modification of the Field Guide

It would need more input on why a secondary digest version would be needed beyond the Field Guide, or if there is a way to improve on the Field Guide itself (most important issues on top). The original discussion takes place on the Make Blog. Proposal: An update to the Field Guide.

Next meeting

The next meeting of the Developer Blog Editorial Group will be on October 5, 2023 at 13:00 UTC in the core-dev-blog channel of the Make WordPress Slack. Contributors continue on GitHub.

Props to @ndiego for reviewing

#core-dev-blog, #summary

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

Developer Blog Editorial Meeting – 06 July 2023

A 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/..

Attendees: @greenshady (facilitator), @marybaum, @milana_cap, @mburridge @oglekler @bworkz . Asynchronous: @webcommsat

Agenda

  • Site updates and new posts
  • Project Board
    • In the works
    • Reviews needed
    • To be approved
    • new discussions on topics
  • Open floor

Site updates and new posts

Update 1:

The What’s new for developers? (June 2023) was amplified by official WordPress social media profiles (Twitter, LinkedIn, Facebook). It seems Facebook doesn’t pick up all the 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. 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.). Discussion via this issue on the Developer Blogblog (versus network, site) Theme repository. 

Update 2

To recruit new writers we added a Call to Action on every post: (also team effort with design, latest version by @greenshady)

screenshot of Call to action for new writers

How to identify topics that are available? If potential authors or reviewers are interested in a topic that is under discussion, you can add a comment to the a discussion issue 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/. Potential authors can identify if someone is working on a topic or what this person should do to claim the topic. If a GitHub discussion on a potential topic is locked and the issue is assigned to someone, the this topic has been taken.

Update 3:

At WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe 2023, a group of contributors identified a GitHub space where Developer Blog writers and Learn WordPress faculty can upload code examples, themes and plugins that are used for educational content.

Once there are a few basic rules in place, we can give access to it and also move existing repos from personal to the Learn WordPress GitHub organization. Huge thank you to @psykro and @courane01 for awesome team work on this. 

Project Board

Closed issue: “not planned” How to add starter content to WordPress themes View comment on the issue

New Posts published since the last meeting:

Posts in the works

On the To-Do list:

To be approved

The following topics were approved:

These topics have been converted to issues and the discussions closed. Prospective authors who would like to contribute to the Developer Blog are invited to select one of these to work on, that have not already been assigned an author.

The group discussion on the post 10 things that all WordPress plugin developers should avoid quite lively. The discussion continues on GitHub issue itself.

Regarding the topic idea: A first look at the Interactivity API. As the feature hasn’t been released yet, there is time to flesh out the topic some more and bring it back to the editorial meeting later this year.

Open floor

@greeshady inquired about formatting a post title that belongs to a series. Example: “Beyond 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. styles: part 1: integrating the wp-scripts package into themes”

Mary Baum has two ideas:

  • use a comma to separate the series and the part number, then we only have one colon, or
  • make the series and part a kicker (= a slug above the titel)

@mburridge brought the latest topic idea to the attendee’s attention: Periodic video round-ups by @eidolonnight. The biggest hurdles for such a round-up would be the external link policy. In the meantime, the discussion has been closed.

Next meeting

The next meeting of the Developer Blog Editorial Group will be on August 3, 2023 at 13:00 UTC in the core-dev-blog channel of the Make WordPress Slack. Contributors continue on GitHub.

Props or reviewing this post to @webcommsat and @oglekler

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

Developer Blog Editorial Meeting – 01 June 2023

A 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/..

Attendees: @greenshady (facilitator), @marybaum, @milana_cap, @ndiego, @webcommsat, @mburridge

Agenda:

  • Site updates and new posts
  • Project Board
    • In the works
    • Reviews needed
    • To be approved
    • new discussions on topics
  • Open Floor

Site updates and new posts

The “What’s new for developers? (May 2023)” post was tweeted about from the official WordPress social media accounts. Attendees were encouraged to re-share to their networks.

Project Board

In the works

New Posts published since the last meeting:

Topics that are currently in progress:

It should be noted that Adding custom color options for blocks has had a change of direction from what was previously approved, but this change has been approved by @greenshady and @bph.

The following posts have previously been approved and are on the to-do list. Some of them already have authors;

Reviews needed

Currently only one post is in need of review:

To be approved

The following topics were approved:

These will be converted to issues and the discussions closed. Prospective authors who would like to contribute to the Developer Blogblog (versus network, site) are invited to select one of these to work on, that hasn’t already been assigned an author.

New discussions on topics

Two topics are under discussion and have not yet been approved:

Regarding the first of these, it was considered that the topic is not yet defined enough. It also mentions using a third-party theme and a third-party pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party which prompted a discussion on whether third-party themes and plugins should be promoted in the Developer Blog. The consensus on this was that they should not be promoted in this way.

With regards to the second topic that was discussed, it was considered that the remit is too broad but that there may be some good ideas for individual posts contained within it.

Open Floor

@greenshady asked whether it might be best to allow linking/mentioning to only coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-owned plugins/themes (i.e., official products), retaining a policy of not linking to third-party plugins/themes?

There was some disagreement on this but eventually the consensus was that only mention of wp.org made plugins/themes should be allowed.

@greenshady also suggested that it might be possible to draw a hard line on this, but allow the editorial group to decide when an edge case pops up.

A distinction was made between personal repos used for demo code in a post, and “products” such as themes and plugins in the WordPress repository.

A ticketticket Created for both bug reports and feature development on the bug tracker. will be opened to continue this discussion.

Also briefly discussed at the end of the meeting was updating the guidelines to make the review process clear.

Props to @greenshady for reviewing this post.

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