Editor Chat Summary: June 1st, 2022

This post summarizes the weekly editor chat meeting (agenda here) held on 2022-06-01 14:00 UTC in Slack. Moderated by @andraganescu.

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/ 13.4 RCrelease 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).

The 13.4 RC version of Gutenberg was released on June 1st by @priethor. Check it out here.

WordPress 6.1

It’s time to focus on the next minor 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. of WordPress, version 6.0.1. It already has a project 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/ concerning fixes and backports from Gutenberg.

Key project updates

Task Coordination

@andraganescu

@hellofromtonya

  • I’m working on wrangling web font needs to support 6.1 tasks. First step is to create a single epic issue that shares the vision (from Matías), a list of open work, prioritizations, and status.
    • Goal is to have this epic ticketticket Created for both bug reports and feature development on the bug tracker. available this week

Open Floor

Announcements, questions and discussions.

@mdxfr

Asked about support for current-menu-ancestor in the navigation 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..

@mdxfr

Asked about how to quicken the landing of gutenberg fixes/improvements (already made within 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) into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. through minor releases?

  • @andraganescu suggested  labeling with Backport to WP Minor Release merged PR’s that should sooner into core and monitoring the WordPress 6.0.1 project on GitHub
  • @hellofromtonya suggested to bring this topic to the weekly Core DevChat for broader discussion on how to do faster, more frequent minor releases to ship fixes faster.

#core-editor, #core-editor-summary, #gutenberg, #meeting-notes, #summary

High Level Feedback from the FSE Outreach Program (May 2022)

Overview

This post summarizes the top pieces of feedback of the current experience to help inform the next steps and as a follow-up to various previous editions. Compared to the previous related posts (March 2021, July 2021), this one seeks to focus on more specific and common items different types of folks might try to accomplish rather than more general themes that continue to come up. This is to help provide more specifics to designers and developers working on these various related features. The aim is that by examining FSE from the vantage point of common flows, contributors can improve specific features in a way that brings everything together intuitively. For example, this doesn’t go into depth around problems that come up when using FSE at scale, like needing to have more ability to sort templates

Keep in mind that this post is simply a snapshot in time and is inherently going to leave out aspects of the experience that haven’t been the subject of calls for testing. It’s also not going to go into great detail about all of the hard work already done to address these items, whether through PRs or sharing designs that offer solutions.

If you want a more in-depth look at feedback across the testing calls and a full summary of all issues rather than a sampling, please review the summary posts. If you want to help give feedback, join the calls for testing or test whenever you’d like!

Provide a better setup state when creating a new template or template part

When creating a new template or template part, the initial options offered to users are quite limited and, after creation, it’s not clear how to fully apply what was just created across the site. Tied to this, the difference between the Template editor in the Site Editor vs the Post Editor continues to be jarring with folks not clear around when and how best to use each at a glance. 

  • Provide better initial default options after creating a template or template part. This could be prioritizing patterns or starting with the closest template in the template hierarchy. 
  • Show which templates use a given template part.
  • When replacing the current template part,  make it clearer which one is currently in use
  • Unless you add a container 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. when creating a new template, any text runs to the edges. Below is a quick video example:

The most immediate issue when creating a new author template is that it was devoid of default blocks. Where was the—at minimum—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. and footer? The empty template would make sense if I was building something from scratch. However, this is not a from-scratch project. It was built from a theme with existing archive.htmlHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. and index.html files, ancestors in the template hierarchy. Since the author template is merely a more specific version of the archive template, it should be a copy of its “parent” in the hierarchy. Users will most likely want to make modifications rather than start from scratch. Using an ancestor template as a base means that they are less likely to unnecessarily deviate from the existing layout, especially with more complex designs.

@greenshady in this WP Tavern article.

Unify the Template Editor in the Post Editor with the Site Editor

For example, a template for posts/pages can only be added via the Template Editor in the Post Editor rather than in the Site Editor. This difference in functionality isn’t made clear at any point though, leading some to not be aware of the Template Editor in the Post Editor at all. Below is a short video discussing some of the differences:

