Editor Chat Agenda: June 12th

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a 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.? Create a ticket in the bug tracker.

Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.

Other questions? Here is a detailed handbook for contributors, complete with tutorials.

Note taker: @pbrocks

This is the agenda for the weekly editor chat meeting on Wednesday, June 12, 2019, 6:00 AM PDT.

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

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.9
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. Europe
Tasks Coordination
Open Floor

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

Garrett Hyder 6:11 pm on June 11, 2019

Hello,

As I won’t be awake for the meeting I was hoping someone could raise naming convention for blocks in the chat.

This was previously raised in #docs on 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/. here;
https://wordpress.slack.com/archives/C02RP4WU5/p1559596330041800

There’s the convention for naming 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/classic editor in lowercase unless referring to 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. But the remaining question is “What about “Paragraph Block” versus “paragraph block” versus “Paragraph block”?” which applies to any block name.

Greatly appreciated
pbrocks 3:44 pm on June 12, 2019

@garrett-eclipse, while the answer is open to interpretation and influenced by context, the general thought is that when you are naming a concept or unit, the capitalization goes on the descriptor, but not the head noun. That is, for the example you proffered, @chrisvanpatten, who championed much of 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/ Handbook, prefers Paragraph 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., as opposed to your other options. This is in accord with something like, Classic Editor 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, where the descriptor consists of two words and the head noun is plugin. Make sense?

For more discussion, you may have already seen the Issue created by @mapk. Let’s follow up there.
- Garrett Hyder 4:29 pm on June 12, 2019
  
  Thanks @pbarthmaier greatly appreciated will follow along and comment on the issue.
SamuelFernandez 4:12 pm on June 12, 2019

Would be nice if this is also treated: https://github.com/WordPress/gutenberg/issues/14744

Comments are closed.

Welcome!

Communication

Share this: