Tag Archives: core-editor

annezazu 8:18 pm on June 4, 2020
Tags: core-editor,   

What’s next in Gutenberg? (June)

This is a monthly update containing the high-level items that 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/ contributors are focusing on for the next month. Please join us in our efforts and let us know in the comments if anything is blocking you from doing so. As a reminder, here’s an overview of different ways to keep up with Gutenberg and the Full Sitesite (versus network, blog) Editing project. 

Full Site Editing (FSE)

Work on this major focus is ongoing and is expected to continue iterating over the next months. Right now, we’re wrapping up the major work needed to build the technical foundation of this project and are soon moving towards expanding the UX & UI:

We’re watching the Theme Experiments repo as well to see how themers are attempting to build 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.-based themes. Thank you to everyone participating there as it’s a super useful way for us to determine prioritization. 

Follow along:

The high level, important tasks have been split into sections and highlighted on this overview issue.

Global Styles

As a reminder, Global Styles refers to the system that defines and manages global aesthetics allowing overall site styles, theme styles, and blocks to work well together. The Global Styles work remains a major focus for this month. The important tasks for the month are:

Follow along:

You can follow the progress of this focus in this overview issue.

Navigation Screen

The new Navigation Menu screen and Navigation block will continue to be iterated on and polished. In particular, work is being done to create a true drag and drop experience and to explore improving the selection/focus experience (feedback welcome). In an effort to expand the functionality allowed within navigation, work is being done to explore adding different kinds of blocks other than links.

Follow along:

You can follow the progress of this project on this project board.

Refining the interface

The previous releases saw a big UI update for the editor canvas and the inserter. The team will continue to iterate based on the remaining tasks and the user feedback. The remaining tasks here include:

Follow along:

You can follow the progress of this focus in this overview issue. 

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. Screen

As part of expanding the block editor to other screens in the adminadmin (and super admin), work continues to improve the widget screen including finding bugs in the legacy widget block, ensuring synchronization, and more. Depending on the work done here, the screen should be ready to leave the experimental state and receive additional feedback soon. 

Follow along:

You can follow the progress of this focus by reviewing issues with the [Feature] Widgets label.

Areas to be aware of:

Block & 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 Developers

@aduth just merged this pull request to update default block categories which should be available in next week’s plugin releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software.. This could be particularly impactful for block implementers, since the default categories have changed. For now, please review this drafted devnote here as a point of reference for this change. 

Theme Developers

@epiqueras recently broke down all template tags alongside their block equivalent in order to lay the groundwork for Full Site Editing: 

“The idea is for everyone in the community, especially those very familiar with traditional theme development, to contribute to this list. There might be things we are missing. There might be things we could lose.”

Please check out this overall issue and share what might be missing. 

Ways to Help:

While the above items are our focuses, don’t forget that you can always help with triage, needs testing issues, good first issues and reviewing PRs. If there’s anything we can do to makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). contributing easier, let us know in the comments or in #core-editor chats. While we can’t promise to fix everything, we’d appreciate being aware of any blockers.

#core-editor #gutenberg-next

Paal Joachim Romdahl 9:57 am on June 2, 2020
Tags: , core-editor, ,   

Editor Chat Agenda: 3 June, 2020

Facilitator and notetaker: @ajitbohra

This is the agenda for the weekly editor chat scheduled for 2020-06-03 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 have anything to share for the Task Coordination section, please leave it as a comment on this post.

If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

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

#agenda, #core-editor, #core-editor-agenda, #gutenberg

annezazu 5:51 pm on May 27, 2020
Tags: core-editor, , , ,   

Editor Chat Summary: 27th May, 2020

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, May 27, 2020,14:00 UTC and was moderated by @itsjusteileen.

Quick Announcements

WordPress 5.5 Upcoming ReleaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. 

The planning roundup for 5.5 can be found here. There are several features that are under an experimental flag in Gutenberg, and to have a chance to makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). it for 5.5 they’d need to be out of experimental by July 7th. This led to a quick discussion that the 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. screen can soon leave the experimental state!

@matveb chimed in to share the following later on to highlight that there’s plenty to do beyond the main projects that are underway if people want to/can help:

I wanted to mention that while many groups are focused on larger pieces of work (FSE, global styles, navigation, etc) 5.5 will require some focus on ensuring what exists right now is in good shape. That includes shipping the new design, patterns, the new inserter with new categories, new APIs and deprecations, etc.

Gutenberg version 8.2

Gutenberg RC candidate 8.2.0 was released this week with the stable release launched just after this meeting ended. Update your sites and check out what’s new.

Monthly Plan

There was limited discussion on the specifics of the current monthly priorities.

Task Coordination

Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.

@poena

  • Flagged this issue as needing a decision about the dynamic content with @matveb chiming in to say that there needs to be closer parity with the current theme experience as a start.

@paaljoachim

@nosolosw

  • Focusing on a new iteration of theme.json and early documentation for it.
  • Helping with reviews and other PRs, mainly in the areas of styles & 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. registration.

@michael-arestad

  • Dropping a new figma prototype very shortly on inserting saved (and new) template parts that deviates from previous designs and the current implementation. 
  • Planning to create a new issue with designs/discussion around a vertical grid for template building (and general layout things).
  • Planning to update the end to end full site editing prototype (i4).