The slightly different variations of the template editing screen were just too confusing for me. As someone who has been trying to work in the FSE for a few months now, I was completely thrown off by the slightly different screen you got when you launch the template editor directly from a post vs the template editor you get when you go to edit site, and then select a template to edit.

@​​beckej in this comment.

Improve the process of applying and viewing a template in action

After creating a new template that you might want to use for a page/post, it’s not clear that you have to assign it to that post/page. To ease this workflow, after a user creates a new template, they could be prompted to apply it to all child pages of a parent page. The same is true for creating new template parts and needing to actually apply them to each template you might want to use it in. 

On a related note, after someone creates an author template or date template, they would have to know the relative link for their site to see the template in action. It would be great to connect the dots a bit more in the interface so that folks can see their changes after a new template has been created. This came up during a recent call for testing around creating an author template with folks not knowing how to see the template without being linked to an example.

I really do not know which template affects which pages/posts. So I assume that a Page template affects all the pages. 

@paaljoachim in this comment.

Make it clearer that editing a template part will update everywhere it’s used

Currently, it’s very easy to edit a template part without realizing any changes you make can potentially have a site-wide impact. This touches on a few issues: 

Tied into this is the general experience of when and why to use template part focus mode, since the advantages of doing so aren’t always clear and the general mode matches the appearance of the Template Editor in the Post Editor (dark background, back button, etc). 

I went down a weird rabbit hole where I couldn’t figure out why we had the header block and the header template parts. I mean, what if I wanted to have two different headers with wildly different information in them? Whenever I changed the main header block (anything living inside it), it changed it in all the header template parts, and I found that very confusing and frustrating. I ended up removing the header block inside the header templates and keeping things just in groups. That made way more sense to me.

@aurooba in this comment.

Make multi-entity saving more user-friendly

Building off of a need to have more granular information in multi-entity saving for Styles, the following are repeat items that have continued to come up: 

Improve theme block placeholders

Placeholders need to be greatly improved as folks are accidentally deleting theme blocks like the Post Content block not realizing that it’s what will display their actual content in the template itself. The more robust the placeholders can be, the more visual clarity there can be between editing a template vs post/page. Keep in mind that when user content is displayed but not editable, there needs to be a clear way for folks to understand why they can’t edit their content directly. 

I found it a bit strange adding a featured imageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. block and a duotone 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. without seeing what the result would look like.  

@paaljoachim in this comment.

Ease the process of editing a template for currently viewed page/post

When you are viewing a page, it’s not always clear what template is currently in use, and it  takes numerous steps just to get to a specific template in use outside of your homepage (wp-adminadmin (and super admin) > Appearance > Editor > W Menu > Templates > Select correct template). There are a few issues related to this to explore, including:

Add ability to bulk add items to Navigation Block, including pages, categories, etc.

This was previously possible with the prior Appearance > Menus screen but a known pain point with the current Navigation Block experience. In time, this should also include expanding beyond just posts/pages and being able to add additional items like categories in bulk

Open up more ways to set the site icon

Without using the Site Icon block, there’s not a current way to set this for your site. It’s also not clear that one has to add that block and that, after adding it, you’ll see an option to set your site icon. 

Provide consistent dimension controls across blocks 

In nearly every call for testing, folks are left wondering why certain controls exist in some blocks and not in others. This current experience of dimension controls needs to be standardized and expanded appropriately

The different controls for different blocks makes it really hard to make something that is consistent and nice. I decided it would be cool to make the user pictures a little bit bigger, like that might make the comments more inviting. Since I made the commenters pictures so big, I said, let’s add in a Post Author block so that the post author’s picture will be shown too! Wait, the AvatarAvatar An avatar is an image or illustration that specifically refers to a character that represents an online user. It’s usually a square box that appears next to the user’s name. block in the Comments Query loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. and the Post Author have completely different control? I can make the avatar any size, but the post author I have a dropdown with 3 choices? I can but a border radius on the avatar block, but not the post author block? If it’s a picture, I should have all the same tools available to me as any other block that uses a picture.

