Tag Archives: editor-chat

Andrei Draganescu 6:03 pm on June 4, 2019
Tags: , , editor-chat   

Editor Chat Agenda: June 5th

Note taker: @ajitbohra

This is the agenda for the weekly editor chat meeting on Wednesday, 5 June 2019, 13:00 UTC.

  • Tasks Coordination
  • Open Floor

This meeting is held in the #core-editor channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

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

#agenda, #core-editor, #editor-chat
Jorge Costa 5:09 pm on May 29, 2019
Tags: , editor-chat,   

Editor Chat Summary: May 29th

Agenda, Slack Transcript

Announcements

Gutenberg 5.8 was released today, congratulations to everyone who participated in this release!

The release agenda for WP 5.2.2 is out https://make.wordpress.org/core/2019/05/28/5-2-2-release-agenda/.

Regarding the WP 5.2.2 release, from the editor side, we have two PRs to be backported. https://github.com/WordPress/gutenberg/pulls?utf8=%E2%9C%93&q=is%3Apr+label%3A%22Backport+to+WP+Core%22+is%3Aclosed+milestone%3A%225.8+%28Gutenberg%29%22+.

@youknowriad volunteered to backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. the PR’s.

Task Coordination

  • @aduth
    • Toyed with a first 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/ Actions workflow for the project, to auto-assign merged pull requests to milestones https://github.com/WordPress/gutenberg/pull/15826
    • Explored preferences persistence, which initially seemed there could be a simple option to reuse existing features https://github.com/WordPress/gutenberg/pull/15800.
    • Plans to merge some improvements to make the build faster.
  • @youknowriad wants to work on
    • Exploring grid helpers when resizing images.
    • Exploring more animations (snackbars, moving blocks…).
    • document the release tool.
    • automate npm releases.
  • @nerrad
    • Implemented useSelect hook and it’s powering withSelect.
    • Is working on the useDispatch hook.
  • @gziolo
    • Spent one full working day triaging issues last week
    • https://make.wordpress.org/core/2019/05/27/the-block-registration-api-status-update/ – Is still awaiting feedback for the block.json proposal, hopes to finalize it this week.
    • Is helping @joen with improved UXUX User experience for nested blocks.
    • Wants to start on Bring consistency to 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. toolbar for text blocks .
  • @mapk
    • Is working on a few Table block issues.
    • Is looking at word breaks in the Media_Text block.
    • Will look into custom fields checkbox in the Options menu.
    • Will check spacer block clearing floats.
  • @andraganescu
    • continues to work on the media blocks update flow.
  • @kjellr
    • Still helping support the nested block work from @joen
    • Thinking about providing suggested column layouts: https://github.com/WordPress/gutenberg/issues/15663#issuecomment-496568894
    • Narrowing down the icons for the Group block: https://github.com/WordPress/gutenberg/issues/15602
  • @jorgefilipecosta
    • Past week:
      • Worked on the widgets screen endpoints and frontend rendering of blocks in the widget areas, a summary of the work was posted in https://github.com/WordPress/gutenberg/issues/13204#issuecomment-496934219.
      • Worked on other enhancements e.g.: text color in the heading, link UIUI User interface on the images and some editor 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.
    • Next week:
      • Will explore a short term very specific project board to make organizing PR’s and issues easier.
      • Continue the work to solve generic block editor problems affecting the widgets screen and probably external usages of the block editor.
      • Address reviews on the image link UI.
      • Work on some bug fixes and UI enhancements e.g. explore insert by URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org on cover and media text blocks to make them more similar to the other media blocks.
      • Improve the contrast checking to make aware of parent colors (e.g: group block) and solve some bugs.
  • @iseulde
    • Plans to continue with this roadmap: https://github.com/WordPress/gutenberg/issues/13778.
    • Is a bit busy with conferences.

To anyone reading this, it is possible to participate in the task coordination in an async way. Feel free to comment in this post with the tasks that you worked on during the last week and/or what tasks you plan to work on during the next week.

Inline color support

@paaljoachim asked participants in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor chat to discuss his comment https://github.com/WordPress/gutenberg/issues/8171#issuecomment-496304938, that proposes the addition of inline color support.