@sageshilling

  • Working with coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-media data flow, design gallery, image block, gallery patterns.

@mapk

  • Working on the widgets screen with @jorgefilipecosta.
  • Updating UIUI User interface issues/PRs with Figma label.
  • Providing feedback on FSE work.
  • Redesign of spotlight mode with @youknowriad.

@karmatosed

  • Focusing deeply on navigation with a side order of triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors..

@andraganescu

  • Various work on the navigation screen
  • Added new suggestion types to LinkControl
  • Continued the work on adding delete to Entities

@nrqsnchz

  • working with @michael-arestad on inserting saved (and new) template parts (FSE).

@zebulan

  • Add RichText split-at-end/merge/remove behavior.
  • Add usePrevious hook to @wordpress/compose package.
  • Use toolbar exclusively for heading level controls in Heading Block
  • PR to replace instances of Lodash.includes with native JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. [].includes in the block-editor package is awaiting reviews.
  • PR to refactor ReusableBlockEditPanel to use ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. 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. is awaiting reviews.
  • PR for the Table of Contents Block needs technical help/feedback in order to progress along with accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) feedback.
  • PR for the Reusable Block edit component has made progress thanks to feedback/help but has one remaining behavior issue that’s blocking it.
  • Polish Custom HTML block PR is ready to go, assuming the stylistic changes are okay. Please provide design feedback.
  • Started a PR to update the Quote Block to use a light block wrapper but got stuck and need technical help to move forward. Solving this will help other blocks use light block wrappers.
  • Started a PR to add color controls to the List block but running into problems with style conflicts on most default WordPress themes.
  • Started a PR to add a heading level checker to the Heading block, based on prior efforts in this issue.

@itsjonq

  • Adding Padding controls
  • Working on video Background position controls
  • Working on cover image auto dominant colour detection

Open Floor

@youknowriad shared helpful guidelines for folks creating PRs to make the changelog easier to automatically compile.

  • When working on experimental screens and features, apply the [Type] Experimental label instead of Feature, Enhancement, etc.
  • When working on new features to technical packages (scripts, create-block, adding  react hooks, etc), apply the [Type] New API label instead of Feature, Enhancement, etc.
  • When fixing 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 making an enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. to an internal tool used in the project, apply the [Type] Build Tooling instead of Bugs, Enhancement, etc.
  • In PR titles, instead of describing the code change done to fix an issue, consider referring to the actual bug being fixed instead. For example: instead of saying “Check for nullable object in component”, it would be preferable to say “Fix editor breakage when clicking the copy block button”.
  • Take the time to choose the right [Type] label for your PRs. With some updates to the changelog command (type priorities), we should be able to support multiple types on a PR for some of the examples above.

Next step: @annezazu will look into updating both triage documentation and contributor documentation as appropriate.

Will core-editor participate in Contributor Day and should this be mentioned to participants? Raised by @itsjusteileen.

Yes! @youknowriad is planning to do a quick zoom chat to help people setup a Gutenberg environment at the beginning of the day. To come prepared, please have “Docker” + Latest node.JS LTS setup. This is also mentioned above under announcements.

Listing names in the code owners document to better understand who can be pinged for help/a review. Raised by @paaljoachim.

Paal encouraged everyone to review this document and keep it up to date. @karmatosed mentioned that relying on solid labeling alongside bringing in specific people from that list will likely help more for getting everyone to see issues appropriately.

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

Riad Benguella 4:32 pm on May 27, 2020
Tags: core-editor, ,   

What’s new in Gutenberg? (27 May)

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/ 8.2 is released. The team continues to heavily iterate on the two big projects: Full Sitesite (versus network, blog) Editing and the navigation screen.

The releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. also includes a number of improvements, features, 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 to the post editor.

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. Patterns

After the introduction of the search support, the Block Patterns UIUI User interface and APIs continue to improve with the introduction of the block pattern categories. In addition to that, a viewportWidth property has been made available to allow tweaking the width used on the block patterns preview. This is especially useful for large block patterns.

Cover Block content alignment

The Cover block saw the introduction of the new content alignment feature which opens up more design possibilities.

Editing flow

The editing flow is a constant priority for the project, and Gutenberg 8.2 introduces several enhancements to improve the writing experience. Copying, cutting, and pasting single blocks is now much easier. You can also split out of captions and button blocks using “Enter” to continue your writing.

8.2 🇮🇹

Features

  • Cover block: Support customizing the content alignment. (21091) (22322)
  • Add Block Pattern Categories Support. (22164) (22410)
  • Copy the whole block if no text is selected. (22186)

Enhancements

  • Limit the most used blocks in the inserter to 6 elements. (22521)
  • Allow split out of caption on Enter. (22290)
  • Buttons block: Allow split and merge. (22436)
  • Improve video backgrounds for the Cover block in iOSiOS The operating system used on iPhones and iPads.. (22346)
  • Combine Calendar Help and Close buttons in the date and time picker. (22176)
  • wordpress/env: Better run command errors. (22475)
  • Add support for named orientations and literal colors on custom gradients. (22239)
  • Use theme color as focus color. (22261)
  • Refine the specificity of the embed block styles. (21599)
  • Change inserter search placeholder text color. (22444)
  • Improve interactions and add unit parsing to the unit selector used in Cover block. (22329)
  • Use smaller spacer and cover block step values. (22320)
  • 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): Add explanatory text before the a11y.speak aria-live regions. (22112)
  • Add Animoto, Dailymotion block embed icons. (21882)
  • Group block: Match frontend markup in the editor. (21867)
  • Iterations on the welcome guide. (21847)
  • Don’t show protocol in link suggestions. (20350)
  • New Block Patterns:
    • Hero and two columns. (21130)
    • Features or Services. (20898)