@beckej in this comment.

Offer more ways to see how changing Styles will impact the entire site 

The Styles system is powerful and vast to the point that the current experience makes it difficult to know just how much is being adjusted with a few clicks: 

Improve the experience of changing font sizes using the default options

Whether you’re selecting from the default options or trying to set a custom size, the UXUX User experience is fairly quirky. Finding the custom size option is somewhat cumbersome and, if you select one of the default sizes but want to switch back, you have to “reset” the font selection from the ellipsis menu. The presentation of the font sizes isn’t easily known either, with “t-shirt” sizes currently being considered. Regardless, this is an extremely basic action to take that now takes numerous steps to complete as the video below demonstrates:

Ease switching to a block theme/between block themes

Switching to or between a block theme should feel seamless and there are a few issues to help get the experience where it needs to be:

Simplify various ways of creating common layouts

This covers a large number of use cases, from using the same width for the rest of your content in a new template to wanting to have a site logo next to a site title. Beyond relying on patterns to set a header or footer layout, it’s incredibly difficult to create your own as you often need to use a group/row/stack block first and foremost. From there, getting the spacing right is incredibly difficult. This is true of individual experiences like with the Navigation Block and of trying to combine multiple blocks into one layout:

Users who want to even slightly change the spacing and positioning of content have to have deep knowledge of container blocks, design tools (often locked away in ellipsis menus), and the spacer block. While the spacer block is the most user-friendly option for controlling spacing, the problems below remain: 

  • It’s not clear when to use spacer blocks. 
  • Spacer blocks often aren’t robust enough. 
  • Design tools are hidden in the ellipsis menu. 
  • It’s not clear if one needs to use container blocks to have more control over layout/spacing. 

Still trying to get “edge space” – ie margin from edge to orange borders I tried toggling on the “inherit default layout” This didnt make any different to the margin. It just changed the padding. I also added a zero to the block spacing field. Nothing changed. I tried changing the layout toggle to 80 % wide. This changed the internal padding of the block and didnt move the block away from the edges…Why are some settings in the block toolbar and some in the inspector? Why aren’t the same settings (where appropriate) in all similar blocks – ie padding, margins, width available in both groups, and columns?

@alixnotes in this comment.

Thank you to @priethor for helping to review this post at various stages.

#core-editor, #fse-outreach-program, #full-site-editing, #gutenberg

Editor chat agenda: 1st June 2022

Facilitator and notetaker: @andraganescu.

This is the agenda for the weekly editor chat scheduled for 2022-06-01 14:00 UTC.

This meeting is held in the #core-editor 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 you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion:

  • If you have an update for the main site editing projects, please feel free to share as a comment or come prepared for the meeting itself.
  • 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, #core-editor-agenda, #meeting

Editor Chat Summary: May 25, 2022

This post summarizes the weekly editor chat meeting (agenda here) held on 2022-05-25 14:00 UTC in Slack. Moderated by @zieladam.

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/ 13.3

The 13.3 version was released on May 25th by @welcher. Find out more in the What’s New in Gutenberg 13.3.0 post.

WordPress 6.0

The long-awaited WordPress 6.0 stable version has been released this Tuesday!

The highlights include:

  • Enhanced Writing Experience
  • Style Switching
  • More Template Choices
  • Integrated Patterns
  • Additional Design Tools

Key project updates

Task Coordination

@amustaque97

@mamaduka

  • I’m mostly doing PR reviews last couple of days

@isabel_brison

  • I’ll mostly be migrating flaky e2e tests to Playwright this week

@zieladam

@welcher

@ntsekouras

  • I’ve started the work for expanding the templates in site editor. The first part will be for custom post types and their archive pages.

Open Floor

Announcements, questions and discussions.

@markhowellsmead

Asked about the motivation behind moving coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSSCSS Cascading Style Sheets. inline.

This change has directly lead to many specificity problems, not least that it’s very difficult (and somtimes impossible) to override inline styles using rules in external CSS files.
Ref. https://github.com/WordPress/gutenberg/issues/38719
Ref: https://github.com/WordPress/gutenberg/issues/40159

