This post summarizes the latest weekly Editor meeting (agenda, slack transcript). This meeting was held in the #core-editor Slack 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.
Gutenberg 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 release. 8.1 is focused on performance improvements, bug 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 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 Site 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 UI 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 block 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 triage 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/plugin 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 trac 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 core 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 make 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 meta 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