New APIs

  • ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. 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.:
    • Add new React hook UseCopyOnClick as an alternative to the ClipboardButton component. (22224)
    • Add usePrevious hook to wordpress/compose package. (22540) (22597)
  • wordpress/env:
    • Granular volume mappings. (22256)
    • Add command to display Docker container logs. (21737)
    • Add a destroy command. (21529)
    • Add phpunit support. (20090)
  • wordpress/scripts:
    • Add CSSCSS Cascading Style Sheets. support to start and build scripts. (21730)
    • Support enabling/disabling dev tools, bundle analyzer and externals for build and start scripts. (22310) (22426)
  • Support preloading 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. requests using the fetchAllMiddleware middleware. (22510)
  • Support controlled InnerBlocks. (21368) (22366)
  • Add Close button 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.. (22323)
  • Block API: Allow block registration without categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging.. (22280)
  • Support customizing the viewportWidth for block patterns. (22216)

Bug Fixes

  • Fix theme CSS bleed in the Button component. (22460) (22522)
  • Fix CSS validation error on Button block styles. (22583)
  • Fix editor crash potentially happening when hovering style variations. (22490)
  • wordpress/env: Start database service before running tasks. (22486)
  • Fix editor crash when zooming. (22408)
  • Fix Button border radius set as 0. (22393)
  • Fix Cover block resizing. (22349)
  • Writing Flow: Fix reverse block selection after block deletion from rich text. (22292)
  • A11y: Include reusable blocks in announced inserter search results. (22279)
  • Remove the previous style CSS class when the default style variation is chosen. (22266)
  • Show the global inserter in container blocks nested inside locked templates. (22115)
  • Prevent the Page Break block from showing up as the first block in the inserter. (22523)
  • Polish code editor and fix iOS scrolling issue. (22021)
  • LinkControl component: Fix search result focus state border. (22553)
  • Prevent contributors for accessing the Media Modal. (22306)

Performance

  • Adds a command to run performance tests across branches. (22418)
  • useMovingAnimation: Avoid initial transform animation. (22536)
  • Optimize resizable preview hooks. (22511)
  • Short-circuit validation for identical markup. (22506)
  • More accurate dependency list for useGenericPreviewBlock hook. (22355)
  • Add missing side-effect declarations. (22300)

Experimental

  • Full Site Editing and Site Editor screen:
    • Add page-based navigation. (22368)
    • Page and Template switchers improvements. (22449)
    • Add Query block. (22199) (22364)
    • Use the inserter panel. (22413)
    • Add basic “tools” menu. (22539)
    • Implement post switcher and integrate with “navigate to link”. (22543)
    • Add focus mode and top toolbar modes. (22537)
    • Add entity editor to post content block. (22473)
    • Add ‘Review changes’ button for multi entity saving flow. (22450)
    • Fix Post Author block render issues. (22397)
    • Refactor Post Author block to use block context. (22359)
    • Templates Endpoint: Add resolved query arg to return only relevant templates. (21981)
  • Navigation Block and Screen:
    • Add block movers to the block navigator. (18014)
    • Add ellipsis menu to block navigator. (22427) (22517)
    • Add standard notices to nav menu page. (22374)
    • Implement the creation of menus on the edit navigation screen. (22309)
    • Add menu location management. (21351)
    • Navigation Link block: Add RichText split-at-end/merge/remove behavior. (21764)
    • Fix navigation block placeholder overlap. (22407)
    • Adds orientation class on frontend for the navigation block. (22272)
    • Refactor block navigation block contents. (22487)
    • Fix navigation screen crash with no menu items. (22342)
    • Adds save and failure notices to the navigation screen. (22326)
    • Display the block appender only for the currently active menu. (22311)
    • Allow editing of new menu items from the block inspector. (22210)
    • Submenu nesting and saving new nested items. (21671)
  • Block-based Widgets screen 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. tab:
    • Use interface package on widgets screen 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.. (22304)
    • Use single block editor in the widgets screen. (22140) (22459)
    • Use the mobile view for the Customizer. (22533)
    • Add legacy 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. to calendar transform. (14586)
  • 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.:
    • Implement Managed CSS for Global Styles. (20290)
    • Support theme.json in Post editor. (22520)
  • Block Directory:
    • Activate deactivated blocks if already installed . (22286)
    • Only support an array of assets when injecting assets. (22289)
    • Remove the author rating when none exist. (22184)
    • Update layout for smaller inserter width. (22124)
    • Add error messages inline. (20001)