Mark and other theme developers have seen feedback that hints how editor devs (in some cases) don’t want to “allow” others to modify layout or logical decisions through the use of code in themes or plugins. By blocking access to allow themes and plugins to override what should be simple core CSS rules, we’re being forced towards a complete deactivation of core CSS in some projects.  It’s admirable to release devs from the burden of basic CSS by way of the Style Engine, but there are limitless requirements for custom-built themes which neither belong in core, nor which can be solved by a generic 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..

@amustaque97

Asked whether https://github.com/WordPress/gutenberg/issues/40809 is a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. or enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature.. @zieladam thought it was a bug since it reports a mismatch between the editor and the website.

@welcher

Asked whether anyone is aware of any commits that need to be cherry-picked.

@manfcarlo

Reported that https://github.com/WordPress/gutenberg/issues/29484 is currently closed but it needs to be re-opened. The issue has been reopened since then.

@greenshady

Requested feedback on https://github.com/WordPress/gutenberg/issues/41324. The vertical alignment options for Row and Buttons (flex) blocks is always centered on the front end, even when choosing something like top alignment. This seems to be an issue with WordPress 6.0 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". but not with Gutenberg 13.2.2 active.

@bph

Proposed a theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. ‘allow-list’ to limit the number of patterns offered to the users through the patterns directory.

To get more details go directly to the Open Floor discussions in the Core Editor 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.

#core-editor, #core-editor-summary, #gutenberg, #meeting-notes, #summary

Editor chat agenda: 25th May 2022

Facilitator and notetaker: @zieladam.

This is the agenda for the weekly editor chat scheduled for 2022-05-25 14:00 UTC.

This meeting is held in the #core-editor 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 you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion:

  • If you have an update for the main site editing projects, please feel free to share as a comment or come prepared for the meeting itself.
  • 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, #core-editor-agenda, #meeting

Core Editor Improvement: Creating & containing containers