@youknowriad said:

I think that is something we can consider, it should be tracked in its own issue separately from the block level color support tracked in 8171.

@mapk volunteered to create an issue to track this task.

@iseulde said that this task is on the rich text roadmap, but would be good if there’s a separate issue.

@mapk referred that @phpbits volunteered to implement this feature. Thank you @phpbits!

@youknowriad would like some design and 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. explorations and referred that the following questions should be considered:

  • What inline formatting do we want to support aside colors?
  • Do we want to gather these in a panel/popover?
  • In terms of API, how can we control the availability of these options?

Open Floor

@iseulde proposed a dedicated place (a specific meeting/a channel) to have conversations related to the RichText component.

@youknowriad asked why does it need to be separate from the current meeting? While adding that he not suggesting we don’t do it but was wondering if a section during the core editor meeting could be dedicated to RichText when needed.

@iseulde shared that in her opinion core-editor has become very broad and she thinks it might be good to have something smaller. She is not sure about set meeting times, she thinks that perhaps just a space where people can chat async is enough.

The conversation went on with some people trying to understand the current challenges communication related to RichText faces, and some people showing support to the idea of a RichTextspecific communication medium.

@youknowriad ended the meeting by saying that we should experiment and see what works and asked @iseulde to keep us updated.

#core-editor, #editor-chat, #summary

André 5:55 pm on May 22, 2019
Tags: , editor-chat,   

Editor Chat Summary, May 22nd

Agenda, Slack Transcript

Announcements

  • WordPress 5.2.1 was released and comes with a few 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. Editor bugfixes, including RTL keyboard navigation and Format 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. ones.

Task Coordination

Slack Transcript

Visibility of documentation

Agenda, Slack Transcript

@karmatosed raises the question of how we can make the User docs and Developer docs more visible. Raised from community engagement.

Action items:

  • Engage docs and marketing. @karmatosed and @chrisvanpatten
  • Publish a make post on existing doc resources. @karmatosed
  • Add links to docs in https://wordpress.org/gutenberg/ (to be discussed with marketing). @karmatosed
  • Idea worth exploring: how docs can be surfaced the Help tab in wp-adminadmin (and super admin). Unowned.

Open Floor

Slack transcript

@yannicki asks about the status of adding an inner container to the Group block. It’s in review status and there is some uncertainty around the approach. Will get more attention in the next weeks.

New package @wordpress/data-controls. To be released to npm in next Gutenberg release (expected in a week). @nerrad

Work continues to explore useSelect primitive in @wordpress/data package. @nerrad

Triage sessions: @youknowriad @nerrad @karmatosed

  • these group activities with a set schedule are valuable to bring new contributors and clarify the status of certain proposals
  • this can be resource expensive if they’re ran and attended by the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-team only
  • to be continued and evaluated after a while

#core-editor, #editor-chat, #summary

Andrei Draganescu 7:44 pm on May 15, 2019
Tags: , editor-chat,   

Editor chat summary: May 15

This post summarizes the weekly Editor meeting on Wednesday, May 15, 2019, 4:00 PM GMT+3 held in Slack.

The agenda followed can be found here.

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/ 5.7

Gutenberg 5.7 was released today, congratulations to everyone who participated in this release!

Gutenberg Docs are now in the WordPress DevHub

You can check this out at: https://developer.wordpress.org/block-editor/  They have also been reorganized for better navigation and discoverability. Props to @nosolosw @chrisvanpatten @coffee2code @mkaz @kenshino.

WordPress 5.3 planning

During the previous dev chat the scope of the WordPress 5.3 was discussed. Today @youknowriad asked what can we get into that release from the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor team.

@youknowriad, @aduth, @joen, @getdave proposed new Gutenberg features and updates to land in  WordPress 5.3 (to be released in late August):

Improvements we can safely expect:

  • Columns 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. Resizing
  • Group Block (new block)
  • Nested Block Selection improvements
  • Table Block
  • UIUI User interface improvements: Micro-animations, publishing flow tweaks, Snackbar notifications
  • Selecting parent blocks with clickthrough
  • Block Grouping

