Editor chat Summary: 29 January, 2020

This post summarizes the weekly editor chat meeting agenda here. Held on Wednesday, 29th January 2020 held in Slack. Moderated by @youknowriad.

Weekly Priorities

@jorgefilipecosta
We are getting closer to the WordPress 5.4 beta releases.
Release dates:
11 February 2020 – Beta 1 – Deadline for new features (after this date, only bug fixes for regressions in the release).
18 February 2020 – Beta 2
25 February 2020 – Beta 3
3 March 2020 – RC1
10 March 2020- RC2
17 March 2020 – RC3
24 March 2020 – RC4
31 March 2020 – 5.4 Release day

The main priority is making sure we don’t send an unfixed critical issue on the first WordPress 5.4 beta. To track the issues we have a project board:
https://github.com/WordPress/gutenberg/projects/39
We should give particular care to issues raised after 18th of September (date of the last Gutenberg release that was included in WordPress 5.3).

@youknowriad
Gutenberg 7.4 on Feb 5 (RC on Feb 3)
(Exceptional release) Gutenberg 7.5 on Feb 12 (RC on Feb 10)
Both will be included in WP 5.4.
What do you think about the current state of things?

@jorgefilipecosta
Currently it seems we are on track. Some new features like the custom gradient picker may need some focus to be polished and could benefit from tests/feedback. https://github.com/WordPress/gutenberg/issues/16662 and https://github.com/WordPress/gutenberg/pull/19582
I would also like to request everyone that implemented experimental API’s to think if they could be made stable before WordPress 5.4. It would be good to reduce experimental API’s as much as possible.

I will soon add a comment on https://github.com/WordPress/gutenberg/issues/17743 pinging the authors of API’s I think could be stabilised.

@gziolo
We are discussing with @mcsf block variations. It is nice to have for 5.4.
I believe that Social Icons is still not exposed for WordPress core so we only would include this new API paired with Social Icons block.

I also don’t feel that we can make the accessible toolbar for 5.4 but maybe it’s better to have it enabled together with the block toolbar redesign. In the gist, it’s change in the tabbing behavior where every toolbar is only one tab stop and you can navigate between items with arrow keys, home, end, etc. Super important from accessibility standpoint.

@mkaz
We started a draft PR iterating on Social Icons adjust implementation to allow for no-duplication of assets and making extendable, but there are some trade-offs being considered:
https://github.com/WordPress/gutenberg/pull/19888

Task Coordination

@karmatosed
I’ve had my head deep in Figma working on global styles. Focusing on the minimum version first. I also have been diving into controls. I also have been working on some iterations to color picker. Along the side there is as always a constant flow of triage.

@youknowriad
Still working on the Dashicons and gathering all icons under the same package. Wrote some blog posts about Gutenberg Extensibility APIs and Modularity. https://make.wordpress.org/core/2020/01/23/controlling-the-block-editor/
Reviewing, triaging as I can.
I’m hoping to continue on the icons and to circle back to the keyboards shortcuts package work as there’s still some improvements to make to allow third-party shortcuts to show up in the modal.

@jorgefilipecosta
Last week:
I started the work on the global styles, proposed the resolver system.
Iterated on the angle picker and merged it.
Triaged issues relevant for WordPress 5.4 & submitted bug fixes.
Next week:
Audit experimental APIs. Stabilize some API’s I proposed.
Audit dev notes and create an issue summarizing all the dev notes needed.
Continue the work on global styles.
Continue the work on the custom gradient picker.
Continue the WordPress 5.4 preparations by triaging and fixing issues.
PR reviews.

@andraganescu
I am working on adding features to the author block.
https://github.com/WordPress/gutenberg/issues/19696 and
https://github.com/WordPress/gutenberg/pull/19894

@mkaz
We have some cool image editing tools we’d love to get in at some point, appreciate some feedback and guidance. Issue and details added here, plugin available for testing: https://github.com/WordPress/gutenberg/issues/13748#issuecomment-574903126

@aduth
Been working a fair bit around the LinkControl component and related implementations (Popovers, etc). I expect to be continuing this in the next week.
Discussing user preferences persistence using meta. There’s been a lively discussion in https://github.com/WordPress/gutenberg/pull/19177

