This post summarises the weekly editor chat meeting (agenda here) held on 2021-11-24 14:00 UTC in Slack. Moderated by @get_dave.
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/ 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 releases
- Gutenberg 12.0.0 was released (after the meeting) – thanks to @welcher for leading this one.
- Highlights post will be released on Make blog (versus network, site) soon.
WordPress 5.9 status updates
Updates based on the scope for Site Editing projects
Updates were requested for the key projects:
Native Mobile Team
@antonisme provided the update:
- Added Clipboard Link Suggestion to Image 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. and Buttons block
- Added auto opening of media upload options to new Gallery block
- Only set font sizes for block based themes
- Reverted erroneous native editor package version bumps
- Finalizing GSS Font size, line height and selected text colors.
@get_dave provided the update:
@mciampini provided an update:
ToolsPanel has an improved README and Storybook stories illustrating its usage. This component is used to group related sidebar 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. controls, grouping them and providing a standard UI User interface for showing and hiding them.
- We’ve added an example for adding a chevron icon in the
Item component for certain types of navigation used in Styles.
offset prop now supports RTL languages properly.
@annezazu stepped in to provide an update based on her recent knowledge:
The following items were shared by folks to update us on what work is in progress or where help is needed:
- Update on my end — lots of testing/triaging for 5.9 in GitHub, helped ship the recent /News post highlighting a 5.9 video a crew of us worked on.
- Continued amplifying & responding to the latest FSE outreach call for testing.
- Shared some personal thoughts on why I voted to delay 5.9, and nearly done with draft of Styles user doc (needed for the welcome guide).
- After this next week, I’ll have far more time to focus on documentation and testing efforts so plan to continue to shift attention there (have a presentation due this week about 5.9).
- I’m helping with making the navigation block ready.
- Right now working on giving new menus a name in https://github.com/WordPress/gutenberg/pull/36760.
- I just noticed a few bugs stemming from the complexity, so I want to follow-up with a 2-in-1 PR: simplification and bugfixes.
Get involved in the latest call for testing
- Alan Smodic asked for some insight or guidance on some issues that he and his team have flagged and added comments to. Wondering if these have ever been talked about before or how best we can help to potentially solve.
- Publish datepicker time zone is server time instead of user time: #29306.
- DateTimePicker Time Zone Selection: #31522.
- Timepicker time resets when using AM/PM toggle: #29720.
- @get_dave suggested getting @talldanwp to triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. in the bi-weekly triage meetings.
- @talldanwp suggested following up post 5.9.
- @mciampini said he will flag it to the rest of the components folks,
Normalize Github labels to a single “[Type] Documentation” label
- @mkaz informed us that there is a label in GitHub for “developer docs”, which is intended for issues specific to the developer documentation site.
- He’s not sure the distinction is necessary and the additional label is confusing, as many docs are being labeled with one of the two labels.
- Marcus proposed we remove the “developer docs” label and make sure any issues and PRs that have that label also have the “[Type] Documentation” label.
- Folks in the meeting agreed with this proposal.
Call for input: can we run DB upgrade scripts as part of Gutenberg upgrade process?
- @get_dave raised this Issue whereby meta tags were added to the post content on “Paste”.
- The core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. issue has now been fixed but contributors are asking whether Gutenberg can add a one time operation on upgrade which runs a DB cleanup operation on all posts to remove this erroneous tag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.).
- I’d like to understand whether there is any prior art for achieving such a thing in Gutenberg – any input from @youknowriad or other Core folks would be appreciated.
Thanks to everyone who attended the meeting!