Big subjects and uncertain features:

  • A Navigation Block
  • A new widgets screen
  • The Block Registration 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. relying on block.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.

Notes:

  • @mapk expressed concern over committing to landing a Navigation Block in WordPress 5.3 because of a lacking clear place to use the block once it becomes available in the Inserter.
  • @youknowriad expressed hope that we’ll soon have a « widgets screen » prototype 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/ or can be cost-based plugin from a third-party and clarify whether this can be part of the release or not.
  • @gziolo: 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. 1 is the deadline for new features which means late July to have everything ready

Task Coordination

  • @nerrad:
    • Exposing whether a selector has a resolver
    • New `wordpress/data-controls` package is up for review, requires the above before it can be merged
    • Exposing the registry context object needed for the work related to `useSelect` and other 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.,
    • Some initial experimental work on `useSelect`
    • volunteered to review the RFC docs
  • @karmatosed
    • Next week the goal is to go through the ‘needs design’ and pass over issues to see we didn’t miss anything.
    • Personally focused on herding triages and test posting 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).
    • Volunteered to review the RFC docs
  • @mkaz
  • @jorgefilipecosta
    • Add widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user.-areas endpoint, ready for review, and it may be good PR for people with more experience in PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher than JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. to review.ecially
  • @aduth
    • Would like to start looking at persistent user preferences (maybe reduce the frequency in which you see the “Welcome to Gutenberg” tips)
  • @kjellr:
  • @koke:
    • there are more incoming changes to RichText so the mobile team would like to coordinate those better: @sergioestevao and @daniloercoli would be the RichText contacts for iOSiOS The operating system used on iPhones and iPads. and Android respectively.
  • @getdave
  • @nosolosw
    • Helping with docs: fixes, reorganization, migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. to DevHub.
    • For the next weeks, iterate on gallery improvements and the ability to reorder images within them (new controls that are keyboard-friendly and drag&drop).
  • @danr:
    • working on table block improvements, there is a new PR open for adding captions
    • WIll work on  exploring keyboard navigation (navigating between cells using arrow keys)
  • @mapk
    • Will  help @danr on those Table block improvements

Explicit Draft statuses for RFCs

There is an increasing worry over the current state of the Widgets RFC because it is hard to make sense of it, or to follow developments as it’s now at over 170 comments. It became a good example that when trying to devise the perfect all-encompassing plan, discussion can become fragmented, we lose sight of the larger goal, and momentum halts.

There was as lively discussion about this and @youknowriad identified the following actionable steps:

To handle multiple merged RFCs @aduth proposed we’d have a Project board with a column for each RFC, and each column would contain issues or PR’s that affect that column’s RFC.

A second Gutenberg triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. session that is more APAC timezones friendly

The proposal is to have a second Gutenberg triage session around 06:00 UTC, every two weeks, in the slackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. #core-editor channel, but no day is yet. @danr, @noisysocks and, @andraganescu would attend/run the sessions and we’d love it if others could join/help. The reasoning is that many struggle to attend meetings or triage sessions due to timezones, so this would be a chance to get involved at a more comfortable time of day.

Notes:

  • the general feeling was that it’s a good idea and that it should happen.
  • @youknowriad suggested it could include new contributors help

Closing

Have thoughts on the above? Please leave a comment on this post!

The agenda for the next meeting, on Wednesday, May 22, 2019, 4:00 PM GMT+3 , is here; please add anything that you want to discuss.

#editor-chat

aduth 4:40 pm on May 7, 2019
Tags: , , editor-chat   

Editor Chat Agenda: May 8th

This is the agenda for the weekly editor chat meeting on Wednesday, 8th May 2019, 13:00 UTC.

This meeting is held in the #core-editor channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

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

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

aduth 4:06 pm on April 30, 2019
Tags: , , editor-chat   

Editor Chat Agenda: May 1st

This is the agenda for the weekly editor chat meeting on Wednesday, 1st May 2019, 13:00 UTC.

  • 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/ 5.6
  • Tasks Coordination
  • Open Floor

This meeting is held in the #core-editor channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

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

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