Documentation

  • Document experimental theme.json. (22518)
  • Fix duplicate grammar docs. (22466)
  • Document the performance testing commands. (22464)
  • Docs: Update note for extraProps filter. (22419)
  • Recommend adding an API docs section. (22415)
  • Add side effect documentation. (22379)
  • Update block editor docs to incorporate the block-toolbar Popover Slot. (22308)
  • Adds a README to MediaReplaceFlow. (22268)
  • Typos and tweaks: (22254) (21968) (21695) (22554)

Code Quality

  • Avoid circular dependency issue in AutoBlockPreview. (22425)
  • Remove opinionated label color from CustomSelectControl component. (22594)
  • Image block:
    • Use hooks. (22499) (22277)
    • Remove extra div wrapper in the editor. (22585)
  • Remove redundant condition from setting default grouping. (22563)
  • Testing: Replace require.requireActual with jest.requireActual. (22370)
  • Use a light block DOM for the Cover block to map frontend markup. (22348)
  • Rename a complementary area component property. (22336)
  • Block API: WP_Block: Document attributes class property. (22222)
  • Polish block wrapper elements file. (21304)
  • Move supports to block.json files for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blocks. (22422)
  • Create Block: Simplify the process of defining a config for templates. (22235)
  • Block Edit: Use hooks. (22433)
  • Add BlockContext component to type-checking. (22353)

Build Tooling

  • ESLint 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: Fix dependency group checking for CommonJS. (22230)
  • Restore Playground 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/ Pages deployDeploy Launching code from a local development environment to the production web server, so that it's available to visitors.. (22443)
  • Fix API Docs generation for filenames with spaces. (22513)
  • Fix check-latest-npm.js failure on Windows. (22485)
  • Refactor the changelog script as a release tool command. (22380)
  • Enable import/no-unresolved ESLint rule for Gutenberg. (20905)
  • Only allow ECMAScript stage 4 features. (22083)
  • Storybook: Use a consistent port number. (22552)
  • Add 0BSD to GPLv2 compatible licenses. (22391)
  • Refactor the release tool and split it into several command files. (22003)
  • Replace wp-scripts env usage with wp-env in CI. (20280)

Various

  • Update: ResizableBox makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). showHandle true by default. (22360)
  • Fix dirty state end-to-end test intermittent failuire. (22532)
  • Fix dirty state end-to-end test. (22448)
  • Add a simple block patterns end-to-end tests and a test utility. (22414) (22495)
  • Remove insert block delay from end-to-end tests. (22377)
  • Add an end to end test to verify cover can be resized with drag & drop. (22369)
  • Upgrade Reakit to stable v1.0.0. (22352)
  • Use alternate display for the popover in alignment matrix. (22351)
  • Fix deprecated version used for register_pattern. (22341)
  • API Fetch: Remove deprecated useApiFetch. (22333)
  • Framework: Pin nvmrc to specific current LTS. (22236)

Performance Benchmark

The following benchmark compares performance for a particularly sizeable post (~ 36000 words, ~ 1000 blocks) over the last releases. Such a large post isn’t representative of the average editing experience but is adequate for spotting variations in performance.

Version Loading Time KeyPress event (typing)
Gutenberg 8.2.0 7.4s 29.7ms
Gutenberg 8.1.0 8.6s 29.7ms
WordPress 5.4 9.2s 26.8ms

Kudos for all the contributors that helped with the release. 👏

#core-editor, #editor, #gutenberg-new

annezazu 5:51 pm on May 20, 2020
Tags: core-editor, , ,   

Ways to keep up with Full Site Editing (FSE)

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

Yearly:

The WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ Roadmap with Four Phases of GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ updated by @chanthaboune and/or @matt. This is the highest level overview of the changes coming to WordPress.

Quarterly: 

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

Monthly: 

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

Block Based Themes Chat. These chats are currently wrangled by @kjellreigstad in the #themereview SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel and are dedicated to sharing FSE changes that will specifically impact themes. Agendas and summaries are shared on the make/themes blog. 

Biweekly: 

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

Weekly: 

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

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

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

Daily:

Checking in on FSE PRs and FSE issues on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/. This will give you a nearly real-time understanding of what’s being worked on by the developers and designers. 

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

Feedback welcome

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

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

#full-site-editing, #gutenberg

Jorge Costa 9:00 pm on May 13, 2020
Tags: core-editor, ,   

What’s new in Gutenberg? (13 May)

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/ 8.1 releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. mostly contains developments/enhancements on experimental screens, 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 performance improvements.
It also contains some new features available on the general editor screens, described bellow.

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. pattern features

Gutenberg 8.1 brings pattern search to makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). it easier to insert the desired patterns and a new pattern: the testimonials.

Copy block action

The copy block action is a small quality of life improvement for touchscreen users or users who don’t use keyboard shortcuts. Gutenberg 8.1 adds a button to the collapsed block actions (next to duplicate, etc.) to copy the selected block(s). The feature is quite similar to the “Copy all blocks” but then for the selected block.

8.1 🇹🇷

New features

  • Pattern search (21944)
  • Testimonials block pattern. (20894)
  • New Transforms:
    • Embed blocks into Paragraph blocks. (17413)
    • Code to HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. block and the opposite. (21779)
  • Add copy action to the blocks. (22214)

