Tag Archives: chats

Andrei Draganescu 3:52 pm on November 7, 2023
Tags: chats, ,   

Proposal: cancel core editor chat

Proposal: cancel coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor chat

The core editor chat is a 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/. meeting that takes place every week on Wednesdays in the core-editor channel of the WordPress Slack instance, focused on discussing topics related 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/ 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. editor development.

This meeting has served in time as a place for the following types of communication:

  • general announcements about Gutenberg or WordPress
  • Gutenberg project updates, on various features in development
  • task coordination between the various people contributing
  • community introductions and help during open floor
  • issue escalation – bringing attention to specific issues
  • requests for help or reviews, a place to ask for an extra pair of hands or eyes

The meeting has served us well over the years, but in the past two years several developments occurred:

  • the post pandemic speed of people picking up these meetings was suboptimal
  • the GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ project management has been considerably better
    • there are people managing tracking and overview issues, updating them with project status
    • the project features of GitHub itself have been significantly upgraded
  • several other efforts picked up steam:
    • there is a new learn section on 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/
    • there is a revamped developer blogblog (versus network, site) on wordpress.org
    • developer experience and outreach programs improved
    • we have a constant stream of events like hallway hangouts on varied topics

Considering the above, I suggest that the meeting has now become an inefficient use of the time for those organizing it. 

It’s not only that the attendance is low, but the topics discussed and the lack of interest in the meeting itself point to the fact that the other avenues are doing a better job at keeping people engaged and updated with the progress of Gutenberg in WordPress, as well as providing much better avenues for getting support to contribute to or implement the core editor.

Therefore we propose discontinuing the meeting.

What do you think? You’re all invited to chime in with pros and cons, ideas and anything related for the duration of a three week comment time for this proposal to cancel the core editor chat for an indeterminate duration of time.

Thank you

Many thanks to the following list of people who have been helping across the years with running, summarizing and managing the agenda of the core editor chat:

@ajitbohra @annezazu @paaljoachim @fabiankaegy @jorgefilipecosta @get_dave @zieladam @bph

Important note

For the duration of the comment time (three weeks) there will be no more core editor chats (meetings).

#chats, #editor-chat, #proposal

Jorge Costa 10:10 am on March 18, 2022
Tags: , chats, , ,   

Editor chat summary: Wednesday, 16 March 2022

This post summarizes the weekly editor chat meeting on Wednesday, 16 March 2022, 14:00 UTC held in Slack.

WordPress 5.9.2

@jorgefilipecosta said WordPress 5.9.2 was an important security and maintenance release and asked everyone to update all their sites. There were updates until WordPress 3.7, everyone even if not on the last WordPress major version should be able to update.

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

Gutenberg 12.8 was released around the chat time by @priethor. Details about the release can be backed on the release page.

Key projects updates

Patterns

@jorgefilipecosta shared the following update related to patterns:

The current experience when creating a new page and starting with a blank canvas is not ideal. It would be better if we had something premade ready. On #39147 we are interacting on this experience. Patterns will be able to specify they are full page patterns, and uses will be able to create pages in an easy way. We also merged recently changes to how one inserts and replaces the content of a template part and now are changing the flows for the query 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. #38997.

Styles

@jorgefilipecosta said that we have some improvements to how duotone styles are handled in #38681, and we also fixed the centered image alignment styles at #39422.

Comments 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. block

@bernhard-reiter shared the following update:

Quite a bit of progress there, thanks to the team: There’s a fix for the broken pagination that’s now ready to merge. The Generic 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 PR has also been approved. Finally, there’s a bugfix for two rather annoying bugs with inner block selection and duplicated settings in the inspector controls of the Comments Query Loop block.

Native mobile application

@carlosgprim said the team is focused on the following on Drag and Drop project and addressing content uploading issues.

Task coordination

@jorgefilipecosta

I will start for the next week I want to update #38997 and improve the modal UIUI User interface to contain a grid and carousel view. I also plan on working on the base editor experience be it by helping the effort to get partial multi block text selection, helping the nested blocks on quotes and lists and other related tasks. Let’s see how much we can improve the basics.

@paaljoachim

  • I have made multiple videos. Among these one is about going from a classic theme to an FSE theme.
  • Added notes into the fse-outreach-experiment channel.
  • Added feedback to a few Navigation block exploration issues.
  • Made a few new issues: #39490, #39380, #39307.

@mamaduka

  • I’m continuing my work on Block Locking UI and 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.. Here’s my latest proposal on implementing “Locked by System” in the editor.
  • Finished an error handling audit for media blocks. They should correctly display upload errors now 🙂
  • Created PR to make error messages returned via uploadMedia utility more consistent. This is a breaking change, so I’m looking for some feedback.

Open floor

Template part resizing

@paaljoachim said: “With exploring the transition og going from a classic theme and over to Twenty Twenty Two I noticed that I was not able to adjust the 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. template height.I also made an issue for it here: #39490“.

@jorgefilipecosta anwsred “To me template part is just a block to reference an area. It should not deal with the content its styles its size etc. I guess to control the height of an area like an header one can put a group block or cover block inside that header”.

The conversation continued and @paaljoachim said a group was already present, both participants in the discussion agreed there maybe be space for improvements and the conversation will continue on the issue. If you have some thoughts on this please share them.

wordpress/frontend-dx Gutenberg subteam

@bernhard-reiter shared the following:

I’d like to create a GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ team (under the WordPress org, as a sub-team of the Gutenberg team) for those of us that are currently working on Fronted Developer Experience (tentatively named “Frontend DX”, which means we’d use the handle @wordpress/frontend-dx). There’s currently a rather well-defined group of folks focusing on this, so it’d be quite handy for us to be able to @mention the entire team.

The participants showed support for this idea and @bernhard-reiter is going to create the subteam.

PR’s and Issues awareness

@azouamauriac raised the attention of the team to PR #39426 that is ready for review and to issue #39395 which is a regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. that happened on 5.9. @jorgefilipecosta said #39395 probably is something that we should fix in WordPress 5.9.3 release.

#block-editor, #chats, #core-editor, #core-editor-summary, #gutenberg

Jorge Costa 2:03 pm on January 17, 2022
Tags: , chats, , ,   

Editor chat summary: Wednesday, 12 January 2022

This post summarizes the weekly editor chat meeting on Wednesday, 12 January 2022, 14:00 UTC held in Slack.

WordPress and 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/ Releases

