Progressive Web @ WCUS Contributor’s Day

From you can get a sense of the large number of rich web APIs that are standard today. This is often referred to as the Progressive Web Platform. With these capabilities, alongside the use of modern development workflows and coding and performance best practices, web developers can create great user-first experiences on the web.  Similarly, the WordPress platform has also been evolving steadily since its inception, and most recently, sweeping changes are being introduced with the development of Gutenberg.

An important part of the continued evolution of WordPress is the integration of modern Web Platform capabilities into core when possible, and into plugins and themes as well. We have been working on a project aimed at integrating the Service Workers API (#36995) and Web App Manifests (#43328) into WordPress core, as well as expanding core support for HTTPS (#28521). Right now this effort is been advanced under the umbrella of a PWA feature plugin.

Up until now this feature plugin has primarily been collaboration between XWP and the Chrome team at Google. The plugin is a technology preview for a core foundation that themes and plugins can use to create new user experiences, like being able to access a site while offline. Service workers will also make it possible to do offline editing in Gutenberg. To be successful, the project needs the participation of the WordPress core community and wider ecosystem. We have been delaying the feature-as-plugin proposal until after Gutenberg launches, but now that WordPress 5.0 is around the corner, we want to start the formal feature-as-plugin process.

We will be at the WCUS Contributor Day in Nashville next week, and we want to discuss the current status of the PWA feature plugin and a roadmap for the work ahead. If you are interested in learning more about this proposal and possibly contribute to the project, we would love to chat.

#progressive, #pwa, #service-workers, #wcus

PHP Meeting Recap – November 26th

This recap is a summary of our previous PHP meeting. It highlights the ideas and decisions which came up during that meeting, both as a means of documenting and to provide a quick overview for those who were unable to attend.

You can find this meeting’s chat log here.

Chat Summary

  • @schlessera introduced the idea of using the concept of “feature flags” to be able to commit experimental code to be tested into trunk without immediately affecting everyone by default. Features hidden behind these feature flags would be opt-in through a mechanism like a setting in wp-config.php. The WP Beta Tester plugin could maybe be updated to provide a graphical interface to enable such feature flags.
  • The general format for feature flags in the wp-config.php could be something like the following:
    define( 'WSOD_PROTECTION', getenv( 'WSOD_PROTECTION ) || false );
  • This allows for direct hardcoding of the value, as well as for passing it in via the server environment.
  • Discussion revolved around whether such a “feature flag” system would actually improve anything. For code to be considered “committable” to trunk under a feature flag, conditions would probably be the very same than for it to be committable to trunk directly.
  • @nerrad is concerned about the code churn that such feature flags could add to Core development.
  • @sergeybiryukov is concerned that feature flags would create a new precedent in WordPress and would prefer to have us either commit the required hooks into Core to provide WSOD protection through a plugin, or to iterate directly in trunk as this has been done before the advent of feature plugins.
  • An alternative approach would be to make branches available through the WP Beta Tester plugin. However, branches are hard to keep in sync with trunk, especially in SVN.
  • @afragen will experiment with changes to the WP Beta Tester plugin to see how feature flags or branches could be handled.

Post-meeting update

Next week’s meeting

  • Next meeting will take place on Monday, December 3rd, 2018 at 15:00 UTC in #core-php.
  • Agenda: WCUS in-person opportunities planning.
  • If you have suggestions about this but cannot make the meeting, please leave a comment on this post so that we can take them into account.

#core-php, #php, #summary

5.0 / Gutenberg Status Update – Dec 3

Current PRs for review:

Open issues in 5.0.0: 1 (=)
Open issues in 5.0.1: 33 (-1)
Open issues in 5.0.x (fast follow): 121 (-1)
5.0 status: RC2, released November 30.
Current plugin: 4.6, released November 30.
Next 5.0 milestone: TBC

In Trac:

  • Ready to commit:
    • N/A
  • Has patch, needs review:
    • N/A
  • Opened bugs:
    • N/A

#core-editor, #editor, #gutenberg

What’s New in Gutenberg? (30th November)

This should be the final “what’s new” installment for 5.0 — the 46th overall — accompanying the second release candidate which is also just released.

The Gutenberg plugin has also been updated to match core. The changelog here is a bit longer as it updates from 4.5.1:

4.6 ⌛️

#core-editor, #editor, #gutenberg

5.0 / Gutenberg Status Update – Nov 30

Current PRs for review:

Open issues in 5.0.0: 1 (-14)
Open issues in 5.0.1: 34 (-18)
Open issues in 5.0.x (fast follow): 122 (+17)
5.0 status: RC 1, released November 23.
Current plugin: 4.6, released today.
Next 5.0 milestone: RC 2, targeted for today.

In Trac:

#core-editor, #editor, #gutenberg

Dev Chat Summary: November 28th (5.0 Week 9)

This post summarizes the dev chat meeting from November 28th (agenda, Slack archive).

5.0 Planning and Updates

  • We started with a reminder that RC1 is out and moved quickly into a lively discussion about remaining blockers, timing, and general logistics. I’ve summarized them the best I could below.
    • There was a request for review on one outstanding item in the default theme.
    • There were requests for consideration on 11973, 6177, and 45407 in media. These tickets are largely about how to best handle responsive images, specifically some nuance around the sizes attribute.
    • There are no automated tests for expected vs actual behavior
    • This affects only new posts, or newly edited posts.
    • It’s related to full-width images in the new editor and further complicated by the lack of any way to filter for block alignment width.
    • There are concerns about high data usage and negative impacts on search engines (esp for mobile)
    • Q: If we fix this in 5.0.x, what happens to content published in between 5.0 and 5.0.x? Will content need to be updated to correct? It was suggested that fixing the insertion of full size images in content and incorrect width attributes would let us ship and then iterate. Insertion is already fixed, so it’s just the second one!
    • Q: What would need to be fixed or added to content to allow it to be fixed post-release? Ensure we have correct default height and width attributes on inserted img elements.
    • We started running low on time, but additional clarifications were offered in #core-media. Additional discussion can take place on
  • There were a number of questions that got interjected during the discussion, that I’ve collected the best I could below.
    • Are we proceeding with the January slip date as identified in the launch post?
      • A January date was seconded by the docs team and a collection of others.
      • Many mentioned concerns around predictability and user trust.
      • Data is still being gathered about how RC1 is being received, and once enough is available, a Core P2 post will be made to help people plan. RC2 is next on the horizon.
      • How much time will there be between the announcement of the release date and the actual release date?
    • Are there any dev notes that need to be posted prior to release? And if so, is there a list? And how can we help?
    • Should we prep a 4.9.9 in order to be prepared for PHP7.3 support?
    • There were multiple offers to help gather necessary data to determine how close we are to a release date.

Component and Focus Updates

  • The PHP team shared last week’s meeting recap which included some discussion of Tide, whether to expose PHP compat on plugins/themes, and best ways to identify those with compatibility concerns.
  • The JavaScript team shared this week’s meeting recap which included discussion of Contributor Day at WordCamp US, work on docs parsing for devhub, and ESLint configurations.
  • Design has a new research channel in the works. A lot of their initial work will be around user research for Phase 2+ of Gutenberg. Not much going on, but worth knowing about for sure. 🙂

Next meeting

The next meeting will take place on Wednesday, December 5 21:00 UTC in the #core Slack channel. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot make the meeting, please leave a comment on the upcoming agenda post so that we can take them into account.


5.0 / Gutenberg Status Update – Nov 29

Current PRs for review:

Open issues in 5.0.0: 15 (=)
Open issues in 5.0.1: 52 (-1)
Open issues in 5.0.x (fast follow): 105 (-1)
Current beta: RC 1, released November 23.
Current plugin: 4.5.1, released November 21.
Next release: RC 2, November 30.

In Trac:

#core-editor, #editor, #gutenberg

Gutenberg & 5.0 Listening Office Hours

A number of folks have requested an opportunity to connect more directly on where we’re at in the 5.0 process, or share their point of view on where we’re going. In the spirit of getting as many inputs as possible, I’ve opened up 24 office hours slots Thursday through Sunday. You can sign up using this link:

The sessions will be 15 minutes (even though it says 20 on the calendar) so I get a chance to connect with as many people as possible. I’m looking forward to it!

5.0 / Gutenberg Status Update – Nov 28

Current PRs for review: 7 in 4.6 Milestone (-5)
Open issues in 5.0.0: 15 (=)
Open issues in 5.0.1: 53 (+3)
Open issues in 5.0.x (fast follow): 106 (=)
Current beta: RC 1, released November 23.
Current plugin: 4.5.1, released November 21.
Next release: TBC.

In Trac:

#core-editor, #editor, #gutenberg

Dev Chat Agenda: November 28th (5.0 Week 9)

This is the agenda for the weekly devchat meeting on November 28th, 2018 at 21:00 UTC:

  • 5.0 Planning and Updates
    • A discussion about getting #11973 in 5.0 has been requested.
  • Updates from focus leads and component maintainers
  • General announcements

If you have anything to propose to add to the agenda or specific items related to those listed above, please leave a comment below. Either way, we look forward to seeing you at the devchat this week!

This meeting is held in the #core channel in the Making WordPress Slack.

#5-0, #agenda, #core, #dev-chat