Enhancements

  • Implement Block Navigator selection on the Nav Menus page. (22017)
  • Write block patterns in PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 to allow 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.. (21946)
  • Post title: handle paste as blocks. (21758)
  • Clear Publish Date Button. (20914)
  • Add gap between nested submenus. (22227)
  • Block Library: enhance the author’s block. (19894)
  • Add “black” and “white” color options to the default color palette. (22082)
  • Light blocks: social links. (22078)
  • CustomSelectControl: set aria-hidden to empty option list. (21298)
  • Add some more g2 icons. (21825)
  • Allow the column block in the inserter. (20502)
  • Delete menus in nav menus experimental screen. (21486)
  • Visual and experience improvements to existing sub-navigation flow. (22107)
  • Reduce font-size and line-height of “it’s time”. (21627)
  • Template Loader: Introduce get_template_hierarchy(), drop gutenberg_template_include_filter(). (21980)
  • Make parts of the BlockNavigationList overridable using slots. (21948)
  • Change the color alpha input step to match the slider step. (21953)
  • Navigation: fallback for undefined orientation. (22057)
  • Remove the subscription button from the blogblog (versus network, site) template. (22129)
  • Move the Entities Saved States from Modal to 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.. (21522)

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. Changes

  • Update the Patterns API to avoid ambiguity. (21970)
  • Expose the registered pattern slugs in get_all_registered. (21619)
  • Fix doc-building pre-commit API hook issue. (22116)
  • 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/.: Block directory – Typecast author_block_count as integer. (17594)
  • Block API: Block Context: 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. content, prepare attributes at render, pass a block to render. (21925)

Experimental

  • Add undo-redo UIUI User interface to edit-sitesite (versus network, blog) and edit-widgets. (21955)
  • Light blocks: site title. (22069)
  • Update: Use EntityProvider on the 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. area. (22008)
  • Site editor:
    • Extract gutenberg_find_template_post helper. (21959)
    • Fix default editor background. (22182)
    • Refactor close button slot. (22179)
    • Make close button replaceable. (22001)
    • Add home icon to template switcher. (22004)
    • Updated template content. (22044)
    • Fix spelling mistake. (21991)

Performance

  • Reduce re-renders from block nodes context. (22134)
  • Move memo() from BlockStyles to BlockPreview. (21993)
  • Avoid rerenders of the entire BlockInspector when block attributes change. (21990)
  • Optimize BlockStyles by using 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. and React.memo (instead of HOCs). (21973)