@jorgefilipecosta started the chat by saying Gutenberg 12.3 was released on the 5 of January. Details related to the Gutenberg release can be read in this post. The notable features are new blocks one can use and the gap and typography support additions to the group 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..

Regarding the WordPress release, @jorgefilipecosta said the RC2 was released on 11 of January and things are going smoothly with the WordPress release. The final WordPress 5.9 version is planned for 25 of January 2022.

From the editor side on 5.9 must-have board we still have 9 to-do items and 3 items are in progress.

Project updates

Native mobile app

Shipped

  • ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. Native v0.66 upgrade

Fixes

  • Line-height issue on Android
  • Link picker freeze when virtual keyboard is hidden
  • Text formatting issue when backspace is used
  • Cover block regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. related to the color settings

In progress

  • Final tweaks in the GSS Font size/color implementation
  • Finalizing reliability improvements of the mobile translations pipeline

Template editor, site editor, and styles

Two PR’s were submitted (#1, #2) that implement code editing for edit site and the ability to copy the template content. These PR’s when merged will bring UI parity between the site editor and post editor.

Regarding the styles project the focus was on testing things and improving what we have in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. by fixing some bugs, improving the escaping of some parts, and fixing missed backports.

Task coordination

@mamaduka

@jorgefilipecosta

Worked on bringing parity between site editor and post editor. For the next week plans on:

Open floor

WordPress 6.0 project board

@paaljoachim shared the following:

As there are issues that are punted from WP 5.9. Will it be helpful to get a project board up as soon as possible for WP 6.0 to be sure that punted issues and other issues are handled early? Similar to how TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. has a 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.) for 6.0 early tickets.

@jorgefilipecosta answered that we don’t have a board for 6.0 because the assumption is everything that is being worked on will be part of 6.0.

Block editor dependency on user endpoints

@tomjn shared the following:

I had hoped to raise a subject I wanted to talk about last week but I will not be around tomorrow. I’d much appreciate anybody who can look into the issue of the editor making the invalidinvalid A resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. assumption that the user is always logged in and always has a usable active session.

This has crippled Frontenberg but also doesn’t account for expired WP sessions, cancelled sessions, etc, and does not have an appropriate fallback ( it results in a partial code editor view ). Default behaviour in WordPress has always been to show a modal dialog with the login window, and past Gutenberg behaviour has been to assume the user cannot publish and adjust the UIUI User interface accordingly e.g. submit for review rather than publish/update. It’s also prior precedent that these types of REST request are bundled with the initial page load to avoid the additional request so there are performance consequences

– https://make.wordpress.org/core/2022/01/04/editor-chat-agenda-5-january-2021/#comment-42271

– https://github.com/WordPress/gutenberg/issues/37682

@jorgefilipecosta said this seems like an issue we should address. We just need someone to work on the fix.

@tomjn said that his hunch at the moment is that getEntityRecords handles this and the same pattern would work for getCurrentUser but it’s mainly speculation. If that’s the case the fix is simple.

Typography settings consitency and list block class

@luminuu shared the following:

While testing the 5.9 RC1, I came across the inconsistency of the font family selection at the typography settings. It was reverted from the paragraph block but it is still in use in some other blocks. To avoid confusion with users, I suggested to remove the font family setting from the other blocks as well. Please have a look and share your thoughts: https://github.com/WordPress/gutenberg/issues/37826

I also want to request some help with the PR https://github.com/WordPress/gutenberg/pull/36676 as I’m struggling to have the checks running through properly. This PR is related to an issue of the 5.9 Must Have project: https://github.com/WordPress/gutenberg/issues/37388

@jorgefilipecosta said that regarding #37826 @ntsekouras created a PR to address it. Regarding #36676 the addition of a class to the list block was discussed as part of the fix to the issue #37388. @oandregal proposed an alternative fix and left his thoughts after the chat in this comment.

Unexpected style warnings

@joostdevalk shared the following:

Hey team! I have a problem I want to submit to you all.

  • In this PR an error was introduced that is thrown when Gutenberg thinks styles are not added properly.
  • As becomes clear from the content of the errors, only styles added by blocks or themes are taken into account. However, plugins can add styles as well. At Yoast we add a style sheet to add styling to our metaboxMetabox A post metabox is a draggable box shown on the post editing screen. Its purpose is to allow the user to select or enter information in addition to the main post content. This information should be related to the post in some way..
  • We haven’t changed the way we include those styles in years, but suddenly console errors started showing up. Even though nothing breaks functionally, errors are thrown, which means people will start blaming us if something actually breaks.
  • In this PR the level of the errors was lowered to warnings.
  • In October, Ella drafted a PR that would make sure no warnings were thrown anymore.
  • Because this was quite a big PR, it was decided to extract the fix related to the warnings to a separate PR. This PR has been open since about a month.
  • Earlier this week, the PR was removed from the WordPress 5.9 Must-Haves project board.

We’d really like to have Ella’s PR merged into 5.9 to prevent warnings from being thrown, to prevent support load and getting the blame for broken things that are unrelated to us.

@mamaduka said:

I’m a little worried about including the fix in 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). that hasn’t been well tested.Maybe we should remove the warning from 5.9; since plugins that add CSSCSS Cascading Style Sheets. files to the editor have no way to fix it. And as @joostdevalk mentioned, it will just increase support overhead.Then we can try and ship #37466 in the 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..

@aristath added:

At this point, the warning does more harm than good. The intention behind it is good, but if we can’t fix the current implementation for 5.9, then temporarily removing these warnings makes sense

@jorgefilipecosta we can have a PR disabling the warnings and discuss in more detail on the PR.

Escaping in bocks

@fabiankaegy said the following:

I just quickly wanted to throw in this discussion I opened regarding how block should handle late escaping the content of inner blocks in dynamic blocks here: https://github.com/WordPress/gutenberg/discussions/37823It is something that keeps popping up in for example WordPress VIP code reviews and there isn’t really any guidance in the docs or in the core codebase.

@jorgefilipecosta shared that applying wp_kses_post to the content like wp_kses_post( $content ) does not seem like a good idea as a block may legitimately need to output unsafe content like javascriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. events etc and if those come from the block they are expected and safe.

@jorgefilipecosta added that the issues arise when a block outputs any information the user can manipulate like attributes. Any kind of output containing use information should be escaped as close to the output as possible. Following the WordPress principle of sanitizing sooner escaping late. @jorgefilipecosta ended the subject by sharing that @getdave is making some improvements to how core escapes information.