These “CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor Improvement…” posts (labeled with the #core-editor-improvement 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.)) are a series dedicated to highlighting various new features, improvements, and more from Core Editor related projects. 

In the last few versions 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/ set to be included in WordPress 6.0, a collection of changes were made to simplify the discovery, use, and optionality of container blocks. When combined with the new 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. locking UIUI User interface, you can create layouts of your choosing and lock when you’re ready. 

Improved discoverability

When you select multiple blocks, the toolbar shows each variation of the Group block so you can quickly choose between the different variations while directly creating content. 

Of note, you can always ungroup blocks after you’ve done this if you’d like by using the ellipsis menu in the block toolbar and selecting Ungroup. 

More variations

Blocks are now easily grouped into either a Stack layout (vertical) or a Row layout (horizontal) with a single click. These flex-based containers allow for responsiveness at default for your content, especially when combined. From the 6.0 dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. on Block markup updates for image, quote, list and group blocks:

It’s a flex container, meaning it has access to content justifications and block spacing. If combined with the Row block and its ability to optionally wrap onto new lines, it can enable basic responsive behaviors, such as two columns that stack to a single column on smaller displays.

You can switch between them in the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. settings too after your initial selection to get a feel for what you want. The video below brings the entire experience together:

More design options

To customize things more, you can play with gap support, margin, typography options, and more. For margin and padding, thanks to Gutenberg 13.2 (not coming to 6.0), you can more readily visualize your changes too. Here’s a video from the release notes:

Lock when done 

When you have things exactly as you want them, you can lock whatever pieces you’d like of your creation to prevent removal or movement from the overall container blocks discussed above to individual blocks within. This is a great way to preserve your layout. Here’s a quick visual from a previous release post


If you’ve explored these new options in the release cycle for 6.0 or via the Gutenberg 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, feel free to share your creations below in the comments or even in the Pattern Directory. If you haven’t just yet, get excited to explore for WordPress 6.0.

#core-editor, #core-editor-improvement, #gutenberg

Editor Chat Summary: 18th May 2022

This post summarises the weekly editor chat meeting (agenda here) held on 2022-05-18 14:00 UTC in Slack. Moderated by @get_dave.

Status Updates

Task Coordination

The following items were shared by folks to update us on what work is in progress or where help is needed:

@noisysocks:

@manfcarlo (not present – shared by @paaljoachim):

  • I want to draw attention to Page Break block ( core/nextpage ) not working as expected.
  • It was patched in January but there are some problems with the 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. that will need to be re-patched.
  • Details are in the latest comment on the issue.

@mamaduka – I got sidetracked with shiny new issues, but I plan to continue working on the 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. Locking feature.

@vcanales:

  • I’ve created a draft PR with a small proof of concept on creating random color palettes in the 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. Styles panel, with colors that work well together in terms of legibility.
  • It’s very early on, but I’ll be updating that PR with whatever issues I can surface. I’ll also come back every week to ask for input

@get_dave:

@tomasz:

  • I wanted to call for a review of Search Block extensibility: search query vars (now merged).
  • I would really appreciate a review of the proposed implementation as this would enable our team at Woo to provide more contributions around the Search Block if we could rely on this extensibility feature.

@zieladam:

  • I’ve been working with @gziolo on merging 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/ changes into the WordPress 6.0 release branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch"..
  • The RC3 was released yesterday as @get_dave mentioned, next stop: RC4 and a stable version next week.
  • I’ve shipped [Gutenberg Data Tutorial] Part 4: Creating pages
  • I’ve proposed Typescript Entity configuration types – the last blockerblocker A bug which is so severe that it blocks a release. before shipping TypeScript types for getEntityRecord and other coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-data selectors for a great  autocompletion experience

@glendaviesnz (not present – shared by @paaljoachim):

  • There have been some requests for the addition of spacing presets in Gutenberg, similar to the font size presets that are already available, to allow theme designers to specify a select list of spacing values that can be applied to blocks.
  • It would be good to get some design feedback on this, in terms of the feasibility of adding this to the UIUI User interface, and how the UI for this might be structured.
  • I think there has been some ongoing discussion about the suitability of the current UI for selecting the font size presets, so would be good not to repeat any problems that might exist there.

Open Floor

The full Open Floor discussion is available 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/..

Right click action on List View (and in wider editor)

  • @andrewserong would like to surface this PR which explore adding right click behaviour to the List View.
  • He’d love feedback on whether overriding the native right click behaviour is something we want to do in Gutenberg.
  • @get_dave, @zieladam and @mamaduka were in favour so long as it considered a11yAccessibility 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) concerns.
  • @paaljoachim had reservations around discoverability.
  • It was noted that @alexstine had already provided a11y feedback and an opt out via editor settings has been added to the PR.
  • @hypest also noted that it should consider mobile interactions as well.
  • Agreed to leave further feedback on the Issue/PR itself.

Request for feedback: enabling styling of interaction states in editor

  • @get_dave wanted to surface these design explorations on enabling styling of interaction states (:hover, :focus .etc) within the editor.
  • Now is a good time to provide feedback and raise concerns in order that the first iteration of the interface can be as good as it can be.
  • Folks were broadly in favour of this functionality being added.
  • @fabiankaegy was concerned about adding a lot of additional clicks to every interaction – felt this would be better served with a persistent setting instead of a local state in every component.
  • @get_dave requested input from folks experienced with Global Styles and Theme JSONJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. to discuss the potential data structure for such a feature.
  • @tomasz noted it would be nice to have a full overview of the state ie. color + typography etc. rather than split between different panels. A summary would avoid having to keep a mental map in your head of all interactions.
  • Please continue to discuss on the Issue.

Breaking change: promoting experimentalFetchLinkSuggestions to stable 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.

  • @get_dave would like to flag a PR which renames a long-standing experimental API to stable.
  • There’s been lots of discussion around experimental APIs and the deprecation strategy recently, so I wanted to flag this one final time before it gets merged.
  • Hopefully the impact is minor but it’s worth being aware of as it’s been around as __experimental for quite some time.
  • Noted that outreach has been done to community Plugins making use of the API.
  • Will merge this week unless there are any blockers raised.