Bug Fixes

  • Popover: Fix closest().parentNode null error. (22264)
  • Correct color palette in color settings. (22138)
  • Remove import of inexistant component. (22130)
  • Build Tooling: Run packages build before lint. (22088)
  • RangeControl: Fix number input change interaction. (22084)
  • Fix entity selection through save panel. (22011)
  • ESLint 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: Relax check for i18n-text-domain rule. (21928)
  • Block Library: Fix ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. does not recognize isSelected prop in Spacer block. (21924)
  • Reinitialize the iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser. after the parent block is moved around. (21916)
  • Configure the navigation editor with correct __experimentalFetchLinkSuggestions. (21873)
  • Create the proper 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. on paste. (21864)
  • Refactor FontSizePicker component. Fix bug on undo. (21757)
  • Move caret to the end of pasted content. (21755)
  • Embed: use the same SmugMug URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org regex as the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. (21744)
  • Navigation block: use new icon in placeholder. (21713)
  • Fix Template Part placeholder preview. (21623)
  • Restore the missing background color on the nested submenus. (22228)
  • fix: [#21777] Prevent focusing of FireFox address bar. (22215)
  • Fix flaky test in rich text. (22202)
  • Fix flaky test: tag “target” attribute. (22200)
  • Fix extra tab stop on Modal component. (22063)
  • Writing flow: fix vertical arrow nav in table (and generally grid). (22105)
  • Gallery block / media-placeholder – Preserve changes made while upload in progress. (19134)
  • Add missing dependency. (22086)

Tooling

  • Build Tools: Validate package-lock.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. for “resolved” errors. (22237)
  • Build Tools: Disable ESLint no-console for bin directory. (22033)
  • Build Tools: Changelog: Normalize entry to end with period. (22010)
  • Add analyze-bundles script. (21827)
  • Add changelog generator script. (19866)
  • Add a method for publishing patches to the Lerna scripts. (21844)
  • Add additional e2e debugging option. (21845)
  • Replace espree with babel. (21853)
  • Update diff to 4.0.2 and work around tree-shaking issues. (21994)
  • Increase the severityseverity The seriousness of the ticket in the eyes of the reporter. Generally, severity is a judgment of how bad a bug is, while priority is its relationship to other bugs. of jsdoc/no-undefined-types. . (21942)

Code Quality

  • Block: move new props to hook. (22212)
  • Block: avoid useLayoutEffect. (22108)
  • Try: Reduced specificity base block margins. (22051)
  • Update the audio and video blocks to use a light wrapper in the editor. (22028)
  • Remove unused animation lingering in paragraph file. (22020)
  • Columns. Remove the top and bottom margin from individual column blocks. (22018)
  • Try better inserter toggle styling. (22016)
  • Block Editor: Rename block context in BlockListBlock. (21922)
  • Remove duplicate CopyHanddler. (21817)
  • Types: Restore element, icons, primitives types. (21781)
  • Convert core toolbar buttons into ToolbarButton. (20008)
  • Block Directory: Add end 2 end tests. (20023)
  • ClipboardButton: use hooks. (22220)
  • ClipboardButton: remove wrapper span. (22218)
  • Block Library: Update FSE blocks to use block context. (21696)
  • Group: Zero out the intrinsic margin set to every block in the editor. (22209)
  • Unset the inherit for links. (22160)
  • Template Loader: Get rid of _wp_current_template_part_ids globals. (22143)
  • Block Library: Post Author: Reference attributes by argument. (22114)
  • Remove pass by reference of the $scripts and $styles attributes in client-assets.php. (21987)
  • Use optional chaining, optional catch binding. (21967)
  • Extract block mover buttons so that they can be individually imported. (22122)sss

Documentation

  • Scripts: Mark env script as deprecated. (22158)
  • Docs: Use InspectorControls from wordpress/block-editor. (22153)
  • Fix bundle analysis change location in the changelog. (22136)
  • Documentation: Improve the way CHANGELOG files are maintained. (22126)
  • ESLint Plugin: Add missing rules to root README. (22042)
  • Fix props, in example, code for Edit Post module. (21976)
  • Document e2e test command options. (21962)
  • Add an example for how to choose a style variation for a block variation. (21927)
  • Add documentation for onSelectURL property. (20799)
  • Document the old patterns API deprecation. (22177)
  • Coding Guidelines:
  • Document 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/. language support commitment. (22030)
  • Add “gotchas” section about ES2020 optional chaining. (22029)
  • Recommend function components. (22090)

Various

  • Expose presets declared via add_theme_support in global styles. (22076)
  • Update is-promise package to the latest version. (21940)
  • Blocks: Register FSE blocks if the experiment is enabled. (21536)

Mobile App

  • Add missing RTL support for some mobile components. (21502)
  • Remove separatorType prop from TextControl, RangeControl… (21365)
  • Color settings. (21326)
  • Global styles provider. (21637)
  • Update existing templates to use new blocks. (21857)
  • Enable pullquote block. (21930)
  • Merge 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". back to master for v1.27.1. (22234)
  • Wrap button blocks with buttons blocks in page templates. (21939)
  • Components: Create a separate .native entry for ToolbarItem. (22229)

Performance Benchmark

The following benchmark compares performance for a particularly sizeable post (~ 36000 words, ~ 1000 blocks) over the last releases. Such a large post isn’t representative of the average editing experience but is adequate for spotting variations in performance.

Version Loading Time KeyPress event (typing)
Gutenberg 8.1.0 10.88s 43.61ms
Gutenberg 8.0.0 13.30s 42.97ms
WordPress 5.4 10.80s 52.87ms
#core-editor, #editor, #gutenberg-new
annezazu 5:19 pm on May 13, 2020
Tags: core-editor, , , ,   

Editor Chat Summary: 13th May, 2020

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, May 13, 2020,14:00 UTC and was 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/ 8.1.0

Gutenberg 8.1 RC was released on May 11th and is on track for a final releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software.. 8.1 is focused on performance improvements, 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 multiple enhancements around several areas of the editor and the experimental screens/features. Outside of those focuses, there are also new features like new transforms, pattern search, and a new testimonials pattern.

Weekly Priorities

There was limited discussion on weekly and monthly priorities. @andraganescu noted that the new navigation menuNavigation Menu A theme feature introduced with Version 3.0. WordPress includes an easy to use mechanism for giving various control options to get users to click from one place to another on a site. screen is coming together! Overall though, Full Sitesite (versus network, blog) Editing (FSE) is a major focus right now and can be followed here with the overall plan shared here.

Task Coordination

Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.

@nosolosw

  • Main focus has been “Global Styles”. Currently, iterating on some framework tasks that need to be to unlock before resuming work on the UIUI User interface. This will be the focus for this week too.

@aduth

  • Working on some documentation and framework-level improvements, largely summarized in this slack convo.
  • Refreshing and splitting off work around renaming 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. categories.
  • Next up, continuing work on renaming block categories plus follow-up work around block context.

@youknowriad

  • Did two zoom chats to help contributors (one in #core-editor, one in French WordPress slack).
  • Trying to land categories support for patterns.

@nrqsnchz

@retrofox

  • Made progress in the Tips approach. It’s now possible to register tips defining the scope, descriptions, and other parameters.

@earnjam

  • Handling some PR reviews to help with triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. starting with the list of non-draft PRs with no review, less than 2 comments, and sorted by least recently updated to try to find anything that has slipped through the cracks.

@mapk

  • Spent time triaging issues.
  • Search block enhancements.

@itsjonq

  • Continuing to add features to Cover block via new control UIs (“Design Tools”). In doing so, also building a set of incredibly robust and feature rich control primitives (e.g. Input).
  • Longer termer goal would be to (hopefully) refactor/replace existing controls within Gutenberg with these ones. These components would of course be available for block/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 authors as well, enriching the UI experience of the Gutenberg ecosystem as a whole.

@vindl

  • Working on allowing extensions/replacements of editor close button which is part of this issue. It’s already merged for the site editor, and now I’m looking to expand it to the post editor too.
  • After the above work wraps up, will return to site editor UI tasks. 

@michael-arestad

  • Working on template part creation/manipulation design patterns. Right now, exploring how they might work as sections. This could be really slick when building templates.
  • Continuing on this path this week and will likely spin up some zooms if anyone wants to help or just watch! Links will be shared in #design.

@sageshilling

  • Working on the image and gallery blocks.

@andraganescu

  • Working on the navigation screen– just merged menu location management.
  • Will continue to work on various issues on this project for the next week.

@zieladam

Working on the experimental navigation screen, in particular:

Open floor

Do we instead of listing packages and versions, need to list components and versions? Raised by @paaljoachim.

This discussion point was raised in reaction to a comment from @clorith in this trac ticket on adding Gutenberg plugin version information to the Site Health section. Right now, this tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. issue needs feedback to keep the issue moving. It was agreed that there’s no easy solution to this partially because WordPress versions includes features and bug fixes of various versions of Gutenberg. This makes handling bug reports tricky for example.

Next step: Taking the discussion back to the track ticket!

Do we need to apply a max height for the style placeholders in the inspector? Raised by @munirkamal.

The problem right now is that placeholders need to have a preview so if the block is quite large the the preview is too. @matveb chimed in to say that previews are loading example content now so this decision is up to the block author. However, if an example is not provided it falls back to actual block content which is where a max-height could be useful.

Next step: A “Needs Design” Label was added to the issue for design to explore further.

What time and day would work for the discussion about full-site editing and the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. customize component? Raised by @dlh.

The original proposed date and time was 20:00 UTC on May 25th but this time may not work well for the people working on Full Site Editing. @youknowriad suggested meeting more around 15UTC/16UTC but wants to hear from others. Tied to this, @aduth noted that May 25th is Memorial Day in the United States which

Next step: If you’re interested in attending this meeting, please share in the comments below what time might work best. Notes will be taken and posted either way if you can’t makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). it.

Can we add a block ID to each block that is unique and stable to help connect server data to client data? Raised by @sageshilling.

This came up as part of work done on the image and gallery blocks (full context here). There have been various discussions about this historically in the early days of Gutenberg. These discussions always concluded that while there is a need for this from time to time we don’t want to pollute markup and/or we don’t want to keep two separate things in sync. Before discussing anything technically, it was agreed that a case needs to be made for why it should go in core and why extension-based solutions are not apt.

Next step: @sageshilling will collect use cases and details in a post on metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. to propose this idea.

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

Paal Joachim Romdahl 5:23 am on May 12, 2020
Tags: , core-editor, ,   

Editor Chat Agenda: 13 May, 2020

Facilitator: @andraganescu. Notetaker: @annezazu

This is the agenda for the weekly editor chat scheduled for 2020-05-13 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/..

  • 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/ 8.1.0
  • Monthly Plan & Weekly Priorities
  • Task Coordination
  • Open Floor

If you have anything to share for the Task Coordination section, please leave it as a comment on this post.

If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

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

#agenda, #core-editor, #core-editor-agenda, #gutenberg

Paal Joachim Romdahl 11:07 am on May 7, 2020
Tags: core-editor, ,   

Editor chat Summary: 6 May, 2020

This post summarizes the weekly editor chat meeting agenda here. Held on Wednesday, 6th May 2020 held in Slack. Facilitated by @paaljoachim.

Monthly Plan

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/? (May)
https://make.wordpress.org/core/2020/05/06/whats-next-in-gutenberg-may/

A summary from @youknowriad
Let’s do aa small recap about the previous months and the next one:
– We did some good progress about 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. Patterns on the last month
– FSE Sitesite (versus network, blog) Builder screen is getting closer in terms of parity with the post editor, there’s still some work left
– FSE: we worked on the context 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., it was a bit more complex than originally anticipated but we landed something
– Navigation screen continues to improve
– Implemented several Global Styles config per block (colors, line height,…)
The priorities remain mostly the same because most of these are big projects we’re polishing and improving.

Some highlights to come:
– Query Blocks
– More iterations to the patterns (categories)
– Sibling inserter redesign maybe
– Continue on Site Builder and Navigation Screen
– Expand 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. capabilities

Task Coordination

@karmatosed
Different blocks in navigation: 22096
Sub-nav improvements: 22087
Ellipsis and movers: 22089
All my other focus is on triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors., “needs design” and “design feedback” label has replies.

@nosolosw
I’ve worked on style things at various levels:
– theme.json: convos & reviews about its role to control the editor.
– Global styles: expose style presets (font-size, color, gradients) as CSSCSS Cascading Style Sheets. vars.
– Editor styles: fix for font-sizes.
Also contributed to some misc things such as convos and PR about the 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/. version we support, and provide feedback on switching the JSDoc parser we use for our API docs tool.

@mkaz and @annezazu
Working on a plan to improve block editor docs.

@youknowriad
– Worked a little bit on some follow-ups to the Patterns UIUI User interface (search support)
– Worked on some small refactorings PRs, 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 performance.
– Planning to focus more on the categories support for patterns.

@andraganescu
– I am mostly working on the new nav screen project.
– 21557 PR in progress of adding a new feature to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. data entities delete.
– I constantly try to do more reviews!

@nrqsnchz
– I continue to work on iterations to the Welcome Guide.
– Starting to take a dive into Full Site Editing with Inserting existing saved template parts.
– Started to put together a matrix of pattern categories in a spreadsheet found in other site builders so we can get a better idea of what categories we’d want to have in the inserter.

@pstonier
I’ve been finalizing adding the functionality to 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. the Latest Posts block by author and added the ability to show the author in the list: 16169

@michael-arestad
– Posted a prototype of a page switcher when editing site. (could use some feedback)
– Iteration on template partial creation – (needs dev)
– Proposed persistent block navigator.
Next up:
– Iterate on template partial insertion.
– Explore transforming template partials.
– Could use help with implementation of multi-entity saving.

@mapk
Search block enhancements.
Block mover explorations.
Helping to push scheduled post PR forward with @earnjam.
Providing feedback where I can.

@retrofox
First approach on improving tips. Looked at contextual tips issue.
The idea is being able to register tips defining description, scope, etc.
Related issues
Add rotating block-specific tips to the inserter’s help panel.
Compile a list of possible block-specific tips.
Consider adding adding a rotating Tips area to the block sidebar.
Blocks: Contextual tips tied to specific search queries.

@brentswisher
Hoping to finish adding storybook stories for components this week.
Hoping to review: Storybook: Add DateTimePicker.

@marek
Improving the post scheduling process by showing you what dates you’ve already scheduled for. Needs feedback/reviews.

@zieladam
Working on visual improvements to the navigation block (#22107) and experimenting with making menu items editable in the inspector on the experimental nav menus page (#21948).

@Zeb
– Table of Contents block.
Done: Added multipage post support. Ability to toggle if all multipage headings are listed.
Needs: technical reviews/feedback, accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) and copy reviews. A G2 icon.
– Heading block H1-H6 level control. Needs: design and technical reviews.
– Custom HTML block polish PR that could use another design review.
– PR: Enable backspace to remove empty Navigation links. Needs help to fix issues and how to handle certain scenarios like removing a Navigation Link with children.
– PR: List block: add color controls. Stuck: Editor style conflicts.
Resolving this PR would open the door to adding color controls to other blocks that use HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. lists (e.g. Latest Posts or Table of Contents).
– PR: PreviewOptions: remove chevron from button. What should the button look like, since it’s text/border styles are inconsistent with the Save Draft button.
– PR: Embed: use same SmugMug URL regex as core. Needs: Review.
– PR: Refactor reusable block edit component using hooks and Refactor ReusableBlockEditPanel to use hooks (and add type info) both need reviews.
– PR: Polish block wrapper elements file. Needs: Review.

Open Floor

Discussing the need to find additional people to review PRs.

@youknowriad
We have 137 on the 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/ team on Gutenberg that can approve PRs. How can we increase the confidence level of these people to actually review and approve PRs?
@earnjam
…Work on more areas = more confident to makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). a decision regarding those things.
@aduth
It’s something I was really hopeful CODEOWNERS approach would help with. Where people can specialize in certain areas of the codebase, and it’s fine to focus in those areas. At this point, I think Gutenberg has scaled to such a size that no single person can possibly know how it all works.
@karmatosed
Ideas from experience with triage:
Open sessions for learning how to review PRs. During these go through a few and pick out gotchas and gain confidence through doing.
Mentoring/pairing on PR reviews.