#block-editor, #chats, #core-editor, #core-editor-summary, #gutenberg

Jorge Costa 3:49 pm on September 28, 2021
Tags: , chats, , , ,   

Editor chat summary: Wednesday, 22 September 2021

This post summarizes the weekly editor chat meeting on Wednesday, 22 September 2021, 14:00 UTC held in Slack.

What’s next in 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/? (Mid-September 2021)

@jorgefilipecosta said the post with the goals for the Gutenberg project in September is published and referred that the priorities are the template Editor, Patterns, Global Styles 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., the design tools., and 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./navigation editor work.

As a follow-up @ntsekouras brought attention to an experiment to trigger some discussions – a Patterns explorer, asking people to share their thoughts.

Project Updates

Mobile Application

Shipped

  • Improve error handling for embed block
  • Improve Reusable Blocks inserter UIUI User interface

Fixes

  • Fix image block height and border regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5.
  • Fix back icon color in dark mode

In Progress

  • Additional Embed block improvements
  • GSS Font size, line height, colors

Components package

Shipping

  • Completed a migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. away from the createComponent function. This simplifies the process of adding new components to the library, using the more straightforward View component.
  • Following up on the recently expanded contributor guidelines, we simplified the structure of the guidelines and added a table of contents.

In Progress

  • @youknowriad merged a PR that introduces a navigation component to the Global Styles 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., which moves us closer to the updated designs. We’re experimenting now with a revised Navigator component that may provide greater flexibility for the design.

Navigation Editor

Lots of work happening on priority items. Thanks to everyone who is contributing so much work.

• REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. interactions have been improved and more issues identified.
• Started looking at ways to add links in Bulk.
• Using Theme JSON to control the block in the editor has been ruled out.
• Another Hallway Hangout is on the cards – dates/times to be confirmed.

Task Coordination

@annezazu

Hallway hangout for adoption pathways for FSE with Marcus & Dave, continue amplifying the current block theme switching exploration (please check it out!), did some light triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors., and shared a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor improvement post on the new Widgets Group block!