@nosolosw
I’ve also been diving into GlobalStyles (master issue at https://github.com/WordPress/gutenberg/issues/19611) pairing with Jorge and Q. My focus at the moment is accommodating the prototypes shared in the issue into the proper data structures, client side.
Need a tech review at https://github.com/WordPress/gutenberg/pull/14930

@gziolo
Merged create-block package for block scaffolding, still not published to npm until next Wednesday.
Landed Variations API integration with the inserter.
Some more work to improve the workflow for syncing Gutenberg and WP core.
I plan more work on the Variations API and smaller accessibility improvements I started earlier.

@mcsf
I have been focusing on the Block Patterns Variations API with @gziolo and exploring applying that to Social Links: https://github.com/WordPress/gutenberg/pull/19887
Discussing what @epiqueras initially proposed of server-side rendering support for parent attributes context:
https://github.com/WordPress/gutenberg/issues/19685
Improved the way RichText blocks do or don’t automatically transform content into another block: https://github.com/WordPress/gutenberg/pull/19727

@itsjonq
Continue with Global Styles work. Pairing with @karmatosed, @nosolosw, and @jorgefilipecosta for various parts. Also diving deeper into the technical aspects/flow and planning.
https://github.com/WordPress/gutenberg/issues/19611
Updates to the RangeControl component in wordpress/components at https://github.com/WordPress/gutenberg/pull/19916

@richtabor
Background color support for Columns block has landed: https://github.com/WordPress/gutenberg/pull/17813
Tidied up labels/titles to use sentence case formatting: https://github.com/WordPress/gutenberg/pull/19903 and https://github.com/WordPress/gutenberg/pull/19901

Open Floor

@SvenWeber asked about this issue: https://github.com/WordPress/gutenberg/issues/19898
@aduth added a comment to the issue.

@Munirkamal asked:
How can I replicate the “Add to Reusable Blocks” functionality on my custom Gutenberg Block which I need to allow users to save to a custom post type. So users will be able to save the block to a defined post type like core add to reusable functionality.
@epiqueras
I think he means saving the blocks to a different CPT.
https://github.com/WordPress/gutenberg/blob/5cb272724b30877217c9ec2d6ee0f4724deb4b51/packages/block-library/src/template-part/edit/index.js#L39
https://github.com/WordPress/gutenberg/blob/5cb272724b30877217c9ec2d6ee0f4724deb4b51/packages/block-library/src/template-part/edit/inner-blocks.js#L8-L21
@youknowriad
You just need to save a wp.blocks.serialize( block ) and save as “content” of your CPT.

@kjellr
A brand new recurring meeting in the #themereview channel. It’s dedicated to crafting the future of block-based themes in concert with the full-site editing work happening in Gutenberg. It will be held bi-weekly on Wednesdays @ 16:00 UTC, beginning Feb 5th. Look for an official post about the meeting on make.wordpress.org/themes later today.

Core editor chat summary 4th December, 2019

This post summarizes the weekly editor chat meeting agenda here. Held on Wednesday, 4th December 2019 held in Slack. Moderated by @ellatrix.

Full Site Editing and themes

@ellatrix
The idea here is to recap what’s being worked on, what has been discussed in #themereview yesterday’s meeting and provide some space for feedback and discussions about the next steps.
Must Read:
– Summary for yesterday’s #themereview meeting
https://make.wordpress.org/themes/2019/12/04/questions-about-the-future-of-themes/
– Documentation for the current state of Block-based themes
https://github.com/WordPress/gutenberg/pull/18890

@youknowriad
The main takeaways/action items for me are:
– Let’s have theme authors experiment with these in Github/personal themes and provide feedback: Gather a list of Missing blocks?
– Potentially help build a demo theme in Gutenberg in this folder https://github.com/WordPress/gutenberg/blob/master/lib/demo-block-templates/index.html
– From the editor side, continue on the current PRs/work https://github.com/WordPress/gutenberg/labels/%5BFeature%5D%20Full%20Site%20Editing

@williampatton
Sounds good to me, in addition we will also be doing more to get stuck in and help you all out with comments, PRs and testing as we all make time for it in the coming weeks.

@noisysocks
If I’m a theme author and read these incredibly helpful links and have some questions or comments, where should I put them?

@youknowriad
I think at the moment (only during experiment phase), it should be fine to ask here and raise Github issues for bugs. We should also take these as opportunities to document things as we move forward from both themers and devs.

Weekly Priorities

@youknowriad
I’d like to share the new priorities post for December in case you missed it https://make.wordpress.org/core/2019/12/03/whats-next-in-gutenberg-december/
An emphasize on Block content areas / Full site editing and also a push for Block Patterns APIs and usage across blocks and inserter in addition to a few tightening up items.

Task Coordination

@aduth
I’ve been focusing more on framework-y stuff:
– Get types checking in place https://github.com/WordPress/gutenberg/issues/18838
– A never-ending crusade to stabilize Travis build
Hoping in the next week to revisit some feature work:
– Better _fields handling in wordpress/apiFetch and/or wordpress/data
– Revisit spoken messages in Notice pull request
– Also been fixing up a few theme interoperability issues, notably around background colors for custom editor styles:
https://github.com/WordPress/gutenberg/pull/18732
https://github.com/WordPress/gutenberg/pull/18871
https://github.com/WordPress/gutenberg/pull/18873

@noisysocks
I’m somewhat looking at deprecating the wordpress/nux package but mostly reviewing PRs this week.

@ellatrix
I’ve been working on “Lighter block DOM: detached controls in popovers”, improvements on Popover, multi block selection, and paste on multi block selection.

@get_dave
I’ve been working on…
…a PR to allow parent blocks to capture the Block toolbars of all child blocks which is just waiting on a thumbs up from @jorgefilipecosta:
https://github.com/WordPress/gutenberg/pull/18440
…adding justification tools to the Navigation Block:
https://github.com/WordPress/gutenberg/pull/18909

@jorgefilipecosta
Past week:
– Reviewed some media-related PR’s, namely the refactor to the gallery, to increase reusability with the native mobile APP.
– Helped the enhancements to useColors and merged the PR that uses the hook in the paragraph.
– Finish the remove editor module usages in block-editor by applying changes to the reusable blocks, rich-text, and native inserter. Some PR’s are waiting for a review.
– Updated the release tool to move readme and changelog files to the Github repository.
– Submitted several bug fixes.
– Continued the interactions/enhancements on the PR’s I have open e.g.: custom gradients.
Next week:
– Increase my involvement with the FSE work (by reviewing PR’s and working on a subtask — Suggestions for a possible subtask are welcome 🙂 ).
– Continue giving my support to some media-related PR’s by reviewing and testing them, and maybe submit follow up enhancements.
– Rebase Update the buttons block PR and try to unblock the PR.
– Address reviews Add a mechanism to set a width on withViewportMatch https://github.com/WordPress/gutenberg/pull/17085.
– Fix some widget related issues.

@youknowriad
I’ve mostly trying to make sure everyone is not blocked and also worked on some PR’s related to the block toolbar/UI (fixed toolbar, select/edit modes…) and some code quality refactorings.

@richtabor
I have a PR for adding background color support to the Columns block:
https://github.com/WordPress/gutenberg/pull/17813

@welcher
I have a small docs PR that explains how to work with the changes to serverSideRender location: https://github.com/WordPress/gutenberg/pull/18722

@gziolo
Last week:
– Worked on fixes for regression introduced in the block toolbar.
– Refactoring towards using the new accessible version of Toolbar component.
– Core patch to simplify the process of updating Gutenberg packages after every plugin release.
Next week:
– Resume work on Patterns API once we decide which blocks should be integrated (Table?, Cover?).
– Resume work on block.json transformation on the client side to allow automatic handling of translations.

Open Floor

@gziolo
Resume work on Patterns API once we decide which blocks should be integrated (Table?, Cover?)
We have Columns block integrate, we use some sort of setup step for Table block, should we integrate it with Patterns API as well?
The challenge is that it needs to allow the custom creator as well.

We tried Media & Text but we abandoned this idea
https://github.com/WordPress/gutenberg/issues/16283#issuecomment-508132004
Information here: https://github.com/WordPress/gutenberg/pull/18343

There was additional conversations about patterns and transforms during the open floor: https://wordpress.slack.com/archives/C02QB2JS7/p1575469981089100

PHP Meeting Recap – November 12th

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 adapted the README.md in the Servehappy repository so that it just links to the Feature Project page, to avoid requiring both to stay in sync.
  • Adding support for PHP version requirements to themes was discussed (Meta Trac #3718). The current state of the requirement for themes to have a readme.txt file does not seem to be clearly defined, as the only source of truth is the combination of an old blog post from 2015 and its collection of comments.
  • @afragen proposed to split the individual next actions for theme support into separate tickets, just as we did with plugins.
  • We also initiated contact with one of the team leads of the #themereview team (@williampatton) to discuss the current state of the theme’s readme.txt requirements.
  • @schlessera noted that while it seems we need to help move some unrelated stuff forward to get around our own blockers, we should be careful to avoid taking on too much responsibility and wasting our time on unrelated efforts.

Next week’s meeting

  • Next meeting will take place on Monday, November 19th, 2018 at 15:00 UTC in #core-php.
  • Agenda: Open floor.
  • 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, #servehappy, #summary

Dev Chat Summary: September 12, 2018 (4.9.9 week 5)

This post summarizes the weekly dev chat meeting held Wednesday, September 12, 2018 at 20:00 UTC. Agenda | Slack archive


4.9.9 Planning

We have a Road Map and she is gorgeous. Thank you @antpb and @schlessera for putting it together. Here’s a summary:

Suggested Timeline

We will reassess these dates after the three-week mark:

  • Beta : Monday October 22, 2018
  • Release Candidate : Monday October 29, 2018
  • Release Date : Monday November 5, 2018

Key Focuses

If you’re interested in helping out with these topics, hit up these Slack channels:

*Not real but should be.

Bug Scrubs

  • The plan is to run them weekly in the #core Slack channel across multiple timezones. Schedule 👏 Coming 👏 Soon 👏

Focus Lead and Component Maintainer Updates

Notes and Summary Posts

Additional Updates/Requests

  • From PHP Servehappy: More testers are needed for the WSOD protection on real-life, complex sites to reveal edge cases. A “complex site” is basically any site running locally with random plugins and random code.

If you’re thinking about get all up in these Focus and Component Maintainer teams, try attending a chat. Here’s the comprehensive list.


Open Floor

Tickets

Anyone can submit a ticket for the Open Floor. Send your submission to @jeffpaul or moi (@whitneyyadrich), or comment on the agenda for that week’s chat.

  • #12563: New action on body open – Submitted via @welcher. Will be discussed in the #themereview meeting.
  • #32326: Improve Support for Structured Data – This one pairs nicely with the ticket above, so the conversation should be happening in the #themereview room and scheduled chat.
  • #25280: wp_localize_script unexpectedly converts numbers to strings – Submitted via @adamsilverstein and Ivan Kristianto. Lots of words about code were had in the chat, and then the conversation was moved to the ticket itself.

General Announcements

Dev Chat Schedule

@psykro published his proposal for a second <dev chat> and it’s open for your comments. I’m sure we’ll touch on this during tomorrow’s dev chat, too. 

As always, anyone is welcome to join <dev chat> every Wednesday at 20:00 UTC. As I said in the chat, to sorta quote the late, great Notorious B.I.G.

I’m goin’ go call my WP crew
You go call your WP crew
We can rendezvous in <dev chat> tomorrow around two (or Wednesday at 20:00 UTC)

#summary, #4-9-9, #core, #dev-chat

Dev Chat Summary: October 12 (4.7 week 8)

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

Reminders

Feature Proposals for 4.7

  • REST API: Content API (@kadamwhite)
    • REST API Team Update
    • Content API endpoints have been stable for some time and now have the missing functionality established at the start of this development cycle
    • We pitched merging in the OAuth 1 server alongside those content endpoints, to simplify the process of authenticating from remote applications
    • The auth method in core right now is cookie/nonce-based, so it’s available to any code running within the same domain as the main WordPress install and leverages the existing login cookie
    • plugins and themes that utilize JS to enhance the editing experience within their admin UI have full read/write access, restricted to the capabilities of the authenticated user
    • External applications, e.g. a mobile app, desktop app or external server, would have read-only access
    • readers, aggregators, etc are possible without authentication, and more complex read-write apps can be written by installing one of the available authentication plugins, of which OAuth is but one
    • Reference for options and when/how to use
    • 90 contributors for the rest-api plugin
    • automated test coverage currently at 90.44%
    • 37 more open tickets
    • weekly meeting on Monday at 1400UTC in #core-restapi
  • Discovering and installing themes in the customizer (@celloexpressions)
    • Related Make/Design and Make/Flow posts, but best to post all feedback to the Make/Core feature proposal
    • Working through the accessibility feedback, but it’s a bit unclear what’s specific to this feature versus the customizer in general, and which issues are also present in the admin theme installer
    • Haven’t heard anything from polyglots, security (unlikely to have any issues), or docs
    • There is one known i18n concern where we’ll need a compromise until we have JS i18n in core
    • @celloexpressions to do a final iteration to pick up any remaining feedback on Thursday, then pass to @westonruter for the code review process
  • Custom CSS with live previews (@celloexpressions)
    • seems to have decent support as a feature, with the biggest question in the comments being how to store and output the CSS
    • CSS is output from the db via a style tag, use of `style` tag is key for targeting for `postMessage` live preview
    • Post-based storage allows for revisions built in (ensuring that there are hooks for a plugin that wants to write a file would alleviate many concerns)
    • CSS is theme-specific in the proposal for this, with a post object for each theme that has CSS
    • Scheduling a meeting to go through these concerns and make a decision, coordination to occur in #core-customize
  • Customize Changesets (née Transactions) (@westonruter)
    • Technical Post (audience is developers who have extended the customizer significantly, as there may be impacts to any heavy customizer integrations since changesets touches some very low-level stuff in the customizer)
    • Users will be able to bookmark a customizer session since the changeset UUID will be part of the URL
    • Theme switches will no longer result in changes being lost (no more AYS dialog)
    • a few other open questions and issues that have been noted

Components

#4-7, #core, #dev-chat, #summary