@owoce
Asked for interest in..
Multi-select: add a toolbar with formatting options when multiple blocks are selected. Owoce started some work on this as a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party (repo) but she is hoping to get something like this into the editor itself.
@youknowriad
Riad shared an example from an older multi select PR that stalled.
@paaljoachim and @youknowriad
Both mentioned that it would be good to create a Github issue when questioner is ready to do so as to continue discussion in an issue.
In the mean time check out her Gutenberg-multi-edit plugin currently at alpha stage.

@brentswisher
Github is having their satellite conference virtually and free this year here: https://githubsatellite.com/schedule/ if someone is looking for learning opportunities.

@kjellr
NB! A heads-up to label issues and PRs that impact theme styling or markup with the label: [Feature] Themes

#core-editor, #core-editor-summary, #gutenberg

Riad Benguella 12:13 pm on May 6, 2020
Tags: core-editor,   

What’s next in Gutenberg? (May)

This is a monthly update containing the high-level items that 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/ contributors are focusing on for the next month. Join us in our efforts.

Full Sitesite (versus network, blog) Editing

Work on this major focus is ongoing and is expected to continue iterating over the next months.

The Site Editor UI is improving constantly and it remains a priority while other important building pieces will be tackled such as the Query block and the controlled InnerBlocks 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..

The important tasks have been split into sections and highlighted on this overview issue.

Global Styles

The Global Styles work remains a major focus for this month. The important tasks for the month here are:

You can follow the progress of this project on this overview issue.

Navigation Screen

The new Navigation Menu screen and 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. will continue to be iterated on and polished.

Refining the interface

The previous releases saw a big UIUI User interface update for the editor canvas and the inserter. The team will continue to iterate based on the remaining tasks and the user feedback.

The remaining tasks here include:

  • Support pattern categories.
  • Improvements to the inserter tips.
  • Better canvas inserters (also called sibling inserter)

While these are our focuses don’t forget you can always help with triage, needs testing issues, good first issues and reviewing PRs.

#core-editor #gutenberg-next