Title: design – Make WordPress Core --- # Tag Archives: design [ ](https://profiles.wordpress.org/bph/) [Birgit Pauli-Haack](https://profiles.wordpress.org/bph/) 9:48 am _on_ December 8, 2022 Tags: [core-editor ( 761 )](https://make.wordpress.org/core/tag/core-editor/), [core-editor-summary ( 185 )](https://make.wordpress.org/core/tag/core-editor-summary/), design, [docs ( 11 )](https://make.wordpress.org/core/tag/docs/), [gutenberg ( 553 )](https://make.wordpress.org/core/tag/gutenberg/), [meeting notes ( 227 )](https://make.wordpress.org/core/tag/meeting-notes/), [meta ( 41 )](https://make.wordpress.org/core/tag/meta/), [summary ( 981 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[Editor chat summary: Wednesday, December 7, 2022](https://make.wordpress.org/core/2022/12/08/editor-chat-summary-wednesday-december-7-2022/)󠁿 This post summarizes weekly editor chat of [Wednesday, December 7, 2022 at 15:00 CET](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Core+Editor+Chat&iso=20221207T15&p1=3903&ah=1) held in SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/). You can view the [full transcript here](https://wordpress.slack.com/archives/C02QB2JS7/p1670421665260829). ## General Announcements and Links * [Gutenberg plugin version 14.7](https://github.com/WordPress/gutenberg/releases/tag/v14.7.0) is released and [available in the Plugin Directory](https://wordpress.org/plugins/gutenberg/)( First 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. release by [@daisyo](https://profiles.wordpress.org/daisyo/)) 👏 * [Core Team Reps for 2023: Submit Your Votes](https://make.wordpress.org/core/2022/12/02/core-team-reps-for-2023-submit-your-votes/) Open until Dec. 16, 2022) * [#meta](https://make.wordpress.org/core/tag/meta/) team is  [Introducing the Block Editor in the Support Forums](https://make.wordpress.org/support/2022/12/introducing-the-block-editor-in-the-support-forums/) *  The [#design](https://make.wordpress.org/core/tag/design/) team shared what they have been working on: [Design Share: Nov 21–Dec 2](https://make.wordpress.org/design/2022/12/05/design-share-nov-21-dec-2/) ## Key project updates * [[[Navigation Block](https://github.com/WordPress/gutenberg/issues/41549) * [Site Editor & Templates](https://github.com/WordPress/gutenberg/issues/41241) * [Building with Patterns](https://github.com/WordPress/gutenberg/issues/38529) * [Design Tools](https://github.com/WordPress/gutenberg/issues/33447) - [Layout Option & Design Tools](https://github.com/WordPress/gutenberg/issues/44720) * [Styles](https://github.com/WordPress/gutenberg/issues/41232) - [Style Engine](https://github.com/WordPress/gutenberg/issues/38167) * [Query Block](https://github.com/WordPress/gutenberg/issues/41405) * [Mobile Team](https://github.com/WordPress/gutenberg/issues/38407) * [Components Team](https://github.com/WordPress/gutenberg/labels/%5BPackage%5D%20Components) * [WebFonts API](https://github.com/WordPress/gutenberg/issues/41479) --- [@annezazu](https://profiles.wordpress.org/annezazu/) shared the [latest **Gutenberg Phase 2** update](https://github.com/WordPress/gutenberg/issues/33094#issuecomment-1338130887). “Here’s a TLDR for any devs looking at where to jump in next: _No development work started (yet)_ * [Navigation Overlay – reference as template part.](https://github.com/WordPress/gutenberg/issues/43852#top) * [Global Styles: Allow saving, importing, exporting, copying from another theme without switching to it](https://github.com/WordPress/gutenberg/issues/45371). _Development work started but help appreciated to move it forward from the PR authors:_ * [Push local block styles to global block style](https://github.com/WordPress/gutenberg/pull/45961) * [Add edit button to template parts, reusable blocks and navigation blocks](https://github.com/WordPress/gutenberg/pull/45465#top)“ --- **[@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/)** shared a ** Webfonts 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. Status** “Still in re-design of the architecture phase. Close to merging the first re-architectural PR. What does it need? * Test it with plugins that are using the current functions to ensure nothing is broken, ie back compatibility is maintained with this phase. * Final code review * Then merge Once merged, it will unblock the last re-architectural task. Once both of those are merged, then performance tasks are unblocked.” --- **[@scruffian](https://profiles.wordpress.org/scruffian/)** posted an update on ** [Navigation block](https://github.com/WordPress/gutenberg/issues/41549#issuecomment-1333735733):** “We now have the basics of the Navigation List View working. It is possible to view, edit and remove navigation items from the inspector controls. Drag and drop also works. The main areas of concern are: 1. When editing an item, can we show the settings tab? 2. Can we animate the opening of 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. settings to make it clear that this is conceptually a “drill-down” operation? These will be the next areas to focus on. Work is happening on this project board: [https://github.com/orgs/WordPress/projects/60/views/1](https://github.com/orgs/WordPress/projects/60/views/1), which should give more detail on progress. This video shows the current state of the project: The issue description will be updated to reflect the current outstanding issues.” --- **[@andrewserong](https://profiles.wordpress.org/andrewserong/) **posted an update on **[Layout options and design tools](https://github.com/WordPress/gutenberg/issues/44720#issuecomment-1340253224)** * Fit/Fill/Fixed size controls have been added to child blocks of Row and Stack now, merged in: [Add Layout controls to children of Flex layout blocks #45364](https://github.com/WordPress/gutenberg/pull/45364) * For consistency with other UIUI User interface controls and to make it easier to make adjustments, a slider has been added alongside the Min Height control: [Min Height: Add height control component with slider #45875](https://github.com/WordPress/gutenberg/pull/45875) * Work continues on exploring fixed/sticky support for container blocks in: [[WIP] Add a Position support (including sticky), decoupled from layout #46142](https://github.com/WordPress/gutenberg/pull/46142). The current exploration now decouples the concept from Layout, as there are potential future use cases for _non_ container blocks (e.g. one day being able to set relative/ absolute, to position images for example). There’s still more discussion/work on this topic and a few blockers to resolve, so updates will happen over in the tracking issue for that feature here: [Fixed Position Header and Footer Template Parts #30121 (comment)](https://github.com/WordPress/gutenberg/issues/30121#issuecomment-1330133950) * A PR has been merged that improves the server-rendering performance of layout by reducing calls to get global settings: [Update: Improve performance of gutenberg_render_layout_support_flag. #4607](https://github.com/WordPress/gutenberg/pull/46074) --- **[@carlosgprim](https://profiles.wordpress.org/carlosgprim/)** posted [updates from the Mobile Team:](https://github.com/WordPress/gutenberg/issues/38407#issuecomment-1340947482) **Main focus** — Upgrade ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. [https://reactjs.org](https://reactjs.org/) Native to version 0.69.x (finished via [these changes](https://github.com/WordPress/gutenberg/pull/45235))  **Recently fixed or improved** * ++ [List/quote: Unwrap inner block when pressing Backspace at start](https://github.com/WordPress/gutenberg/pull/46115) * ++ [Prevent error message from unneccesarily firing when uploading to Gallery block](https://github.com/WordPress/gutenberg/pull/46175) * ++ [Update Heading block E2E test](https://github.com/WordPress/gutenberg/pull/46220) * ++ [Adds Github Action to validate Gradle Wrapper](https://github.com/WordPress/gutenberg/pull/46247) * ++ [Add an inline comment to clarify usage of ‘hard’ limit vs. unbounded query](https://github.com/WordPress/gutenberg/pull/46245) * ++ [Temporarily skip failing copy/paste tests](https://github.com/WordPress/gutenberg/pull/46340) ## Task Coordination [@wildworks](https://profiles.wordpress.org/wildworks/) posted: “Can anyone test the PR regarding shortcuts in Windows? This PR has been approved, and I would like to merge it, but I am the only one testing it…This particular is a call for contributors who work on Windows machines [@wildworks](https://profiles.wordpress.org/wildworks/) is working on [Shortcuts: Add Ctrl+Y for redo to all editor instances on Windows](https://github.com/WordPress/gutenberg/pull/43392)( edited)  [@flexseth](https://profiles.wordpress.org/flexseth/) posted: “**Documentation review:** There are quite a few discrepancies in the ESNext flavor syntax used in Code examples for the documentation (and handbook). Maybe the #docs channel would be the best place to take up discussion on that though? I’ve been wanting to make sure all of the examples are functioning and writing more examples for components.. and to also look to establish a standard for the ES6+ code out there.” [@bph](https://profiles.wordpress.org/bph/) noted: “An issue or more than one should go to the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/) repo for discussion. If you want to work on fixing them, you can review the the  [Guide to Documentation contributions](https://developer.wordpress.org/block-editor/contributors/documentation/)“ ## Open Floor [@flexseth](https://profiles.wordpress.org/flexseth/) asked: “Do you know where first time contributors can submit to be listed as contributors for this year? In the contributor numbers for State of the WordState of the Word This is the annual report given by Matt Mullenweg, founder of WordPress at WordCamp US. It looks at what we’ve done, what we’re doing, and the future of WordPress. [https://wordpress.tv/tag/state-of-the-word/](https://wordpress.tv/tag/state-of-the-word/)., in one of the Hallway Hangouts a call for contributors was mentioned I think.” [@bph](https://profiles.wordpress.org/bph/): noted: “AFAIK the contributor numbers in SOTW are always release related. 5.9 6.0 6.1. Each team has their own way of acknowledging contributions. 6.1 was the last release for the year. Every Gutenberg plugin release has a list of contributors, too. [Example](https://github.com/WordPress/gutenberg/releases/tag/v14.7.0-rc.1), including first contributors” Well after having used WordPress for over 10 years, I can say the direction of the project is the best I’ve seen. Good work all! — [@flexseth](https://profiles.wordpress.org/flexseth/) _Props to [@paaljoachim](https://profiles.wordpress.org/paaljoachim/) for his review._ [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#core-editor-summary](https://make.wordpress.org/core/tag/core-editor-summary/), [#gutenberg](https://make.wordpress.org/core/tag/gutenberg/), [#meeting-notes](https://make.wordpress.org/core/tag/meeting-notes/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/danfarrow/) [Dan Farrow](https://profiles.wordpress.org/danfarrow/) 10:29 am _on_ January 19, 2021 Tags: [core-css ( 192 )](https://make.wordpress.org/core/tag/core-css/), design, [summary ( 981 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[CSS Chat Summary: 14 January 2021](https://make.wordpress.org/core/2021/01/19/css-chat-summary-14-january-2021/)󠁿 [The meeting took place here on Slack](https://wordpress.slack.com/archives/CQ7V4966Q/p1610661750004900). [@notlaura](https://profiles.wordpress.org/notlaura/) facilitated and [@danfarrow](https://profiles.wordpress.org/danfarrow/) wrote up these notes. ## Housekeeping [@notlaura](https://profiles.wordpress.org/notlaura/) pointed out that we missed a scheduled 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. scrub today which started a short discussion about how to make them consistent. The outcome was that the lead for each scrub should be established the week before which [@notlaura](https://profiles.wordpress.org/notlaura/) will check in with to make sure the scrub can go ahead as planned. If necessary an upcoming scrub can be skipped and removed from the meetings calendar. ## CSSCSS Cascading Style Sheets. Audit (󠀁[#49582](https://core.trac.wordpress.org/ticket/49582)󠁿) [@danfarrow](https://profiles.wordpress.org/danfarrow/) reported having made a PR to reorganise the audit tool’s HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. report directory structure with the goal of simplification. He also moved the report stylesheet into `/src` and added a command to copy it into `/public`, which means that files inside `/public` need no longer be edited manually. [@notlaura](https://profiles.wordpress.org/notlaura/) noted that the property values reports issue still needs to be resolved. She linked to [this related github issue](https://github.com/ryelle/css-audit/issues/7) as a place to discuss & keep track of ideas. ## Color Scheming (󠀁[#49999](https://core.trac.wordpress.org/ticket/49999)󠁿) & Visual Regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or 󠀁[blockers](https://make.wordpress.org/core/tag/design/?output_format=md#blocker)󠁿. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. Testing (󠀁[#49606](https://core.trac.wordpress.org/ticket/49606)󠁿) [@isabel_brison](https://profiles.wordpress.org/isabel_brison/) shared her [PR to add visual regression tests for wp-admin pages](https://github.com/WordPress/wordpress-develop/pull/209) which is now ready for review/testing. This will be a very useful addition to the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. testing suite, particularly for CSS. [@ryelle](https://profiles.wordpress.org/ryelle/) reported that she [shared her reduced colours branch in dev chat](https://wordpress.slack.com/archives/C02RQBWTW/p1610571436086100) and is hoping for more feedback, from design especially. To encourage this she also added `needs-testing` to [#49999](https://core.trac.wordpress.org/ticket/49999). [The branch is available here](https://github.com/WordPress/wordpress-develop/pull/818)– please have a look. ## Open floor & CSS link share [@isabel_brison](https://profiles.wordpress.org/isabel_brison/) shared a link to [Web Directions’ call ](http://Open%20floor%20&%20CSS%20link%20share)[for speakers](https://webdirections.org/hover/index.php#speakforus) for their upcoming CSS conference. The deadline is the end of this month so get those proposals in! [@notlaura](https://profiles.wordpress.org/notlaura/) shared a [useful reference for logical CSS functions `min`, `max` and `clamp`](https://web.dev/min-max-clamp/). [@danfarrow](https://profiles.wordpress.org/danfarrow/) shared a piece of CSS esoteria: [an ugly hack for rounding values down with two decimal places](https://stackoverflow.com/questions/37754542/css-calc-round-down-with-two-decimal-cases/64921523#64921523). This prompted wry speculation on the usefulness of `0.01px` precision, and with that the meeting concluded. Thanks everyone! [#core-css](https://make.wordpress.org/core/tag/core-css/), [#design](https://make.wordpress.org/core/tag/design/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/danfarrow/) [Dan Farrow](https://profiles.wordpress.org/danfarrow/) 11:41 pm _on_ October 16, 2020 Tags: [core-css ( 192 )](https://make.wordpress.org/core/tag/core-css/), design, [summary ( 981 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[CSS Chat Summary: 15 October 2020](https://make.wordpress.org/core/2020/10/16/css-chat-summary-15-october-2020/)󠁿 [Full meeting transcript here on Slack](https://wordpress.slack.com/archives/CQ7V4966Q/p1602795816267000). [@notlaura](https://profiles.wordpress.org/notlaura/) facilitated the meeting. ## Housekeeping Reminder that [@kburgoine](https://profiles.wordpress.org/kburgoine/) will be leading the biweekly coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSSCSS Cascading Style Sheets. 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. scrub next Thursday, October 22, one hour before the CSS Chat meeting. ## CSS Audit (󠀁[#49582](https://core.trac.wordpress.org/ticket/49582)󠁿) [@ryelle](https://profiles.wordpress.org/ryelle/) reported her progress of having [written up an issue about adding configuration file support](https://github.com/ryelle/css-audit/issues/8) to her CSS Audit tool, to which [@notlaura](https://profiles.wordpress.org/notlaura/) reported having been prompted by the issue to [begin work on the feature](https://github.com/ryelle/css-audit/pull/9)! The generated reports are now accessible as 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 by the repository owner. [https://github.com/](https://github.com/) pages ([here for example](https://ryelle.github.io/css-audit/public/wp-admin)). [@ryelle](https://profiles.wordpress.org/ryelle/) observed that eventually this tool should be migrated to the WordPress github repos. [@notlaura](https://profiles.wordpress.org/notlaura/) mentioned that a comment about report generation should be added to the TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker., for community reference and put a call out for a volunteer to do this, specifying: > the key items to include in a comment are the link to the generated report ([https://ryelle.github.io/css-audit/public/wp-admin](https://ryelle.github.io/css-audit/public/wp-admin)) > and the next steps, which are to complete the data (missing property values) and > to style the template ## Color Scheming (󠀁[#49999](https://core.trac.wordpress.org/ticket/49999)󠁿) [@ryelle](https://profiles.wordpress.org/ryelle/) reported that she has kept her [reduced-color branch testing site](https://dev-admin-colors.pantheonsite.io/wp-admin/) up-to-date with WordPress trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running" trunk", then you are on the latest revision.. There followed a short discussion about the pros and cons of proposing to merge the 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". into the 5.6 betaBeta A pre- release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process.. [@garrett-eclipse](https://profiles.wordpress.org/garrett-eclipse/) suggested seeking a champion from [#design](https://make.wordpress.org/core/tag/design/), otherwise punting it to 5.7, which, [@ryelle](https://profiles.wordpress.org/ryelle/) observed, would allow us to focus on bug-scrubbing & [Twenty Twenty One](https://github.com/WordPress/twentytwentyone/) issues over the coming weeks. ## CSS links share + Open floor [@danfarrow](https://profiles.wordpress.org/danfarrow/) (me!) shared a link to a portfolio site [ichimnetz.com](https://ichimnetz.com) which has a quirky “_adjust CSS_” slider feature which demonstrates the effect of using more or less CSS. [@danfarrow](https://profiles.wordpress.org/danfarrow/) also shared an informative recent [CSS Tricks article about media queries](https://css-tricks.com/a-complete-guide-to-css-media-queries/) which includes a reference to a browser feature _forced colors mode_: > Some browsers will limit the number of available colors that can be used to render > styles. This is called [“forced colors mode”](https://www.w3.org/TR/css-color-adjust-1/#forced-colors-mode) > and, if enabled in the browser settings, the user can choose a limited set of > colors to use on a page. As a result, the user is able to define color combinations > and contrasts that make content more comfortable to read. And, with that, the meeting was concluded. Thanks everybody! [#core-css](https://make.wordpress.org/core/tag/core-css/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/danfarrow/) [Dan Farrow](https://profiles.wordpress.org/danfarrow/) 10:21 am _on_ October 9, 2020 Tags: [accessibility ( 59 )](https://make.wordpress.org/core/tag/accessibility/), [core-css ( 192 )](https://make.wordpress.org/core/tag/core-css/), design, [summary ( 981 )](https://make.wordpress.org/core/tag/summary/) # 󠀁[CSS Chat Summary: 08 October 2020](https://make.wordpress.org/core/2020/10/09/css-chat-summary-08-october-2020/)󠁿 [Full meeting transcript here on Slack](https://wordpress.slack.com/archives/CQ7V4966Q/p1602190992213700). [@notlaura](https://profiles.wordpress.org/notlaura/) facilitated the meeting. ## Housekeeping [@notlaura](https://profiles.wordpress.org/notlaura/) reminded attendees that she will be unavailable on 22 October and needs somebody to step in and run the meeting. If you’re up for it please let her know! ## CSSCSS Cascading Style Sheets. Audit (󠀁[#49582](https://core.trac.wordpress.org/ticket/49582)󠁿) [@notlaura](https://profiles.wordpress.org/notlaura/) reported progress on [her PR to add the HTML report](https://github.com/ryelle/css-audit/pull/4) to [@ryelle](https://profiles.wordpress.org/ryelle/)‘s super [CSS Audit tool](https://github.com/ryelle/css-audit/) which now adds support for a `--format=html` command line option. There is a remaining issue with the property-values audit, and contribution is still needed towards [improving the design and info formatting](https://laras126.github.io/css-audit/public/wp-admin.html). [@notlaura](https://profiles.wordpress.org/notlaura/) also mentioned [an issue she added about the need for property-value audit groupings](https://github.com/ryelle/css-audit/issues/7). A short discussion about possible solutions followed, which gravitated towards adding support for `.json` config files. [@ryelle](https://profiles.wordpress.org/ryelle/) offered to write up an issue to outline the format she envisages for discussion in 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 by the repository owner. [https://github.com/](https://github.com/). [@notlaura](https://profiles.wordpress.org/notlaura/) clarified the approaching milestones of merging her PR, updating the tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker., and enabling more progress on styling the report which [@danfarrow](https://profiles.wordpress.org/danfarrow/)( me!) has started contributing to. [@notlaura](https://profiles.wordpress.org/notlaura/) pointed out a failing test(` Colors › should ignore colors in non-color properties`) which [@ryelle](https://profiles.wordpress.org/ryelle/) confirmed she had left as an aide-mémoire for herself to fix the associated issue. [@ryelle](https://profiles.wordpress.org/ryelle/) suggested that this issue might be a good self-contained task for a new contributor to tackle. ## Color Scheming (󠀁[#49999](https://core.trac.wordpress.org/ticket/49999)󠁿) [@ryelle](https://profiles.wordpress.org/ryelle/) reminded us of her demo site where people can appraise the reduced-colors testing tool – [details in this Slack message](https://wordpress.slack.com/archives/CQ7V4966Q/p1601587917136600). Some issues have already been added to [the github repo](https://github.com/ryelle/wp-core-color-list/issues) but wider testing is required. The plan is to post in [#design](https://make.wordpress.org/core/tag/design/) and [#accessibility](https://make.wordpress.org/core/tag/accessibility/) with info on how to access the tool, how to submit new issues, and prompts to help fix the issues. [@notlaura](https://profiles.wordpress.org/notlaura/) put out a call for somebody to help with this small task, and offered her assistance to clarify what’s required& to review the message before it’s posted. [@ryelle](https://profiles.wordpress.org/ryelle/) added that she can still write the post if nobody else volunteers (although she had mentioned earlier in the meeting that this month is super busy for her so please consider helping out!) ## CSS links share + Open floor [@notlaura](https://profiles.wordpress.org/notlaura/) shared a link to [this CSS-Tricks article about the widening responsibility of front-end developers](https://css-tricks.com/the-widening-responsibility-for-front-end-developers/). [@Andrew](https://profiles.wordpress.org/andrew/) Joyce added a recommendation for an earlier article by the author on the same theme, [The Great Divide](https://css-tricks.com/the-great-divide/). We reflected about a time when writing CSS involved just writing CSS, and on that poignant note the meeting was closed. Thanks to everybody who attended! [#core-css](https://make.wordpress.org/core/tag/core-css/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/laurora/) [Laura Nelson](https://profiles.wordpress.org/laurora/) 12:39 pm _on_ September 17, 2020 Tags: [5.6 ( 85 )](https://make.wordpress.org/core/tag/5-6/), design, [dev chat ( 932 )](https://make.wordpress.org/core/tag/dev-chat/), [summary ( 981 )](https://make.wordpress.org/core/tag/summary/), [sustainability ( 3 )](https://make.wordpress.org/core/tag/sustainability/)    # 󠀁[Dev Chat Summary: September 16 2020](https://make.wordpress.org/core/2020/09/17/dev-chat-summary-september-16-2020/)󠁿 Greetings! Here’s what happened in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev chat on Wednesday, September 16, 2020, 05:00 UTC and Wednesday, September 16, 2020, 20:00 UTC, following this [agenda](https://make.wordpress.org/core/2020/09/15/dev-chat-agenda-september-16th-2020/). **05:00 UTC core dev chat** [@thewebprincess](https://profiles.wordpress.org/thewebprincess/) facilitated the meeting and took notes. [Find the full Slack archive here](https://wordpress.slack.com/archives/C02RQBWTW/p1600232433154700). **20:00 UTC core dev chat** [@thelmachido](https://profiles.wordpress.org/thelmachido/) facilitated the meeting and [@laurora](https://profiles.wordpress.org/laurora/) took notes. [The full Slack archive can be viewed here](https://wordpress.slack.com/archives/C02RQBWTW/p1600286453352500). Both groups followed this agenda: [https://make.wordpress.org/core/2020/09/15/dev-chat-agenda-september-16th-2020/](https://make.wordpress.org/core/2020/09/15/dev-chat-agenda-september-16th-2020/) ## Announcements [@pbiron](https://profiles.wordpress.org/pbiron/) shared that there will be an Upgrade/ Install component 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. scrub [today (September 17) at 18:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200917T1800). Everyone is welcome to attend! More info can be found here: [https://make.wordpress.org/core/2020/09/16/upgrade-install-component-bug-scrub-for-wordpress-5-6](https://make.wordpress.org/core/2020/09/16/upgrade-install-component-bug-scrub-for-wordpress-5-6) [@flixos90](https://profiles.wordpress.org/flixos90/) would like more thoughts and feedback on a proposal to enhance image preview: [https://make.wordpress.org/core/2020/09/15/enhancing-image-preview-core-proposal/](https://make.wordpress.org/core/2020/09/15/enhancing-image-preview-core-proposal/). Please leave your comments on the post. Due to the speed WP5.6 is moving at, and some unexpected items (oEmbed & PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 8.0), [@chanthaboune](https://profiles.wordpress.org/chanthaboune/) has organized a meeting with the 5.6 release squad to discuss. This will take place today (September 17) at 20:00 UTC. [@helen](https://profiles.wordpress.org/helen/) proposed streaming the meeting and the squad is still deciding whether to do this. In any case, notes will be taken and published. ## Highlighted Posts A bug scrub was held before the 20:00 UTC dev chat: [https://make.wordpress.org/core/2020/09/15/i18n-component-bug-scrub-for-wordpress-5-6/](https://make.wordpress.org/core/2020/09/15/i18n-component-bug-scrub-for-wordpress-5-6/). [@helen ](https://profiles.wordpress.org/helen/)explained that updates were left on tickets reviewed from the TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. reports, and [@justinahinon](https://profiles.wordpress.org/justinahinon/) added that progress has been made on all i18ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see [localization](https://make.wordpress.org/core/tag/design/?output_format=md#l10n). Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill. 5.6 slated tickets. ## Updates from Component Maintainers/Focus Leads **Upgrade/Install** Will explore adding some UIUI User interface elements to manage email notifications on 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. and theme auto-updates.[@audrasjb](https://profiles.wordpress.org/audrasjb/) highlighted [the bug scrub](https://make.wordpress.org/core/2020/09/16/upgrade-install-component-bug-scrub-for-wordpress-5-6) taking place today (September 17) at 18:00 UTC. **Privacy** [@carike](https://profiles.wordpress.org/carike/) reported: “We have been receiving a lot of feedback, for which we are very grateful. Will update tickets over the next few days with more details on the proposed application design.”**Comments** [@imath](https://profiles.wordpress.org/imath/) requested a second opinion on ticketticket Created for both bug reports and feature development on the bug tracker. [#50521](https://core.trac.wordpress.org/ticket/50521), and also shared that he’s been working with [@dshanske](https://profiles.wordpress.org/dshanske/) on writing [a kick-off post](https://wordpress.slack.com/files/T024MFP4J/F019KDHDSQG?origin_team=T024MFP4J&origin_channel=C165PN7EX) to launch a project to develop the WP Comment Types feature[ from a plugin](https://github.com/imath/wp-comment-types). They would like guidance on how to make this post public on [make.wordpress.org/core](https://make.wordpress.org/core). **Site Health** [@clorith](https://profiles.wordpress.org/clorith/) shared that they’re doing some multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also **network**, **blog**, **site** work for this cycle and besides that general bug watching. **(Classic) Menus and Widgets** [@audrasjb](https://profiles.wordpress.org/audrasjb/) reviewed some tickets with a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a **diff**. A patch can be _applied_ to a codebase for testing. and put a few of them into milestone 5.6. **Build/Test Tools** [@johnbillion](https://profiles.wordpress.org/johnbillion/) noted the continued progress on PHP 8 compatibility. **Design** [@karmatosed](https://profiles.wordpress.org/karmatosed/) shared “A little note if any components/focuses want design help this release just pop a keyword on or hop into [#design](https://make.wordpress.org/core/tag/design/). There’s an awesome group of people ready to help this release so great to catch all those little tickets and things.” ## Open Floor [@bduclos](https://profiles.wordpress.org/bduclos/) asked if there are any mockups of the new Twenty Twenty One theme available, and will the project be on 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 by the repository owner. [https://github.com/](https://github.com/). [@melchoyce](https://profiles.wordpress.org/melchoyce/) will be sharing more details about this in a post, due to be published soon. There was [a lot of discussion](https://wordpress.slack.com/archives/C02RQBWTW/p1600288405415800) regarding the announcement from Facebook & Instagram that they’ll be dropping unauthenticated oEmbed support; mainly around timing and how to communicate this update to WordPress users. It was noted that the removal of those blocks in v9.0 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/](https://wordpress.org/gutenberg/) is complete– if need be it can be reverted. [@whyisjake](https://profiles.wordpress.org/whyisjake/) volunteered to put a post together so that the conversation could be continued. There was an update in response to privacy/data deletion request in issue [#43437](https://core.trac.wordpress.org/ticket/43437). It is not anticipated that there will much of a change to the current tools. Concluding with it is not foreseen that there will be any significant breaking type changes for the ticket. A proposal was put forward to create a [#sustainability](https://make.wordpress.org/core/tag/sustainability/) SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) channel for those interested in improving the sustainability of WP, through performance enhancements and more. [@isabel_brison](https://profiles.wordpress.org/isabel_brison/) is putting together a blogblog (versus network, site) post to discuss further. [@webcommsat ](https://profiles.wordpress.org/webcommsat/) shared this post: [https://make.wordpress.org/marketing/2020/06/01/sustainability-working-group-update/](https://make.wordpress.org/marketing/2020/06/01/sustainability-working-group-update/) which details some of the work that has been done in this area so far. [@webcommsat](https://profiles.wordpress.org/webcommsat/) highlighted that a week celebrating WordPress translationtranslation The process( or result) of changing text, words, and display formatting to support another language. Also see [localization](https://make.wordpress.org/core/tag/design/?output_format=md#l10n), [internationalization](https://make.wordpress.org/core/tag/design/?output_format=md#i18n). will take place from 28 September to 4 October 2020. If you have any ideas on how the translation process for WordPress releases could be promoted, please leave comments on this post: [https://make.wordpress.org/polyglots/2020/09/09/lets-celebrate-international-translation-day-together/](https://make.wordpress.org/polyglots/2020/09/09/lets-celebrate-international-translation-day-together/). ## Next Dev Chat meetings The next meetings will take place on [Wednesday, September 23, 2020, 05:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Dev+Chat+AM&iso=20200923T05&p1=1440&ah=1) and [Wednesday, September 23, 2020, 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Dev+Chat+PM&iso=20200923T20&p1=1440&ah=1) in the [#core](https://wordpress.slack.com/messages/#core/) Slack channel. Please feel free to drop in with any updates or questions. [#5-5-1](https://make.wordpress.org/core/tag/5-5-1/), [#5-5-2](https://make.wordpress.org/core/tag/5-5-2/), [#5-6](https://make.wordpress.org/core/tag/5-6/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#summary](https://make.wordpress.org/core/tag/summary/) [#5-6](https://make.wordpress.org/core/tag/5-6/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/annezazu/) [annezazu](https://profiles.wordpress.org/annezazu/) 5:19 pm _on_ May 13, 2020 Tags: [core-editor ( 761 )](https://make.wordpress.org/core/tag/core-editor/), design, [editor ( 223 )](https://make.wordpress.org/core/tag/editor/), [gutenberg ( 553 )](https://make.wordpress.org/core/tag/gutenberg/), [meeting notes ( 227 )](https://make.wordpress.org/core/tag/meeting-notes/)    # 󠀁[Editor Chat Summary: 13th May, 2020](https://make.wordpress.org/core/2020/05/13/editor-chat-summary-13th-may-2020/)󠁿 This post summarizes the latest weekly Editor meeting ([age](https://make.wordpress.org/core/2020/05/12/editor-chat-agenda-13-may-2020/) [n](https://make.wordpress.org/core/2020/05/12/editor-chat-agenda-13-may-2020/)[da](https://make.wordpress.org/core/2020/05/12/editor-chat-agenda-13-may-2020/), [slack transcript](https://wordpress.slack.com/archives/C02QB2JS7/p1589378401128000)). This meeting was held in the [#core-editor](https://wordpress.slack.com/messages/C02QB2JS7) SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) channel on [Wednesday, May 13, 2020,14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200513T1400) and was moderated by [@andraganescu](https://profiles.wordpress.org/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/](https://wordpress.org/gutenberg/)󠁿 8.1.0** [Gutenberg 8.1 RC](https://github.com/WordPress/gutenberg/releases/tag/v8.1.0-rc.1) was released on May 11th and is on track for a final release. 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](https://make.wordpress.org/core/2020/05/06/whats-next-in-gutenberg-may/). [@andraganescu](https://profiles.wordpress.org/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 Site Editing (FSE) is a major focus right now and can be followed [here](https://github.com/WordPress/gutenberg/issues?q=is%3Aissue+is%3Aopen+FSE) with the overall plan shared [here](https://github.com/WordPress/gutenberg/issues/13113). ## **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](https://profiles.wordpress.org/nosolosw/) * Main focus has been “Global Styles”. Currently, iterating on some [framework tasks](https://github.com/WordPress/gutenberg/pull/20290) that need to be to unlock before resuming work on the UIUI User interface. This will be the focus for this week too. [@aduth](https://profiles.wordpress.org/aduth/) * Working on some documentation and framework-level improvements, largely summarized in [this slack convo](https://wordpress.slack.com/archives/C5UNMSU4R/p1589295011130100). * 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](https://profiles.wordpress.org/youknowriad/) * Did two zoom chats to help contributors (one in [#core-editor](https://make.wordpress.org/core/tag/core-editor/), one in French WordPress slack). * Trying to land categories support for patterns. [@nrqsnchz](https://profiles.wordpress.org/nrqsnchz/) * Fighting some test failures, but yesterday was able to merge [another block pattern](https://github.com/WordPress/gutenberg/pull/21130). * Continued to work on [the new Welcome Guide](https://github.com/WordPress/gutenberg/pull/21847). * Proposed the creation of [a ‘Whats new’ section for the block editor](https://github.com/WordPress/gutenberg/issues/22241). * Planning to jump into Full Site Editing once done working on the Welcome Guide. [@retrofox](https://profiles.wordpress.org/retrofox/) * Made progress in the [Tips approach](https://github.com/WordPress/gutenberg/pull/22109). It’s now possible to register tips defining the scope, descriptions, and other parameters. [@earnjam](https://profiles.wordpress.org/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](https://profiles.wordpress.org/mapk/) * Spent time triaging issues. * Search block enhancements. [@itsjonq](https://profiles.wordpress.org/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/](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](https://profiles.wordpress.org/vindl/) * Working on allowing extensions/replacements of editor close button which is part of [this issue](https://github.com/WordPress/gutenberg/issues/20929). 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](https://github.com/WordPress/gutenberg/issues/21245). [@michael-arestad](https://profiles.wordpress.org/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](https://make.wordpress.org/core/tag/design/). [@sageshilling](https://profiles.wordpress.org/sageshilling/) * Working on the image and gallery blocks. [@andraganescu](https://profiles.wordpress.org/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](https://profiles.wordpress.org/zieladam/) Working on the experimental navigation screen, in particular: * UI Improvements (#[22311](https://github.com/WordPress/gutenberg/pull/22311) # [22228](https://github.com/WordPress/gutenberg/pull/22228) #[22227](https://github.com/WordPress/gutenberg/pull/22227) and a few more). * [Exploring saving the entire navigation](https://github.com/WordPress/gutenberg/pull/22148) using one request instead of one request per menu item. ## **Open floor** Do we instead of listing packages and versions, need to list components and versions? Raised by [@paaljoachim](https://profiles.wordpress.org/paaljoachim/). This discussion point was raised in reaction to a comment from [@clorith](https://profiles.wordpress.org/clorith/) in [this trac ticket](https://core.trac.wordpress.org/ticket/48329#comment:16%60) 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](https://core.trac.wordpress.org/ticket/48329#comment:16)! Do we need to apply a max height for the style placeholders in the inspector? Raised by [@munirkamal](https://profiles.wordpress.org/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](https://profiles.wordpress.org/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](https://github.com/WordPress/gutenberg/issues/22315) 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](https://profiles.wordpress.org/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](https://profiles.wordpress.org/youknowriad/) suggested meeting more around 15UTC/16UTC but wants to hear from others. Tied to this, [@aduth](https://profiles.wordpress.org/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](https://profiles.wordpress.org/sageshilling/). This came up as part of work done on the image and gallery blocks ([full context here](https://wordpress.slack.com/archives/C02QB2JS7/p1589379582160500)). 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](https://profiles.wordpress.org/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](https://make.wordpress.org/core/tag/meeting-notes/), [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#editor](https://make.wordpress.org/core/tag/editor/), [#gutenberg](https://make.wordpress.org/core/tag/gutenberg/) [ ](https://profiles.wordpress.org/gziolo/) [Greg Ziółkowski](https://profiles.wordpress.org/gziolo/) 1:36 pm _on_ June 12, 2019 Tags: [core-js ( 131 )](https://make.wordpress.org/core/tag/core-js/), design, [javascript ( 130 )](https://make.wordpress.org/core/tag/javascript/)    # 󠀁[JavaScript Chat Summary, June 11, 2019](https://make.wordpress.org/core/2019/06/12/javascript-chat-summary-june-11-2019/)󠁿 Below is a summary of the discussion from this week’s 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](https://www.javascript.com/) chat( [agenda](https://docs.google.com/document/d/1EDmABaak5xmGS1E5LwBDeDoJTZ7TigiP1mOb7HfDSKE/edit), [Slack Transcript](https://wordpress.slack.com/archives/C5UNMSU4R/p1560261764009400)) Have a topic for discussion for the next meeting? Leave a suggested edit on [next week’s agenda](https://docs.google.com/document/d/1AAaFOq6dIs8GAsILWHvN50tJJ0kyJ6PFN86DQhmWgP4/edit). ## Component Props Documentation _[Slack Conversation](https://wordpress.slack.com/archives/C5UNMSU4R/p1560261826011700)_ _Question:_ How can we eliminate human error from components documentation? _Context:_ [@dsifford](https://profiles.wordpress.org/dsifford/)‘s recent [pull requests](https://github.com/WordPress/gutenberg/pulls?utf8=%E2%9C%93&q=is%3Apr+author%3Adsifford) can sort of speak for themselves so far as demonstrating the current inaccuracies in components documentation. He’s discovered them while working on type definitions added to [DefinitelyTyped](https://github.com/DefinitelyTyped/DefinitelyTyped) for`@ wordpress/*` packages and he’s tracking progress on [Trello board](https://trello.com/b/Fk0IrjjM/wordpress-type-definitions). If anyone is interested in helping the effort let us know. Options discussed: * Improve current JSDoc documentation. * Add support for `React.PropTypes`. * Introduce TypeScript. Action items: * Explore [type checking JavaScript Files with TypeScript](https://www.typescriptlang.org/docs/handbook/type-checking-javascript-files.html) which might require some work to improve JSDoc or at least have exceptions in the short-term. * Find a way we can automate the documentation for components. ## Open Floor _[Slack Conversation](https://wordpress.slack.com/archives/C5UNMSU4R/p1560263244048900)_ Some of us are traveling to WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. [Learn more](https://central.wordcamp.org/about/). Europe next week, so we agreed to cancel the meeting planned for next Tuesday and pick up again on **June, 25th**. [#core-js](https://make.wordpress.org/core/tag/core-js/), [#design](https://make.wordpress.org/core/tag/design/), [#javascript](https://make.wordpress.org/core/tag/javascript/) [ ](https://profiles.wordpress.org/ajitbohra/) [Ajit Bohra](https://profiles.wordpress.org/ajitbohra/) 6:21 pm _on_ June 11, 2019 Tags: [core-editor ( 761 )](https://make.wordpress.org/core/tag/core-editor/), [core-editor-summary ( 185 )](https://make.wordpress.org/core/tag/core-editor-summary/), design    # 󠀁[Editor chat summary: June 5th](https://make.wordpress.org/core/2019/06/11/editor-chat-summary-june-5th/)󠁿 This post summarizes the latest weekly Editor meeting, held in the[ #core-editor](https://make.wordpress.org/core/tag/core-editor/) SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) channel, on[ Wednesday, June 05, 2019, 13:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20190605T1300). ## Announcement [@danr](https://profiles.wordpress.org/danr/), [@andraganescu](https://profiles.wordpress.org/andraganescu/) and [@noisysocks](https://profiles.wordpress.org/noisysocks/) will be starting up a new contributor triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. meeting in [#core-editor](https://make.wordpress.org/core/tag/core-editor/) for APAC timezone. First meeting is planned on Thursday 13th July at 6AM UTC and then every two weeks. ## Tasks Coordination * [@nerrad](https://profiles.wordpress.org/nerrad/) merged [useDispatch](https://github.com/WordPress/gutenberg/pull/15896) and is picking up [15444](https://github.com/WordPress/gutenberg/pull/15444). * [@kjell](https://profiles.wordpress.org/kjell/) is modifying small details to the Group/Ungroup [16001](https://github.com/WordPress/gutenberg/pull/16001), [16002](https://github.com/WordPress/gutenberg/pull/16002). Also looking into some a11yAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology( for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) zoom issues [15984](https://github.com/WordPress/gutenberg/pull/15984), [15973](https://github.com/WordPress/gutenberg/pull/15973) * [@getdave](https://profiles.wordpress.org/getdave/) merged 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. [Group/Ungroup](https://github.com/WordPress/gutenberg/pull/14908) PR . * [@aduth](https://profiles.wordpress.org/aduth/) exploring columns drag resizing [15927](https://github.com/WordPress/gutenberg/pull/15927). Also improved build time and further working on follow-up task to make them faster [15230](https://github.com/WordPress/gutenberg/pull/15230), [15967](https://github.com/WordPress/gutenberg/issues/15967). * [@mapk](https://profiles.wordpress.org/mapk/) is tweaking Spacer block, reviewing widgets-block screen, and helping with Image edit flows. * [@karmatosed](https://profiles.wordpress.org/karmatosed/) has been leading wonderful triage sessions in [#design](https://make.wordpress.org/core/tag/design/). * [@gziolo](https://profiles.wordpress.org/gziolo/) [refactored](https://github.com/WordPress/gutenberg/pull/14843) dropdown menus aligning BlockSettingsMenu and MoreMenu and they’re accessible too. [Bringing](https://github.com/WordPress/gutenberg/pull/15964) consistency to block toolbar. Possibly merge Block Registration RFC soon. And small tweaks to `@wordpress/scripts` package. * [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/) working on updates to [widgets-block screen](https://github.com/WordPress/gutenberg/issues/13204#issuecomment-499078467). Also some triage. And helping guide the [Nav block](https://github.com/WordPress/gutenberg/pull/14856) PR. * [@Andrei](https://profiles.wordpress.org/andrei/) Draganescu still working on Image edit flows and [exploring](https://github.com/WordPress/gutenberg/issues/15851) how to add the block inserter to post title. * [@joen](https://profiles.wordpress.org/joen/) merged the [Clickthrough](https://github.com/WordPress/gutenberg/pull/15537) PR. ## Open Floor * [@manooweb](https://profiles.wordpress.org/manooweb/) asked about security in development with ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. [https://reactjs.org](https://reactjs.org/), updating docs to cover the same was agreed upon. * [@soean](https://profiles.wordpress.org/soean/) asked about agenda for Contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of [https://make.wordpress.org/](https://make.wordpress.org/) There are many teams that people can participate in, each with a different focus. [https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/](https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/) at WCEU. * [@gziolo](https://profiles.wordpress.org/gziolo/) shared rough agenda for Contributors day at WCEU: - onboard a few new contributors, collect the feedback and work on documentation improvements to make the process smoother. - go through the list of open issues trying to identify tasks which would be an excellent fit for new contributors. - explore how we could automate the detection of pull requests sent by new contributors to ensure they get enough support from others. - triage issues looking for those which can be closed because they are no longer relevant, are duplicates or should be moved somewhere else. - triage pull requests seeking for those which can be closed, need to be updated or can be merged after short review and testing session. _**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.**_ The meeting archive is [here](https://wordpress.slack.com/archives/C02QB2JS7/p1559739637030900). The agenda for the next meeting is [here](https://docs.google.com/document/d/1OZunmOD3s6i6mec0mDKtgX5npy7OP-FhoBqswkK94J0/edit), please add anything you want to discuss. [#meeting-notes](https://make.wordpress.org/core/tag/agenda/), [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#editor](https://make.wordpress.org/core/tag/editor/), [#gutenberg](https://make.wordpress.org/core/tag/gutenberg/) [#core-editor-summary](https://make.wordpress.org/core/tag/core-editor-summary/) [ ](https://profiles.wordpress.org/aduth/) [Andrew Duthie](https://profiles.wordpress.org/aduth/) 4:16 pm _on_ June 4, 2019 Tags: [core-js ( 131 )](https://make.wordpress.org/core/tag/core-js/), design, [javascript ( 130 )](https://make.wordpress.org/core/tag/javascript/)    # 󠀁[JavaScript Chat Summary, June 4, 2019](https://make.wordpress.org/core/2019/06/04/javascript-chat-summary-june-4-2018/)󠁿 Below is a summary of the discussion from this week’s 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](https://www.javascript.com/) chat( [agenda](https://docs.google.com/document/d/1aJMMuf5uBYJCchVpKCfnDyjA6EqNeK7McsQNAcheKz4/edit), [Slack Transcript](https://wordpress.slack.com/archives/C5UNMSU4R/p1559656828000100)) Have a topic for discussion for the next meeting? Leave a suggested edit on [next week’s agenda](https://docs.google.com/document/d/1EDmABaak5xmGS1E5LwBDeDoJTZ7TigiP1mOb7HfDSKE/edit). ## Agenda: June 18 Meeting Planning _[Slack Conversation](https://wordpress.slack.com/archives/C5UNMSU4R/p1559656934001300)_ Neither [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/) nor [@aduth](https://profiles.wordpress.org/aduth/) will be able to host the meeting scheduled for June 18. Is there anyone willing to host that day, or should we plan to cancel the meeting for that week? This is the Tuesday before WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. [Learn more](https://central.wordcamp.org/about/). Europe, so there may be lower- than-usual attendance. **Decision:** There will be no JavaScript meeting on June 18. ## Agenda: Dependabot Follow-up _[Slack Conversation](https://wordpress.slack.com/archives/C5UNMSU4R/p1559657157005800)_ Discussed in [last week’s meeting](https://make.wordpress.org/core/2019/05/29/javascript-chat-summary-may-28th-2019/), a bot has been submitting security update pull requests to the [gutenberg-examples repository](https://github.com/WordPress/gutenberg-examples). It was discovered that this was a default behavior from [GitHub’s acquisition and integration of Dependabot](https://github.blog/2019-05-23-introducing-new-ways-to-keep-your-code-secure/#automated-security-fixes-with-dependabot). **Proposal:** If there will be a workflow which requires corresponding upstream patches for the WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. project, we should document it. Since the pull requests are not being submitted to the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/) repository, this workflow may not be necessary. The examples repository is standalone and is not mirrored upstream in any fashion. ## Agenda: Broader Impact of Gutenberg Patterns _[Slack Conversation](https://wordpress.slack.com/archives/C5UNMSU4R/p1559657599012200)_ [@nerrad](https://profiles.wordpress.org/nerrad/) raised a concern that patterns developed in Gutenberg may conflictconflict A conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered _stale_, and will require a _refresh_ of the changes before it can be applied, or the conflicts will need to be _resolved_. or overlap with patterns in the broader wp-adminadmin (and super admin) interface. **Example:** The [“Snackbar”](https://github.com/WordPress/gutenberg/pull/15594) iteration is relevant in the conversation about [notifications in the administration screens](https://core.trac.wordpress.org/ticket/43484). **Question:** Are features which land in the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. guaranteed to make their way to stable WordPress release? **Answer:** It’s not intended to be a given, iterations and feedback are to be solicited, and features can be guarded behind feature flags or dropped altogether. But ultimately, the current release workflow does result in most of these being put on a track toward a stable release. **Question:** How do we avoid siloed decision-making? **Considerations:** * These should be discussed beforehand in relevant teams with audiences outside Gutenberg specifically ([#design](https://make.wordpress.org/core/tag/design/) was raised as having discussed this specific “Snackbar” iteration). * There should be some TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. conversation for the broader implications of the specific feature, and if/when this exists, regular updates should be provided to share iterations and solicit feedback. **Next Steps:** Discuss the question of process for how decisions made in Gutenberg are handled in making their way to WordPress core. What are the problems, and who makes the decisions? Consider as a discussion point for a future devchat. ## Open Floor _[Slack Conversation](https://wordpress.slack.com/archives/C5UNMSU4R/p1559659925059300)_ [@nerrad](https://profiles.wordpress.org/nerrad/) shared that the `useDispatch` ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. [https://reactjs.org](https://reactjs.org/) hook is now available for use in Gutenberg master ([pull request](https://github.com/WordPress/gutenberg/pull/15896), [documentation](https://github.com/WordPress/gutenberg/blob/master/packages/data/README.md#useDispatch)). This complements the `useSelect` React hook which had been merged last week ([pull request](https://github.com/WordPress/gutenberg/pull/15737), [documentation](https://github.com/WordPress/gutenberg/blob/master/packages/data/README.md#useSelect)). [@nerrad](https://profiles.wordpress.org/nerrad/) plans to publish a post about these new 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. on his own personal blogblog (versus network, site), and may cross-post or adapt the content into a post for Make/Core (_this blog_). [@gziolo](https://profiles.wordpress.org/gziolo/) shared that he has been making progress on improvements to the `@wordpress/scripts` package tools, including default paths for linting scripts, ensuring the `build` folder is ignored from validation( [pull request](https://github.com/WordPress/gutenberg/pull/15977)), and supporting multiple entry points for build ([pull request](https://github.com/WordPress/gutenberg/pull/15982)). [#core-js](https://make.wordpress.org/core/tag/core-js/), [#javascript](https://make.wordpress.org/core/tag/javascript/) [ ](https://profiles.wordpress.org/antpb/) [Anthony Burchell](https://profiles.wordpress.org/antpb/) 9:30 pm _on_ May 1, 2019 Tags: [5.2 ( 37 )](https://make.wordpress.org/core/tag/5-2/), [core-editor ( 761 )](https://make.wordpress.org/core/tag/core-editor/), design, [dev chat ( 932 )](https://make.wordpress.org/core/tag/dev-chat/), [summary ( 981 )](https://make.wordpress.org/core/tag/summary/) # 󠀁[Dev Chat Summary: May 1](https://make.wordpress.org/core/2019/05/01/dev-chat-summary-april-24-2/)󠁿 ## Announcements Josepha ([@chanthaboune](https://profiles.wordpress.org/chanthaboune/)) has published a 5.0 retrospective wrap up. There are two questions at the end of the post that you are encouraged to discuss in the comments. Thank you for the time and care you have put into this, Josepha! You can find this retrospective wrap up at the following post: > [5.0 Release Retrospective Wrap Up](https://make.wordpress.org/updates/2019/04/26/5-0-release-retrospective-wrap-up/) ## 5.2 updates RC2 is planned for _tomorrow_ with the target release date ~5 days (May 7). Josepha brought attention a few items pending: 1. [#47093](https://core.trac.wordpress.org/ticket/47093) – related to the recovery mode email translations. There’s a potential solution being worked on, but it needs review. 2. [#47070](https://core.trac.wordpress.org/ticket/47070) – related to the Recovery Mode Exit button. Design input and a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a **diff**. A patch can be _applied_ to a codebase for testing. is needed, and then it will also need review. 3. [#46901](https://core.trac.wordpress.org/ticket/46901) – related to the About page. A final patch is incoming that will need review. Most tasks pending for the above tickets have an owner, but it was mentioned by Jonathan ([@desrosj](https://profiles.wordpress.org/desrosj/)) that particular testing and attention to [#47093](https://core.trac.wordpress.org/ticket/47093) – recovery mode email translations is encouraged and appreciated. [@audrasjb](https://profiles.wordpress.org/audrasjb/) asked for an idea of the timing for RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see [alpha (beta)](https://make.wordpress.org/core/tag/design/?output_format=md#alpha-beta). 2 tomorrow. Josepha mentioned that it will likely be in the windows of between 1430- 1630 UTC and again around 2030 UTC. The earlier window is preference. ### 5.3 It would be great to start planning scope/teams/timing etc. for 5.3. (potential agenda item for next week!) Jonathan mentioned that we may be able to start the 5.3 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". in trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. after RC2 has released. ## Open Floor #### WP Campus’ 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) audit released today A big thank you to WP Campus for this important initiative! You can find the blogblog( versus network, site) post announcing the audit here: [https://wpcampus.org/2019/05/gutenberg-audit-results/](https://wpcampus.org/2019/05/gutenberg-audit-results/) [#5-2](https://make.wordpress.org/core/tag/5-2/), [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#design](https://make.wordpress.org/core/tag/design/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#summary](https://make.wordpress.org/core/tag/summary/) # Post navigation [← Older posts](https://make.wordpress.org/core/tag/design/page/2/?output_format=md)