Thanks to everyone who attended the meeting.

#core-editor, #core-editor-summary, #gutenberg, #meeting-notes, #summary

Editor chat agenda: 18th May 2022

Facilitator and notetaker: @get_dave.

This is the agenda for the weekly editor chat scheduled for 2022-05-18 14:00 UTC.

This meeting is held in the #core-editor 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 you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion:

  • If you have an update for the main site editing projects, please feel free to share as a comment or come prepared for the meeting itself.
  • 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, #core-editor-agenda, #meeting

Editor chat summary: 11 May, 2022

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, May 11 2022, 03:00 PM GMT+1 in Slack. Moderated by @paaljoachim.

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/ 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 releases

Gutenberg 13.2 released 11 May.
Whats new in Gutenberg 13.2.

WordPress 6.0

WordPress 6.0 Project board
Project board for Dev Notes
Help Wanted: Test WordPress 6.0

Key project updates

Task Coordination

@amustaque97

I will be looking into issue: Post Comments block: Whitespace on top of warning message

@tomasztunik

A while ago I’ve shared a core Search Block extensibility feature request to give the ability for 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. variations to provide custom search query parameters. Since then I’ve also shared a proposed implementation and I’d love some feedback. This would allow projects like WooCommerce or other projects that introduce custom post types to re-use the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. search experience to provide custom search components for their extensions.But it would also allow creating custom searches for core WordPress experience ie. searching only within specific categories, tags or authors.

Open Floor

Announcements, questions and discussions.

@annezazu

I’d like to start a discussion around adding a new label to the new label to the Gutenberg repo around issues that impact adoption. The aim would be to have an easier way to see, at a glance, what big issues are impacting the adoption of Gutenberg.

  • Would folks find value in having those issues clearly communicated?
  • Does a new 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/ label seem like the right approach? If not, what other approaches would work well?
  • If a new GitHub label works well, what name would work best?

Here are a few suggestions:

  • [Type] Adoption Blockerblocker A bug which is so severe that it blocks a release.
  • [Type] Impacts Adoption

@marybaum
I like Adoption Blocker.
Could also make it active: Blocks Adoption.
@fabiankaegy
I also like the idea of that. Though it is difficult to really gauge the actual impact it has on the party that is blocked from adoption. I guess I’d like to understand what requirements a ticketticket Created for both bug reports and feature development on the bug tracker. needs to fulfill in order to “justify” getting that label applied.
@tomasztunik
I think if people had this at the back of their heads when triaging issues or evaluating feature requests this could shift the perspective toward the product and ecosystem more than the problem itself. Like another “standard” question to ask yourself when evaluating something.
@priethor
This is an example of an issue that would need that label: something already existing in WP but that Gutenberg doesn’t support, preventing Gutenberg adoption and users needing to stick with classic implementations:
https://github.com/WordPress/gutenberg/issues/3144
@mikachan
Another alternative for the label itself could be ‘migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. blocker’ (or ‘impacts migration’ / ‘blocks migration’).

@ndiego

This is a thought-provoking question that I asked earlier in #6-0-release-leads (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/.). When we fix bugs in Gutenberg (and also in Core), they can have unintended consequences when users upgrade to the new versions where the bugs have been fixed. Thought I would share it here as well.

To get more details go directly to the Open Floor discussions in the Core Editor Slack channel.

#core-editor, #core-editor-summary, #gutenberg, #meeting-notes, #summary

Editor Chat Agenda: 11 May 2022

Facilitator and notetaker: @paaljoachim

This is the agenda for the weekly editor chat scheduled for Wednesday, May 11 2022, 04:00 PM GMT+1. This meeting is held in the #core-editor 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 you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion:

  • If you have an update for the main site editing projects, please feel free to share as a comment or come prepared for the meeting itself.
  • 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, #core-editor-agenda, #meeting