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)

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 Site 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

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.

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.

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

– 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!

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

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

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

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

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.

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

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

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

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.

We have 137 on 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/ team on Gutenberg that can approve PRs. How can we increase the confidence level of these people to actually review and approve PRs?
…Work on more areas = more confident to make a decision regarding those things.
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.
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.

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

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

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, #meeting-notes, #summary