@ntsekouras

  • Query Pagination with `flex` layout(#34876, #34897).
  • Pass the search value to inserter, when clicking Browse All(#34912).
  • Delayed loading state of SSR component(#35033).
  • Pattern Explorer experiment(#35006).

@jorgefilipecosta

For the next week, the plan is to continue iterating on the design and address the remaining follow-ups we have thinks like changing the border of the input field from a gray to slightly different gray changing the dimension of inputs from 30px to 40px, changing the focus look on the range control.

@mciampini

Will keep supporting @jorgefilipecosta and other folks working on the @wordpress/components package, including most of the work that is being done on the new Global Styles sidebar.

Open floor

Responsiveness

Roman Axelrod asked the following:

It was mentioned earlier, but… At time moment, core editor doesn’t provide options of setting different styling rules for each device / breakpoint (Preview modes: Desktop, Tablet, Mobile).

Right now, the rules are global. For example if I set padding: 60px to Group block from the right sidebar of the editor, this rule is going to appear on Desktop and Mobile.I curious if we are going to have the same functionality that all popular page builders have? Usually they provide a list of breakpoints and ability to “overwrite” styling rules of previous breakpoint. It gives ability of adapting the design by requirements.Is this something that we can expect soon? Are we going to have something like this in 2021?

@jorgefilipecosta said he thinks that is not something on the roadmap for 5.9, but allowing to control how things look depending on the dimensions of the place where they are rendered is something that will end up existing.

Custom Fields

Roman Axelrod asked the following:

Are there any plans or ideas of using Custom Fields in core blocks?
For example, imagine the situation where I have 20 pages. All pages have a “Hero” section that contains title, text, button on the left and image on the right.
The design is the same but the content is different and unique for each page (kind of a template).Now let’s say, after I built these 20 pages, we realized that the Heading block should be 5px bigger.
How should I fix that? It might be annoying to go page by page and update the font-size of each heading.As a reference, Elementor page builder provides this kind of option – they call it “Dynamic Content”.
I thought that the block-template-parts of FSE will solve this case. But this is still not there. Are there any thoughts/discussions about similar cases?

@jorgefilipecosta answered the following:

Hi Roman, maybe the solution to your issue is to define a CSSCSS Cascading Style Sheets. variable that represents the size. Theme.json provides a mechanism for declaring the css variables, and then instead of using 5px as value you use the css variable as the value. Changing the variable will then change the size in every place.

Roman followed up asking about how non-developers would be able to change those values. @jorgefilipecosta said that If one wants to allow a user to change a CSS variable, one could do it by registering a custom sidebar to change the variable. Maybe one day core offers something that automatically renders a UI where users could change variables registered using theme.json, but it is not part of the road map for now.

Developer Hours online

@bph made a big announcement during the core editor chat:

There will be a make core post with more info, this is just a heads-up, about a trial initiative to hold “Developer Hours online” every other week, with a group of Gutenberg developers, a short topic and then answering attendee’s Block and Theme building questions, with screen sharing of code and follow-up post. Depending how the trial goes, we might expand it. If you want to be part of that initiative let me know or comment on the post.

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

Jorge Costa 5:57 pm on August 5, 2021
Tags: , chats, , , ,   

Editor chat summary: Wednesday, 4 August 2021

This post summarizes the weekly editor chat meeting on Wednesday, 4 August 2021, 14:00 UTC held in Slack.

WordPress 5.8 final release

@jorgefilipecosta congratulated all the people that contribute to the WordPress 5.8 release. Adding that it was a big release that changed multiple things in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., added part of the FSE engine, implemented 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. widgets between other big additions.

@youknowriad invited people to participate in a retrospective that is happening. And added the following:

One thing I didn’t share on my comment there is that we’ve been on a feature release work for a long time. I’d love if we can focus more on quality related work (polish/performance…). For instance if you worked on a feature on previous releases, what can you do today to make it better in terms of code, performance and maintenability.

What’s new in 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/ 11.2.0

@jorgefilipecosta announced that Gutenberg 11.2 was released before the chat, and asked people to report any regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. found in their tests or if the update did not work as expected.

Project updates

Site Editor

@jorgefilipecosta submitted a PR that proposes a mosaic view one of the goals for July & August. The PE contains most of the functionality proposed in the mockups but not all of it because the PR was already huge. The PR also implemented the logic for an editor modes functionality that will be used to add the code editor in edit site very useful for example to full site editing theme developers.

Navigation block

@mkaz shared that, the Navigation Block is in a good state, still iterating but the next big step is a call for testing in the next week. And asked people to keep an eye out at #fse-outreach-experiment or the make.wordpress.org/test site. The team will collect feedback from that call to define what areas need focus, improving, and further iteration.

Navigation

Widgets

Native mobile application

Available in the next release:

  • “New block” block picker badge for 50% of users to measure performance.
  • Setting the 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. via the Image block directly.
  • Fixed a crash in the column block, and an issue with the “More” menu in the UBE.

In progress

  • Updated the Mobile Gallery Block Refactor (PR) with the changes from Web and merged it.
  • Block Picker Search, Embed block, editor onboarding help section, GSS Font size, line height, colors.

Task coordination

@youknowriad

Is working on performance work. Has a PR improving inserter search performance.
Is also iterating on some layout-related additions. Like the block gap support.
Reviewing the PRs that he can help with.

@joen

Looks forward to getting back to polishing and improving the navigation block, list view, and a ton of other cool things, perhaps even a little framer animation! Is also going to land github.com/WordPress/gutenberg/pull/32659 one of these days, and follow up with what that will mean for the Gallery block.

@gziolo

  • Finished working on adding support for variations in block.json file to WordPress core: As part of the efforts the same 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. proposes a unified way to apply translations to block.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. and theme.json.
  • Finished working (together with @jsnajdr and @walbo) on webpack upgrade from v4 to v5 in the build tooling: It would be great to have a wider testing before the team lands it as it impacts Gutenberg, Storybook and all projects that use wordpress/scripts.

@get_dave

Mainly working with @joen on adding a Text field to the Link UI to improve the UX around adding links (mainly in the Nav Editor). Also taking a look at pattern-based solutions to some Widgets screen markup backwards compatibility problems. Starting to think about Navigation Editor and theme.json again.

@jorgefilipecosta

His objectives for the week are:

  • Address feedback and merge the mosaic view PR
  • Propose a follow up PR with the remaining mosaic functionality.
  • Propose a PR with the code editor view on the site editor.
  • Investigate and improve the performance of the site editor.
  • Submit some site editor 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 and code quality/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. improvements.
  • Review the locking improvement proposal.

Open floor

Alignments in the shortcodeShortcode A shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site. block

@paaljoachim share the following:

The Shortcode block does not have alignment or a way to add a custom CSSCSS Cascading Style Sheets.. Here is a conversation in 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/. which would be helpful to take a closer look at: https://wordpress.slack.com/archives/C02QB2JS7/p1627590018095900

Adding that he is hoping that we can improve the shortcode block, as it is very limited in functionality.

@jorgefilipecosta said that for this use case the shortcode should be nested inside a group block.

@paaljoachim added that the shortcode is not working well inside the group block and as a follow up is going to open an issue so the team can investigate this further. The issue was created after the chat.

Wassim Boussebha new contributor presentation

Wassim Boussebha introduced himself to the participants of the chat:

I am Wassim Boussebha 18 years old,  computer science student in first year , I am interested to contribute to gutenberg project and be one of the maintainers in the future, currently I am learning computer science basics and foundations including algorithms, computer operating systems,databases….

Adding that he would like to know what is the specific tech stack that would allow him to contribute and work on this project and if it would be possible to provide some orientation.

@jorgefilipecosta thanked Wassim Boussebha for the interest in contributing. And together with @paaljoachim shared links to some tutorials, explained the tech stack, and referred what could be the first issues Wassim can work on. @jorgefilipecosta added that the team is available on slack to help with any blocking points while trying to contribute.

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

Jorge Costa 3:12 pm on June 21, 2021
Tags: , chats, , , ,   

Editor chat summary: Wednesday, 16 June 2021

This post summarizes the weekly editor chat meeting on Wednesday, 16 June 2021, 14:00 UTC held in Slack.

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/ 10.8 release.

The first topic was the Gutenberg 10.8 release. The release was already shipped a week before the chat https://make.wordpress.org/core/2021/06/10/whats-new-in-gutenberg-10-8-9-june/.

@jorgefilipecosta referred the main features of the 10.8 release (more 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. design tools and template editor enhancements) and added the Gutenberg 10.9 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). was going to be released soon.

@mamaduka will handle the 10.9 release, with @get_dave in the “shadow” and @youknowriad coordinating. Thank you all!

Monthly Plan and key project updates.

Mobile

  • Shipped:
    • Reusable blocks rendering and converting to normal blocks.
  • Soon:
    • RN upgrade to 0.64.x – Merge is very close
  • In progress
    • Gallery Block Refactor – Almost done
    • Editor Onboarding
    • Global Style Support – Colors
    • Adding search to the block inserter
    • Embed block
    • iOSiOS The operating system used on iPhones and iPads. share extension

Global Styles

The shape of the typography block.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. supports was updated to be consistent with the colors and theme.json shape. The data structures used internally were updated to keep track of each preset origin this open path to show multiple palettes e.g: theme and use for example.

Navigation block

The navigation block is still on deck and is getting home link improvements, invalidinvalid A resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. item flagging, and hopefully soon separate overlay colors. The big nav markup also remains on the to-do list.

Navigation editor

  • Exploring methods to provide a better way to disable/enable nav block features for the nav editor. Watch for incoming Issue on this soon!
  • Exploring creation of a reordering endpoint extension for the Menus 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. endpoint.
  • Looking into converting the persistence to utilise the REST bulk API.

Feel free to join to chat for this feature over at #feature-navigation-block-editor.

Block based WidgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. Editor

The 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. fixing work is in progress, every week a big set of issues is solved.

Task Coordination

@aristath

This week’s highlights:

  • Needs discussion/opinions/Review: Working on allowing more than 1 block-styles per-block (#32510). Will help with blocks that need to load styles from other blocks (example: comment-form loads button styles) and will also allow 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 & theme-authors to style individual blocks more efficiently.
  • Needs review: Allow decimals in spacing controls when using units like em, rem etc – #32692
  • Merged: Did for theme.css the same we did for style.css a few months ago to increase performance and load styles when a block gets rendered on the front (#31239)
  • Merged: Fixed a performance issue with the latest-posts block when there are many users in the database (#32620)
  • Backported commits from Gutenberg to wp-coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
  • Lots of PR reviews

Next week: Continue working on performance improvements, styles & scripts loading, PR reviews, and any bugs that come my way

@getdave

  • Finally merged the addition of rich previews when previewing external URLs in the link UIUI User interface (rich text only at the moment). https://github.com/WordPress/gutenberg/pull/31464
  • Helping out with Widgets screen bug fixes.
  • Continued to beaver away on the Navigatoin Editor foundational issues.

@paaljoachim

Is focusing on fixing Reusable block features.
At the moment focusing on adding a lock to the toolbar. A PR has been created here that could use some feedback: https://github.com/WordPress/gutenberg/pull/32710.

@mamaduka

  • Fixed “cover block exists” check for Image Block.
  • Worked on logic to hide settings from the “Options” menu in Widget editor on small screens.
  • Helping with new Widget Screen issues.
  • Helping with PR reviews.

@jorgefilipecosta

During the last week the main focus was the theme.json/global styles changes. For the next week: will help ship the theme.json 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, and 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.; Review PR’s that are pending review; Fix some bugs where he was pinged, and plans on restarting the work to advance the global styles UI. Will also help to ship the new enhancements to our locking API.

@andraganescu

Is focused on advancing the text based tasks around the widgets project (docs, dev note etc).

Open floor

Transforms vs convert API

@get_dave brought the following topic:

I’ve followed up on the `transform` vs `convert` API discussion with x2 options/suggestions for how we could come to a decision.

It’s not a huge problem, but it would be nice to see us unify around a single API for this action. Indeed `convert` has been “experimental” for over 2 years.

I believe this needs guidance from the Core team.

Adding that there are two options:

  1. Deprecate transform in favour of convert
  2. Augment the argument signature of transform and ditch convert.

On the issue @talldanwp referred that he is in favor of deprecating transform in favor of convert. During the chat and then in a comment in the issue @youknowriad said @talldanwp thoughts sound reasonable.

Dot in the Publish/Update button

@bobbingwide asked:

What happened to the dot in the Publish/Update button?
It’s still there when I edit a reusable block. https://sneak-peek.me/2021/06/16/what-does-the-dot-next-to-update-mean/

@jorgefilipecosta said the best path forward would be to have an issue where this issue could be discussed. @paaljoachim created the issue.

Click through vs lock for some blocks

@paaljoachim said:

I think we need a way to figure out if a block should have a click through or/and also a lock. Reusable block could really use a lock similar to the edit button in WP 5.6.

@joen said:

I worry that a lock icon and toolbar action will not be an obvious affordance for editing the contents, or help indicate why this block is any different from the surrounding blocks which you can click and edit. I think some of Jays designs from the previous ticketticket Created for both bug reports and feature development on the bug tracker. have potential.

This is a UXUX User experience decision and the discussion will continue on the issues and related PR’s.

#block-editor, #chats, #core-editor, #core-editor-summary, #gutenberg, #meeting-notes-2

Andrei Draganescu 5:02 pm on May 26, 2021
Tags: chats, ,   

Core Editor Meeting Notes 26 May, 2021

This post summarizes the latest weekly Editor meeting (agenda, slack transcript). This meeting was held 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 on Wednesday, 26 May, 2021, 2:00 PM UTC and was facilitated 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/ 10.7 release 

Gutenberg 10.7 was released today. It’s probably one of the biggest, if not the biggest in terms of number of PRs, releases to date.

Feature freeze

This week held the feature freeze for WordPress 5.8. From the wishlist @youknowriad mentioned 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. and the Post Author block as the ones being left out from the merge effort because of various issues. @mkaz mentioned that the navigation block is still searching for the best solution for its markup. @paaljoachim mentioned the refactored gallery block as one other item that didn’t make it into 5.8.

For the future, it was raised that WordPress should have a process that enables more often and early merges instead of doing everything all at once to avoid stressful situations.

WordPress 5.8 board

The GithubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ board for monitoring progress for WordPress 5.8 is still open and maintained. Past feature freeze there’s still a log of 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 and polish required and a few additional tasks like dev notesdev 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, and 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. and such. The board will serve us to track all of that.

Block based Widgets editor call for testing

Help Test the Widgets Editor for WordPress 5.8!  The block based widgets editor is in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. as part of the merge for 5.8, so now testing can also be done with WordPress trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.. Updating and bug fixing will continue 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.

Monthly Plan

The monthly plan for May 2021 is still up. @annezazu brought up that today is the last day for the current call for testing for the FSE Outreach Program and a new call for testing will also be launched soon after 10.7 is released.

Key project updates

Global Styles

@nosolosw shared this week’s global styles update:

  • Global Styles and Global Settings have been ported to WordPress core and will be part of the WordPress 5.8 release. The focus now is on polishing and fixing bugs as we find them.
  • Now that the 1.0 version of this feature has been shipped and we need to revisit focuses, I thought it’d be a good time to pause these reports while we figure out the next steps. Anything relevant should still be posted in the tracking issue but on an on-demand basis not weekly.
  • More at Issue 20331

Block based widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. editor

@andraganescu shared this week’s update:

  • The Block based Widget Editor. has been ported to WordPress core and will be part of the WordPress 5.8 release. The focus now is on polishing and fixing bugs as we find them. As always you can help by checking out the project’s board on GH and participate in the #feature-widgets-block-editor channel – open at all times of day!

Navigation block

@joen shared this week’s update:

  • Still trucking on with the navigation block. There’s a PR in queue that will enable global styles item padding (PR 31878). Also starting to look to helping with the List View component, which plays a key role in the block.

Block based navigation editor

@getdave shared this week’s update:

  • we’re continuing with our recent theme of lots of code quality and UIUI User interface fixes.Other than that we’re gearing up for addressing some of the “bigger picture” issues on the Navigation Editor including:
    • Disabling / enabling features in the block to better support the editor.
    • Adding support for missing hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same..
    • Improving the experience for editing navigations that are simple or complex.

Mobile/native

@hypest shared this week’s update:

  • Slash inserter!
  • Support for Xcode 12.5.
  • Blocking issue with translations broken which affects the mobile apps (relevant convo too).
  • In Progress: Editor onboarding, Block picker search, Embeds block, working hard to finish up ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. Native 0.64.x upgrade.

Task Coordination

@aristah

  • focused on the site-logo block. Long story short, after a brief experiment with using the default custom_logo theme-mod, it will revert to using a site_logo option.  PR 32229 – fixes 2 of the items in the 5.8-must-haves board. After this is reviewed and merged I’ll be porting the block to core.
  • Pushed some code-quality PRs, fixing eslint warnings
  • Allow non-latin characters in slugs – PR 32232  some eyes on this one would be appreciated since it fixes a long-standing bug for those of us with non-latin posts-titles.
  • Lots and lots of PR reviews. At this stage in the release process, if anyone has some time to spare pleaaase do some reviews, they help everyone move the project forward.

@joen

  • doing small 5.8 things where I can, including a notices bugfix and some Safari flickering debugging.

@annezazu

@mkaz

  • I’m looking at flaky tests and trying to see how we might be able to automate some bits to flag so people can address. This ticket discusses a little but merely retrying is not enough, we’ll need a way to precisely  identify what test is failing for action.

Open Floor

@poena asked, with the upcoming updates in 5.8 how should we call theme types to best differentiate them. A general consensus was that themes with PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher templates will be called classic themes and themes with HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. templates are called block themes.

@priethor brought up the monthly “what’s next” post and asked for suggestiions to improve the format and on feedback about its usefulness. Reply in a thread here, open a Guthub discussion issue or pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” Hector in #core-editor with anything you want to share about this.

@janw.oostendorp brought up their PR 31806 and asked for feedback. The on the spot suggestion was to add the description of a usecase for the filters added by the PR.

#chats, #meeting-notes

Jorge Costa 7:04 pm on May 3, 2021
Tags: , chats, , , ,   

Editor chat summary: Wednesday, 28 April 2021

This post summarizes the weekly editor chat meeting on Wednesday, 28 April 2021, 14:00 UTC held in Slack.

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/ 10.5 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). release.

The first topic was the Gutenberg 10.5 release. The RC was already shipped a week before the chat https://github.com/WordPress/gutenberg/releases/tag/v10.5.0-rc.1. @jorgefilipecosta said that we had some PR’s that were cherry-picked since the RC.

The final release was scheduled for the day of the chat. @jorgefilipecosta gave public congratulations to @ajitbohra for the first RC release!

Posts requiring feedback and insights.

@jorgefilipecosta said that we have two important posts published recently that deserve wide attention:

In case anyone has some insights or thoughts to share please leave a comment on the posts! Your insights are appreciated!


Monthly Plan and key project updates.

Global Styles

Shipped this week

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.

block.json / 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. supports

  • duotone #26752
  • padding: fix to allow units other than px #31057
  • font-size: can be used in nodes other than the wrapper #30879
  • border-color: fix for dynamic blocks #31020
  • blocks
    • padding for site title #31125
    • padding and letter casing for site tagline #31042
    • link color for post date #30791
    • table uses now background/text colors from the theme #30791

Internationalization

  • custom templates can be translated via theme.json #29828

KSES

  • fix to sanitizing user styles #30888

Site editor:

  • fixes for preset classes in the site editor #31218 #31217 #31204
  • fix for color selector in the UIUI User interface color panel #31015

Ongoing

theme.json

  • Changes to format #29891 are ready #30541 we’re now testing and polishing. It also includes versioning (aka migrate the older formats to the new one).
  • Improve 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. to take data from the theme directly #31267

block.json / block supports

  • typography (line-height, font-weight, etc) can be used in nodes other than the wrapper #30880
  • border and color (background, text) to the pull quote block #30951

New style properties

  • Add support for letter-spacing #31118

Misc

  • Add a new endpoint that exposes block editor settings through the REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. (by mobile to access global styles data) #29969
  • standardize capabilities of wp_template, wp_template_part and wp_global_styles #30893

Priorities

The priority continues to be shipping #29891 as soon as possible to unblock related work.

#28913 is a good issue to look at if you can lend a hand (help with reviews, migrate more blocks, more properties, etc).

Block based WidgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. and Navigation Editor.

@andraganescu provided the following update:

The legacy widget got an UXUX User experience upgrade and now the default view is the preview while the embedded widget editor in 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. had a performance overhaul. The focus on back combat continued with more testing with legacy widgets from various plugins. As expected a lot of new issues were opened.

On navigation editor the steady pace of improvements continued last week. Many thanks for the many welcome contributions!

Navigation block.

@joen provided the following update:

For the navigation block, we recently merged a padding change and I’m doing some followups (submenu gap, placeholder items, nav screen). Also looking at small separate improvements, and hope to get back to patterns now that the padding change is merged  — thank you for reviews.

Full Site Editing/Page templates

@youknowriad provided the following update regarding page templates:

I’ve spent some time iterating on that on the last days. We now merged the UIs for templates under a single “template” panel 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., we iterated a bit on the design of the “frame” to distinguish properly between template and post modes and simplified the save flow a bit. There are a number of iterations we could make, I don’t expect all of them to happen before 5.8, at some point, we’d make a final decision about whether it’s good enough to include.

@ntsekouras made a heads up regarding the query block:

Query block has now a wrapper element which for now is div (and will be the default when more tags will be supported) here: https://github.com/WordPress/gutenberg/pull/30804I’ve added a deprecation so everything will work as before but it will be good to update any block themes you have that use Query.

Task Coordination

@aristath

This past week:

  • Continued working on PR to autogenerate anchors for headings – #30825
  • Continued on @nosolosw‘s existing PR to allow inner blocks in quotes – #25892
  • Sustainability: PR to split theme.css styles and only load the ones for rendered blocks – #31239
  • Smaller PRs, mostly to improve code quality & linting errors
  • Lots and lots of PR reviews

Next week: Continue working on all the things mentioned above

@mamaduka

Helping out with the new Navigation Editor screen:

  • Sync menu name updates.
  • Introduce useMenuEntityProp hook.
  • Better handling of unsaved changes. PRs one and two.

Continued my work on the “Most Used Terms” feature and got great feedback about improvements. Thanks, everyone.Planning to continue working on Navigation Editor tasks.

@paaljoachim

@ntsekouras

@annezazu

Continued FSE Program work with the fifth call for testing, publishing a schedule of upcoming plans, reviewing/adding to a brief FSE doc, and launched a second round of questions. I’m planning to likely do a hallway hangout tomorrow on FSE issues/prs/designs in #fse-outreach-experiment for anyone interested!

@poena

Plans to continue on the site block changes but also I want to test the theme.json format and update the tutorial for creating block themes. Awaiting review of the letter-spacing.

@vdwijngaert

Will be working on a PR for moving the post/page title to the top bar. Current PR: #31240, but going to close that in favor of a new one based on a 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".

@jffng

@jorgefilipecosta

The main goal for next week is to review https://github.com/WordPress/gutenberg/pull/30541 and help it be merged. Plans on reviewing other Global Styles PR that are opened (e.g: https://github.com/WordPress/gutenberg/pull/30880). Wants to fix https://github.com/WordPress/gutenberg/issues/27478, which is probably very simple but may have a considerable impact and should be done ASAP.

Open floor

Post title moving in site editor

@bobbingwide said that there’s a problem moving the post title in the Site Editor. Adding that it’s tricky editing the topmost block if one does not have the toolbar set to top. @joen said @ellatrix is working on a fix https://github.com/WordPress/gutenberg/pull/31134.

G2 Components

@aristath asked the status of “G2 components” and if there is any plan on removing them. @youknowriad said that G2 is not removed but while reviewing some of the integration PRs, he noticed that G2 reimplements a lot of things we already have in Gutenberg in its own way. So the plan is still to integrate it but aligning with Gutenberg practices.

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

Andrei Draganescu 5:23 pm on March 24, 2021
Tags: chats, ,   

Core Editor Meeting Notes 24 March, 2021

This post summarizes the latest weekly Editor meeting (agenda, slack transcript). This meeting was held 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 on Wednesday, 17 March, 2021, 10:00 AM EDT and was facilitated 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/ 10.3 release 

At the time of the meeting the release process was having some issues, looked at by @gziolo and @bernhard-reiter

WordPress 5.7.1 maintenance release

WP 5.7.1 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). 1 will be on Wednesday 7 April, 2021 around 23:00 UTC and according to @noisysocks  the WordPress 5.7 board is the one to watch for editor updates that will need to land in this release.

Monthly Priorities

The monthly post outlining Gutenberg’s priorities for March 2021 is available.

Global Styles

@nosolosw shared this week’s global styles update:

  • Merged a few important things for 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.: add a layout config in theme.json, allow themes to use any style via theme.json whether or not the block supports it, translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. for custom templates.
  • Continue iterating 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. supports mechanism: allow skipping the serialization of border.
  • Some bugfixes: PR:30088.

Ongoing/Next tasks necessary for MVPMinimum Viable Product "A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia:

And more:

Full Site Editing (FSE)

@youknowriad and @vindl shared this week’s update:

  • working on making sure the frontend and backend are equivalent for all blocks and themes (as much as we can). The idea being that a user can open the site editor in an unstyled theme, start blank, add blocks bit by bit and having everything look as expected (front and back)

Infrastructure and UI milestone update:

  • Fix for template saving issue after switching FSE themes should be merged soon in PR:29842
  • Experiments to open browsing 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. to the appropriate template sub-menu landed today (PR:26964, PR:30098)
  • Persistent List View now has visual support for multiple selected blocks (PR:29878); its performance has also been improved (PR:29902)
  • Block toolbar is no longer overlapping the navigation panel (PR:29918)
  • Browsing sidebar will now close after template selection (PR:29956)
  • PR for template part block variations in the Inserter was merged (PR:30032), which should unblock the continuation of our work on semantic template parts

Block based widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. editor (and navigation editor)

@andraganescu and @grzim shared this week’s update:

  • the widgets editor progressed a lot by having two PRs landing, one that updated the REST API to work better with widgets and one that added the block inspector as a sliding panel to 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.. Work continues, and the aim is to have blocks in customizer functional in the 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 by the end of the month. Be sure to check things in #feature-widgets-block-editor 

Navigation editor update:

  • Minor improvements in styling PR:30168, PR:29832, PR:30129, PR:29975
  • Theme location settings moved to sidebar and have more features PR:29458
  • Fix of navigation editor toolbar which was disappearing in small screensPR:29967
  • Use the interface package for the navigation screen PR:30013
  • …and there are also a few other PRs that are nearly completed.

Navigation block

@joen shared this week’s update:

  • Layers of CSSCSS Cascading Style Sheets. has been refactored, dead code removed, inheritance fixed so styles work, and in general from here on out it will just be a great deal easier to manage. At the moment we’re also working on a hamburger menu for better responsive behavior, and it’s looking great already.

Mobile/native

@hypest shared this week’s update:

  • Landed various E2E tests related fixes, 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) improvements in UnitControl/StepperCell/RangeCell, removed the cancel button from many settings options on Android, split/merge regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. on Android fixed
  • In Progress and Next up: same as previous week’s update

Task Coordination

@annezazu

  • FSE Program wrangling (responding to feedback, triaging, figuring out what’s next to test, etc), testing FSE everyday (lots of reported bugs), and some light triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.!

@ntsekouras

  • Keep on explorations with block patterns integrations mostly on Patterns transforms(PR:29890) – could use some feedback/testing there 🙂
  • Expose Template part block variations to Inserter
  • Code reviews and triaging

@andraganescu

  • I have merged a few small PRs, triage and code review mainly for the new block editors (widgets and navigation).

@mamaduka

  • Image block now will use image default size from settings. PR:29966
  • Added since parameter to the deprecated function. PR:30017
  • Added/Updated since versions for deprecated features. PR:30072
  • Created PR for Gallery Block pattern to prevent adding all images when adding media. PR:30122

@paaljoachim

  • Triaging.
  • Focusing on getting more exposure on basic Full Site Editing user issues. Such as the preview drop down, easier save, editing template/post content etc 
  • Just made an issue for using a big modal to have a common approach for editing templates/reusable blocks/patterns.

@rafaelgalani

  •  I worked on some small PRs to fix some bugs 

Open Floor

@paaljoachim reminded that the new Gallery Block which uses Inner Image blocks has a call for testing. It is a new and awesome way to use the Gallery block, and it has a lot of potential. Go and test it..:)

#chats, #core-editor, #meeting-notes

Jorge Costa 11:24 pm on December 11, 2020
Tags: , chats, , , , ,   

Editor chat summary: Wednesday, 9 December 2020

This post summarizes the weekly editor chat meeting on Wednesday, 9 December 2020, 14:00 UTC held in Slack.

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

We had a 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. to fix three bugs. The details of the fixes can be checked in the release page.

WordPress 5.6

WordPress 5.6 was recently released, more details can be found here.

The release contains several enhancements to the editor. @isabel_brison made an overview post with the changes https://make.wordpress.org/core/2020/12/03/wordpress-5-6-core-editor-overview/.

Besides the editor enhancements, the 2021 theme is also a big step. It will have an equivalent 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. version that will test how robust is FSE and Global Styles to allow third-party themes.

@youknowriad said: Nice work @isabel_brison and others leading the editor side of the release. And the message was well supported on the chat using 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/. reactions. Thank you for all the work made leading the editor side of this release @isabel_brison!!


Monthly Plan and key project updates.

WidgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. and 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. screen

Widgets and customizer screen are still continuing with explorations going on to find the best way to add blocks support in customizer. 

Global Styles

We merged an update that makes client preset metadata match the server. ” – https://github.com/WordPress/gutenberg/pull/27453. And now we are also not passing some metadata to the client like selectors https://github.com/WordPress/gutenberg/pull/27449.
The work to make 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. translatable continues.
We are making some changes, namely removing some presets we are not totally convinced yet they should exist.
We already have some traction on the work to enhance our components to allow a better UXUX User experience on Global Styles; @q proposed the addition of some utils.
We also have some progress on the Global Styles extensibility with some filters being proposed https://github.com/WordPress/gutenberg/pull/27509.

Full site editing

The Query block now inherits the global query so FSE themes can add a query block in the index or archive templates and it will work for all archives, properly getting the query context from the visitor’s URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org: https://github.com/WordPress/gutenberg/pull/27128.

Template-parts now have a UIUI User interface to select the HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. element that will be used for their wrapper: https://github.com/WordPress/gutenberg/pull/27101 so they can define easier if it’s, etc.

The inserter was also improved and behaves as popover. The editor now has an outline mode used in both Site Editor and Template mode.

Native Mobile APP Updates

  • File block merged and usable.
  • Post’s Save dialog fixes.
  • Background and text color support in Group, Paragraph and Quote blocks
  • Use new link picker in various blocks: Button, Image, Gallery
  • Improvements on Separator block style
  • E2E tests execution improvement.
  • Release process documentation improvements.

An app release is going to be skipped because of New Year’s and people taking holidays on these days.

Task Coordination

@annezazu

Helped a bit with 5.6 Q&A docs, light GH triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors., continued working with @noisysocks on updating the features page and updating the issue templates, worked on FSE program preparation (including adding a welcome bot there and digging into current/recently merged PRs!), and dug in a bit to block directory adoption. Plans to do much of the same in the week ahead!.

@itsjonq

Continued the efforts of improving the Component System for Gutenberg.
The latest update is a (draft) pull-request to bring in the UI libraries/systems Has been working on (aka. “G2 Components”) https://github.com/WordPress/gutenberg/pull/27594. @itsjonq gave a thank you to @youknowriad and @gziolo for thoughts/guidance on integration.
@itsjonq said that t’s just the beginning, but it’s looking very promising. As always, @itsjonq tries Livestream design/dev updates on Twitch several times a week.
@itsjonq is also posting weekly updates on the project blogblog (versus network, site):
https://g2components.wordpress.com/.

@paaljoachim

Design triaged Bigger font for various handbooks.
Worked on several documentation tasks namely: Improving the intro page of the Block Editor Handbook and Re-examining introduction tutorials.

@youknowriad

Has been on working on some follow-ups to the addition of the “template mode” in the post editor.
The idea is that as we add features and enhancements, the code base becomes more complex as we take shortcuts so it’s important to circle back and “clean” the code a bit. Has been doing that with some 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) hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same., extracting common components and removing unnecessary complexity. Still has a few follow-ups planned. Some refactorings and some more features.

@jorgefilipecosta

Worked on an update that makes client preset metadata match the server. And another one that makes sure we are not passing some metadata to the client like selectors.
Did multiple reviews on Global Styles related work.
Proposed a solution to remove some of the presets we have being back-compatible with markup that uses them.
For the next week, plans on helping the effort to improve our WordPress components with PR reviews comments, feedback, etc. Wants to merge the Gutenberg side of theme.json i18ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill. and iterate and merge the typography presets removal. Also plans on making some progress on the design tooling visibility issue.

@cguntur

Would like to help with the Gutenberg documentation.

@aristath

For next week his main focus will be splitting core block assets loading and revisit progressive loading for FSE.
Would also love it if we could focus on removing auto-drafts for theme-provided templates but that one is a bit tricky as it touches lots of things.

Open floor

@bph bring to the attention of the participants of the chat an issue/question https://github.com/WordPress/gutenberg/issues/27321. @youknowriad shared some guesses of what may be the cause of the issue and @ntsekouras offered to followup and share his findings on the issue.

Skipping coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor chats of 23rd and 30th December

@paaljoachim share the following in the agenda:

I suggest that we skip having a Core Editor meeting the 23rd and 30th December as many will be having their Christmas holiday

People discussed this suggestion, there was no opposition to this suggestion so participants of the chat decided to skip the chats of 23rd and 30th December.

Starting the FSE Outreach Program

@annezazu said the following:

After digging into some recent FSE related PRs and talking with a few people, I wanted to raise the idea of starting the #fse-outreach-experiment after the next Gutenberg release. I think this PR from @youknowriad on a template editing mode is a great place to start but wanted to hear thoughts. Right now though, there aren’t a ton of things lined up to do next. I think this will be okay though as it’ll give an extended period of time for people to test (might be good with this time of year) and it’ll make it easier to tweak what we’re doing after this first round. How does that sound to you all? P.S. I welcome people flagging possible additional things to run through for the group. I try my best to stay on top of things but definitely miss stuff.

@youknowriad shared he agrees that the template editing mode is a good flow to test. He believe the feature in itself is still a little bit rough around the edges but testable.

@annezazu supported riad’s thoughts and concluded that she will get to work fleshing out the details to kick off the program. She welcomes any collaborators who might be interested!

For anyone reading this summary, you can be a part of the program by joining #fse-outreach-experiment channel.

One week 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). period

@youknowriad said:

The last releases saw a couple bugs being introduced and to address that I’d like us to discuss the possibility to try a one week RC in Gutenberg 9.6.

The participants of the chat showed support for this idea. The plan is to start having a one week RC period. The next release will still follow the normal schedule, so we give more time of notice to allow publishing the notes of the meeting (this post), and we have a fuller release otherwise it would be just a one-week release which would be very small.

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