XML Sitemaps Meeting: May 26th, 2020

A lot has been going on since our last blog post. Besides many improvements and fruitful discussions in the XML Sitemaps feature project, the proposed schedule for WordPress 5.5 has been published.

The first betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. is currently slated for July 7, which still gives us a bit of time to finish work on our project. We’re getting close to a state where we feel comfortable publishing a merge proposal for inclusion in WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. as part of the 5.5 releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software..

This post aims to give an overview of the things currently in progress, and the items that should be discussed in the upcoming meeting on 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/..

Updates

  • Custom elements in sitemap (#151)
    The pull request proposing a simple APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. still needs some documentation, but overall ready for review.
  • PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 Warning on PHP < 7.3 (#186)
    A pull request has been opened to fix this edge case. Ready for review.
  • Filters for individual sitemap entries (#191)
    Freshly proposed over the weekend, this PR makes it easier to modify sitemap data while having access to the necessary post/term/user objects for context. Ready for review.
  • FilterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. to modify WP_Query arguments (#183)
    Feedback from initial code review still needs to be incorporated.
  • Removing core_ prefixes from code (#182)
    Still some feedback that needs to be incorporated. Tests are currently not passing. Otherwise very close.
  • Custom elements in stylesheet (#152)
    PR #163 is still work in progress. The feeling last time was that it might be too complex for core, and perhaps better off as a 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.
    If the pre-existing stylesheet is deemed to not satisfy the needs, we could also omit the stylesheet completely if wanted.
  • Merge proposal post
    We started with an early draft for this, and will share the draft post with the broader group once we feel more comfortable with it.
  • Core patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing.
    Not yet in progress, as there are some bigger outstanding PRs needed for this. We’ll likely start with a first proof-of-concept PR that can then serve as the basis for discussion.

Agenda: May 26th

The next meeting will be held on Tuesday, May 26th at 16.00 CEST.

Items on the agenda so far:

  • Going through items from updates above
  • Open floor

Want to add anything to the above? Please leave a comment here or reach out on Slack.

This meeting is held in the #core-sitemaps channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#agenda, #feature-plugins, #feature-projects, #xml-sitemaps

Editor Chat Agenda 27 May, 2020

This is the agenda for the weekly coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor chat scheduled for Wednesday, 27 May, 2020, 10:00 AM EDT. This meeting is held in the #core-editor 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/. channel.

  • WordPress 5.5 Upcoming ReleaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software.Planning Roundup
  • GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ version 8.2 — RC 1 Available
  • Monthly Plan
  • Task Coordination
  • Open Floor

If you have anything to share for the Task Coordination section, please leave it as a comment on this post. If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#agenda#core-editor#editor-chat, #core-editor-agenda

CSS Chat Summary: 21st May…

CSSCSS Cascading Style Sheets. Chat Summary: 21st May 2020

Full meeting transcript on Slack: https://wordpress.slack.com/archives/CQ7V4966Q/p1590094908056800

I (@notlaura) facilitated the meeting.

CSS audit updates

@isabel_brison had a couple of questions, and we clarified some items mentioned in the report outline:

For “List of unique values for each of a list of properties, and number of occurrences:” we discussed that margins, padding, top/left/bottom/right, transforms, and typography related properties would be useful for standardizing our units of measurement. @ryelle‘s audit tool would certainly be useful for that.

The other question was to do with the item “Units: instances of px/em/rem/%age and count of use with properties”. We discussed that that should be limited to areas that affect responsive/zoom behavior, or properties where px unit are used but and probably shouldn’t be. Extending this to more than those cases might be beyond the scope of the audit and difficult to automate. Part of the original intent of that item was to identify “brute force layout”, but we discussed that basically the entire wp-adminadmin (and super admin) is brute force layout and auditing that would require manual inspection. Also, that is a subjective item and perhaps a conversation more appropriate for a CSS coding standards discussion after following the audit.

Color Scheming Update

@kburgoine has been doing lots of prep work and reading through historical tickets to get a good understanding of the problem with the current color schemes. She mentioned that the most pressing issue is not necessarily backwards compatibility, rather, the number of colors in use.

We discussed some more about design tokens, and I updated that I elaborated on my idea for the implementation in @ryelle‘s Gutenberg PR, and in a new comment on the “Iterating on Admin Color Schemes” ticketticket Created for both bug reports and feature development on the bug tracker..

I also mentioned some recent activity on the ticket for Dark Mode – which is potentially a conversation we can participate in since the intent behind re-vamping color schemes it to be able to support something like Dark Mode.

Open Floor

@peterwilsoncc jumped in at the end with a question about #46090 and including the X-UA-Compatible headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. for IE detection.

That was all for this week!

#core-css #summary

CSS Chat Agenda: 21st May…

CSSCSS Cascading Style Sheets. Chat Agenda: 21st May 2020

This is the agenda for the upcoming CSS meeting scheduled for Thursday, May 21, 2020, 5:00 PM EDT.

This meeting will be held in the #core-css channel in the 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/..

If there’s any topic you’d like to discuss, please leave a comment below!

  • CSS audit status update
  • Color Scheming Updates
  • Open floor

#agenda, #core-css

X-post: WCEU 2020 Online Contributor Day: All that team facilitators and experienced Contributors need to know

X-post from +make.wordpress.org/updates: WCEU 2020 Online Contributor Day: All that team facilitators and experienced Contributors need to know

Devchat meeting summary – May 20, 2020

@francina facilitated the chat on this agenda.
Meeting recap by @audrasjb and @marybaum.

Full meeting transcript on Slack

Announcements

Just a few hours before the chat, the hardworking team behind the plugins and themes auto-updates feature committed it to Core! Congrats to all!

Check out this related ticketticket Created for both bug reports and feature development on the bug tracker. that adds Help Tabs text to update-core, themes and plugins WP-Adminadmin (and super admin) screens: #50215

If you’d like to be part of the Full Site Editing outreach experiment, the sign-up deadline is now May 22. @chanthaboune noted that’s just to show interest, not a commitment yet.

Highlighted posts

Upcoming releases

WordPress 5.5

The next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. of WordPress is in active development (Alpha cycle).

@francina noted the team is not quite complete, but it’s confirmed that @matt will return as release leadRelease Lead The community member ultimately responsible for the Release.@davidbaumwald as co-lead in the role of Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. PM and @sergeybiryukov as Core tech lead. The 5.5 team will also mentor the 5.6 team.

WordPress 5.4.2

@audrasjb shared that there are 20 tickets in the milestone. Of those, 17 are closed as fixed.

@whyisjake leads this point releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality., and the group firmed plans for a release candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). on June 3 and a final releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. June 10.

Components check-in and status updates

@whyisjake was exuberant that the core team was able to merge the auto-updates code today. This is going to do a great deal to help people stay on top of updates for a safer WordPress ecosystem.

The merge is just the latest significant step toward the master plan for 2020. Lazy-loading of images merged a few weeks ago, and XML sitemaps is making great progress as well.

On the accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) side, @audrasjb shared that most of the accessibility team’s main projects for 5.5 are moving forward. Alternate views for posts, users, and comments lists should be ready for review soon.

@johnbillion wanted to note that weekly meetings for Multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site have restarted, on Tuesdays at 17:00 UTC in #core-multisite. Come join them!

In Sitesite (versus network, blog) Health, @clorith pointed out that the Theme Review Team has implemented requirements for PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 headers in themes. That move should push users in the right direction for updates.

As well, the Site Health component team has had discussions with hosting about bumping the version for Servehappy dashboard nags.

Open floor

@dlh wanted to highlight #48416. He recently encountered a use for it again. If you’re interested in the 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. component, please give it a look.

@sippis reminded everyone to register for WCEU 2020 Online Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/., which is Thursday, June 4, 2020 at 13:00 UTC. If you don’t register, you won’t get the emails you’ll need in advance, so don’t forget to register.

#5-4-2, #5-5, #dev-chat, #feature-autoupdates, #fse, #summary, #wceu, #wceu-2020

Core-Editor Dev Chat May 20, 2020

This post summarizes the latest weekly Editor meeting, held in the #core-editor Slack channel, on Wednesday, May 20, 2020, 10:00 AM EDT. These meetings coordinate collaboration in the development evolution of the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ project. You can find today’s agenda here. Facilitator: @pbrocks

Recap

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 5.5 — Checkout the Planning Roundup here

Gutenberg items to ship:

  • 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. UIUI User interface Redesign
  • Block Patterns
  • Hundreds of small improvements and  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. fixes

Gutenberg items we hope will ship but we’re not certain yet due to the deadlines:

  • Navigation screen and block
  • Widgets screen block-based
  • Global styles

Gutenberg version 8.1

Released last week containing:

  • Pattern searching
  • Copy block
  • Iterations on experimental screens
  • Embed transform to paragraph block.

Monthly Plan

What’s next in Gutenberg outlines the goals for May. There was no additional discussion around the current goals.

Task Coordination

@sageshilling

  • working with core-media data flow, design gallery, image block, gallery patterns…block_id

@mkaz

  • Diving into docs and addressing needs highlighted here Issue 22151

@karmatosed  

  • My main priority right now is navigation, navigation and oh yes navigation! I am working with some awesome peeps there.
  • I have a side order of triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. and ensuring any tickets I touched have feedback.

@andraganescu

  • As part of the ongoing work on the experimental navigation screen, I have added a _delete_ functionality for core data entities. If you are someone who uses entities this is interesting to get right so any feedback is welcome:

@youknowriad 

  • I’ve worked on a new CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress. command to automate performance tests across branches/versions
  • Fixing some bugs related to Color palettes
  • Looking at some UI parity work between edit-post and edit-sitesite (versus network, blog)

@q

  • I’m continuing to help improve the Cover block, mostly around customization and the UI/UXUX User experience of those controls.
    • Adding Padding Controls
    • Improving Color controls
    • Improving Background controls

@ajlende 

  • I’m working on getting the first pass / rough draft of rich image editing now that it’s unblocked again. Still need to know how best to limit for testing as experimental and where it should live. 

@michaelarestad

  • I’m working on template part flows, how they could fit with a site-wide column grid, and hopefully flows for setting up a new template.

@nrqsnchz

  • Merged the new Welcome Guide design, which includes support for prefers-reduced-motion
  • Worked on and merged a couple of block patterns
  • Fight Travis tests, as I usually do

@nosolosw

  • My main focus was the managed CSSCSS Cascading Style Sheets. PR. It’ll remain my main focus for next week.
  • APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. docs generation: audited & updated the list of packages (some are up for grabs, 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 if you’re interested in helping and don’t know how to do it) and documented the steps.
  • A bunch of other things: help with reviews, enable only stage-4 JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. syntax, etc.

@nfmohit 

  • I’m still working on a vertical style for the Buttons block.

@isabel_brison (tellthemachines)

  • working on a prototype for moving blocks between nesting levels with the keyboard and would love some feedback and testing on it! Also addresses the inability to move between nesting levels in navigation mode.

Open Floor

@zeb asks for review of the PRs listed in the agenda comments 

@annezazu The form for the Full Site Editing outreach project is open until May 22nd now: 

@mkaz

I’ve got one with regards to documentation I think we should revisit the idea of publishing off the releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. 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.), and instead be versioning at the unit level. For example, the core docs include the version and changelog for each function. 

@nickthegeek

Looking for comments/help with this Issue 22332 Add screen reader only text format

@noisysocks asked for comments and review on Navigation

`A few of us (@talldanwp @andraganescu @isabel_brison @zieladam @karmatosed) have been building out a rudimentary replacement for nav-menus.php which is based on the Navigation block UI. This new screen is in a semi functional state and you can see it by switching on the Navigation experiment in the latest Gutenberg.

A new [Feature] Navigation Screen label tracks issues to do with this new screen, and the Navigation in 5.5 project board tracks work that we think is important for this feature to land in WordPress 5.5. If you’re interested in helping out with this project, please feel free to pick up one of the tasks in the project board. You can also ping me (@noisysocks) if you have questions or need guidance! `

@zeb expressed concerns with the current navigation interface, specifically referencing wanting to see the following issues addressed;

  • Issue 22089 Navigator iterations: ellipsis and movers
  • Issue 22297 Block Navigator/Navigation: Drag & Drop

The in-depth conversation can be followed in Slack archives. With the team in agreement to continue the conversation in GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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/ with @karmatosed noting the navigation feature is still under an experimental flag and is in an iterative design process.

#meeting-notes #core-editor-summary

Join a discussion about Full Site Editing and the future of the Customizer

GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/’s Full Sitesite (versus network, blog) Editing project, or FSE, is progressing steadily, and while there’s much more to do, the core roadmap plans for FSE to be introduced into WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. later in 2020.

With Full Site Editing on the way, what does the future hold for the CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. and for the core Customize component?

At 16:00 UTC Thursday, May 28, we’ll start to tackle this broad question with an hour of discussion in the #core-customize 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/. channel that will include maintainers of the Customize component, members of the Gutenberg team, and you!

The primary focus of the discussion will be about contributing to the Customizer and to Gutenberg, guided by these questions:

  • First, a recap: What are the goals of the Full Site Editing project?
  • What can be done in the Customize component to help pave the way in core for Full Site Editing?
  • How can developers familiar with the Customizer best apply their experience to assist the Gutenberg team?
  • What’s the best use of time within Customize component for non-Gutenberg tasks? Is it worth patching bugs or pursuing enhancements?

Lastly, we’ll try to leave some time for an open floor.

If you have any questions about this discussion, or if you can’t attend but would like to add something to the agenda, please leave a comment. We’ll get to as many as we can.

I hope you can join us!

#customizer, #full-site-editing

Chat Summary: 14th May 2020…

Chat Summary: 14th May 2020

Full meeting transcript on Slack: https://wordpress.slack.com/archives/CQ7V4966Q/p1589490207487100

I (@notlaura) facilitated the meeting.

CSSCSS Cascading Style Sheets. audit updates

@isabel_brison ran a check for dead code using Purge CSS (and there’s not too much of it!) and added results to the Google Doc.

We discussed running checks on CSS in wp-includes as well as in wp-adminadmin (and super admin), and that seems like a good idea. @isabel_brison mentioned there is some inline CSS in PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 and JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. files – including some inline !importants 🥺. It seems like a useful data point for the audit to include a list of non-CSS files that contain CSS so we can flag those instances for improvement later, and I added that to the Google Doc.

Color Scheming Updates

I added a comment to the Iterating on Color Schemes Trac ticket with some details on how design systems handle theming with abstractly named tokens, and added a few comments to @ryelle‘s Gutenberg PR that contains a prototype for color schemes using PostCSS themes. We discussed the importance of determining an approach for browser support and getting some experiments started early.

wordpress/postcss-plugins-preset

@kburgoine asked about a default PostCSS setup for WordPress which led nicely into this agenda item. The coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor team requested feedback on this PR adding support for building CSS in the wp-scripts package.

WCEU Online Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/.

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 contributor day will be held online on June 4. It is an opportunity to contributors know about #core-css since it is a new group, and we could create a short list of tasks new contributors can help with on the CSS audit, or perhaps point them to the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ CSS 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.). I volunteered to find out some next steps for this.

That was all for this (last…) week!

#summary #core-css

Ways to keep up with Full Site Editing (FSE)

As work on Full Sitesite (versus network, blog) Editing continues, it’s important that communication around the project is made explicit so everyone can follow along appropriately. Each person will have their own unique needs in keeping up with a project of this scale so what follows is more of a catalogue of ways to keep up rather than a recommendation for how to do so. 

Yearly:

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/ Roadmap with Four Phases of GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ updated by @chanthaboune and/or @matt. This is the highest level overview of the changes coming to WordPress.

Quarterly: 

Quarterly Updates from Contribution Teams, coordinated by @chanthaboune. These updates give an overview on what each team is working on, struggling with, and how to get involved.

Monthly: 

“What’s Next In Gutenberg?” posts. These updates are wrangled by the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor team and highlight what’s planned for the coming month of work on Gutenberg. 

Block Based Themes Chat. These chats are currently wrangled by @kjellreigstad in the #themereview 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/. channel and are dedicated to sharing FSE changes that will specifically impact themes. Agendas and summaries are shared on the make/themes blog

Biweekly: 

“What’s New In Gutenberg?” posts. These updates are wrangled by the Core Editor team and focus on what’s been released in each biweekly Gutenberg releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software.. Currently, they tend to mimic a changelog.

Weekly: 

Core Editor chats. These chats are wrangled by volunteer members in the #core-editor Slack channel. Agendas and summaries are shared on the make/core blog. They focus on task coordination and relevant discussions around Gutenberg releases. There is an Open Floor period in each chat where people can suggest topics to discuss.

Weekly Gutenberg Design Updates wrangled by @mapk. These posts capture the big discussions and work being done in the design of Full Site Editing and Gutenberg in general.

Weekly Theme Related Gutenberg Updates (new initiative) wrangled by @kjellr. These posts are focused on themes, including everything from current discussions to recent changes, as well as helpful resources for theme authors. 

Daily:

Checking in on FSE PRs and FSE issues on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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/. This will give you a nearly real-time understanding of what’s being worked on by the developers and designers. 


Each of these are reliable ways of keeping up with the ongoing work on the new Full Site Editing feature coming to WordPress. A big thank you to everyone helping with these various initiatives!

Feedback welcome

What kinds of updates or communication might be missing? What might makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). these current updates and chats easier to follow? Share your ideas and feedback in the comments below! A next step to this work will be refining these communication pathways based on the feedback collected here and elsewhere.

Thank you to @itsjusteileen @andreamiddleton @paaljoachim @mapk for giving me feedback on this post.

#full-site-editing, #gutenberg