Title: Make WordPress.org – Page 24 – A self-referential site --- [ ](https://profiles.wordpress.org/iandunn/) [Ian Dunn](https://profiles.wordpress.org/iandunn/) 6:39 am _on_ May 9, 2019 Tags: [agenda ( 16 )](https://make.wordpress.org/meta/tag/agenda/), [ticket-scrub ( 32 )](https://make.wordpress.org/meta/tag/ticket-scrub/), [wordcamp ( 42 )](https://make.wordpress.org/meta/tag/wordcamp/) # 󠀁[Next WordCamp.org ticket scrub on May 16th, 2019](https://make.wordpress.org/meta/2019/05/09/next-wordcamp-org-ticket-scrub-on-may-16th-2019/)󠁿 This ticket scrub will happen on [2019-05-16 17:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20190516T1700) in the [#meta-wordcamp](https://wordpress.slack.com/archives/meta-wordcamp) channel. The focus is 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. tickets with the [WordCamp Site & Plugins component](https://meta.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&component=WordCamp+Site+%26+Plugins&order=priority). Comment below if there’s a specific ticket or topic you’d like to discuss. [#agenda](https://make.wordpress.org/meta/tag/agenda/) [#ticket-scrub](https://make.wordpress.org/meta/tag/ticket-scrub/) [#wordcamp](https://make.wordpress.org/meta/tag/wordcamp/) +make.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. [https://wordpress.org/](https://wordpress.org/)/community * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2019%2F05%2F09%2Fnext-wordcamp-org-ticket-scrub-on-may-16th-2019%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/tellyworth/) [Tellyworth](https://profiles.wordpress.org/tellyworth/) 8:54 pm _on_ May 8, 2019 Tags: block directory, [blocks ( 2 )](https://make.wordpress.org/meta/tag/blocks/) # 󠀁[Block Plugins and the Block Directory](https://make.wordpress.org/meta/2019/05/08/block-plugins-and-the-block-directory/)󠁿 Over on Make Design, the [design project for installing plugins from within Gutenberg](https://make.wordpress.org/design/2019/04/26/block-library-installing-blocks-from-within-gutenberg/) is underway. It’s time to kick off the discussion about 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. plugins themselves. There’s already been some discussion of this on an earlier [post about blocks in the plugin directory](https://make.wordpress.org/meta/2019/03/08/the-block-directory-and-a-new-type-of-plugin/). That raised a bunch of great points and questions, which this project will attempt to solve. ## Goal: Our plan is to create a new kind of 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., where *the plugin is a block*. These plugins will be familiar to plugin developers, but specially crafted so that they can be safely and seamlessly installed by users from within 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/) editor. They’ll be hosted in a special new section of  the existing WordPress plugin directory. ## Main requirements: * **Gutenberg editor designers and developers** need a way to search the plugin directory for blocks that can be seamlessly installed. * **The plugin directory** needs to index and show metadata about blocks. * **Users** need a way to make a simple and safe decision about whether or not to install a block. * **Site administrators** need a way to manage the blocks and plugins that are available on a site. * **Plugin developers** need ways to clearly communicate the purpose and features of their plugin blocks. * **The plugin review team** needs to set and enforce clear rules about plugin code and behaviour. ## Scope: * We’ll be designing the architecture for a new type of plugin that is focused on single blocks. These plugins **are** blocks. * The  new plugin type will be a subset of the existing WordPress plugin architecture, and compatible with the existing install and update systems. * The new plugin architecture will have some additional limitations and restrictions over and above regular plugins, such as limited UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. and server-side code. * We’ll consider the feasibility of block previews, that could be displayed inside the editor prior to installing the plugin itself. * Security implications will be critical. * We’ll look at the needs of developers with respect to server-side rendering and coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. APIs. * We’re aiming to produce a simple initial version that can be ready in time for the WordPress 5.3 release. ## Next steps: * Scoping the plugin architecture in more detail. * Designing the simplest block plugin that could possibly work. * Creating a separate section within the plugin directory for block plugins. ## When and where to follow along: * The fortnightly 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. Chat, every second Wednesday at 2100 UTC( right after the Core Dev chat) * Regular discussion in [#meta](https://wordpress.slack.com/messages/C02QB8GMM) between formal chats * Important updates will be posted on [Make Plugins](https://make.wordpress.org/plugins/) and [Make Meta](https://make.wordpress.org/meta/) ## Who is involved: * [@tellyworth](https://profiles.wordpress.org/tellyworth/) is leading the plugin architecture and block directory project. * [@iviolini](https://profiles.wordpress.org/iviolini/) is leading the [Gutenberg UI project](https://make.wordpress.org/design/2019/04/26/block-library-installing-blocks-from-within-gutenberg/) over on Make Design with [@melchoyce](https://profiles.wordpress.org/melchoyce/) * **You** can get involved in any part of this by joining the regular Meta or Design meetings, or by contacting [@tellyworth](https://profiles.wordpress.org/tellyworth/), [@iviolini](https://profiles.wordpress.org/iviolini/), or [@melchoyce](https://profiles.wordpress.org/melchoyce/) to volunteer. [#block-directory](https://make.wordpress.org/meta/tag/block-directory/), [#blocks](https://make.wordpress.org/meta/tag/blocks/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2019%2F05%2F08%2Fblock-plugins-and-the-block-directory%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/chanthaboune/) [Josepha](https://profiles.wordpress.org/chanthaboune/) 6:38 pm _on_ April 30, 2019 Tags: [make.wordpress.org/updates ( 18 )](https://make.wordpress.org/meta/tag/make-wordpress-orgupdates/), [p2-xpost ( 89 )](https://make.wordpress.org/meta/tag/p2-xpost/)    # 󠀁[X-post: 5.0 Release Retrospective Wrap Up](https://make.wordpress.org/meta/2019/04/30/xpost-5-0-release-retrospective-wrap-up/)󠁿 X-comment from [+make.wordpress.org/updates](https://make.wordpress.org/updates/): Comment on [5.0 Release Retrospective Wrap Up](https://make.wordpress.org/updates/2019/04/26/5-0-release-retrospective-wrap-up/#comment-4477) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2019%2F04%2F30%2Fxpost-5-0-release-retrospective-wrap-up%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/hlashbrooke/) [Hugh Lashbrooke](https://profiles.wordpress.org/hlashbrooke/) 3:18 pm _on_ April 18, 2019 Tags: [make.wordpress.org/community ( 18 )](https://make.wordpress.org/meta/tag/make-wordpress-orgcommunity/), [p2-xpost ( 89 )](https://make.wordpress.org/meta/tag/p2-xpost/)    # 󠀁[X-post: The Get Involved table at WCEU 2019](https://make.wordpress.org/meta/2019/04/18/xpost-the-get-involved-table-at-wceu-2019/)󠁿 X-post from [+make.wordpress.org/community](https://make.wordpress.org/community/): [The Get Involved table at WCEU 2019](https://make.wordpress.org/community/2019/04/18/the-get-involved-table-at-wceu-2019/) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2019%2F04%2F18%2Fxpost-the-get-involved-table-at-wceu-2019%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/vedjain/) [Vedanshu - Urumi.AI](https://profiles.wordpress.org/vedjain/) 10:06 pm _on_ April 15, 2019 Tags: [agenda ( 16 )](https://make.wordpress.org/meta/tag/agenda/), [meta-wordcamp ( 5 )](https://make.wordpress.org/meta/tag/meta-wordcamp/), [ticket-scrub ( 32 )](https://make.wordpress.org/meta/tag/ticket-scrub/), [wordcamp ( 42 )](https://make.wordpress.org/meta/tag/wordcamp/)    # 󠀁[Next WordCamp.org ticket scrub on April 18, 2019](https://make.wordpress.org/meta/2019/04/15/next-wordcamp-org-ticket-scrub-on-april-18-2019/)󠁿 This ticket scrub will happen on [2019-04-18 17:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20190418T1700) in the [#meta-wordcamp](https://make.wordpress.org/meta/tag/meta-wordcamp/) channel. The focus is 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. tickets with the 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/). Site & Plugins component. Comment below if there’s a specific ticket or topic you’d like to discuss. [#agenda](https://make.wordpress.org/meta/tag/agenda/) [#ticket-scrub](https://make.wordpress.org/meta/tag/ticket-scrub/) [#wordcamp](https://make.wordpress.org/meta/tag/wordcamp/) +make.wordpress.org/community * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2019%2F04%2F15%2Fnext-wordcamp-org-ticket-scrub-on-april-18-2019%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/coreymckrill/) [Corey McKrill](https://profiles.wordpress.org/coreymckrill/) 10:34 pm _on_ March 29, 2019 Tags: [wordcamp ( 42 )](https://make.wordpress.org/meta/tag/wordcamp/) # 󠀁[Feature and maintenance update for WordCamp.org: March 18-29, 2019](https://make.wordpress.org/meta/2019/03/29/feature-and-maintenance-update-for-wordcamp-org-march-18-29-2019/)󠁿 Here’s a list of the WordCamp.org feature developments and maintenance work that was accomplished in the last two weeks: * Continued iterating on 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/).’ s shortcodeShortcode A shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site.-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. conversions - Introduced the Organizers block - Updates to Speakers, Sessions, and Sponsors blocks - Began tracking progress in [a milestone](https://github.com/WordPress/wordcamp.org/milestone/1) * Investigated and mitigated two server downtime incidents * Fixed a problem with retrieving data about meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through [https://www.meetup.com/](https://www.meetup.com/). A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. events after Meetup.com made an unannounced change to their 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. * Fixed a bug that wiped out sponsor data in some situations * Updated the verbiage in ticket receipts to reflect current global sponsors * Began the process of implementing a more reliable cron system on WordCamp.org [#wordcamp](https://make.wordpress.org/meta/tag/wordcamp/) +make.wordpress.org/community * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2019%2F03%2F29%2Ffeature-and-maintenance-update-for-wordcamp-org-march-18-29-2019%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/chanthaboune/) [Josepha](https://profiles.wordpress.org/chanthaboune/) 10:29 pm _on_ March 29, 2019 Tags: [make.wordpress.org/updates ( 18 )](https://make.wordpress.org/meta/tag/make-wordpress-orgupdates/), [p2-xpost ( 89 )](https://make.wordpress.org/meta/tag/p2-xpost/)    # 󠀁[X-post: Weekly Digest | Week 13](https://make.wordpress.org/meta/2019/03/29/xpost-weekly-digest-week-13/)󠁿 X-comment from [+make.wordpress.org/updates](https://make.wordpress.org/updates/): Comment on [Weekly Digest | Week 13](https://make.wordpress.org/updates/2019/03/29/weekly-digest-week-13/#comment-4470) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2019%2F03%2F29%2Fxpost-weekly-digest-week-13%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/tellyworth/) [Tellyworth](https://profiles.wordpress.org/tellyworth/) 1:41 am _on_ March 29, 2019   # 󠀁[Block metadata in the Plugin Directory](https://make.wordpress.org/meta/2019/03/29/block-metadata-in-the-plugin-directory/)󠁿 Plugins that are in the [Block-Enabled section](https://wordpress.org/plugins/browse/blocks/) of 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. Directory can now automatically list the blocks that they provide. For [example](https://wordpress.org/plugins/give/#blocks): [⌊Screen Shot 2019-03-29 at 12.08.24 pm⌉⌊Screen Shot 2019-03-29 at 12.08.24 pm⌉[ If available the list is displayed for now in the Description section, between screenshots and the FAQ. As you can see it’s a rudimentary list to begin with, that simply lists 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. names and titles. We plan to improve that over time, and to do that we could use your feedback and help. Because of the difficulty of reliably extracting block metadata from code, the best way plugin developers can ensure their blocks are reliably indexed is to use `block. json` files as recommended by the [Block Registration RFC](https://github.com/WordPress/gutenberg/blob/2df7f19b360d9d223212167fe5dc5531a3a8accd/docs/rfc/block-registration.md). We’ve done our best to parse this info out of existing source code, but less than half of Block-enabled plugins were easily discoverable this way. The RFC isn’t yet final, but by experimenting with it now plugin developers can help with feedback and suggestions both for the RFC and for the plugin directory’s use of that metadata. I’ve opened a general ticket [#4345](https://meta.trac.wordpress.org/ticket/4345) for discussing improvements to the plugin directory side. The RFC for the `block. json` specification can be discussed [over on GitHub](https://github.com/WordPress/gutenberg/pull/13693). Feedback, suggestions, and questions are welcome. * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2019%2F03%2F29%2Fblock-metadata-in-the-plugin-directory%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/hlashbrooke/) [Hugh Lashbrooke](https://profiles.wordpress.org/hlashbrooke/) 12:20 pm _on_ March 27, 2019 Tags: [make.wordpress.org/polyglots ( 5 )](https://make.wordpress.org/meta/tag/make-wordpress-org-polyglots/), [p2-xpost ( 89 )](https://make.wordpress.org/meta/tag/p2-xpost/)    # 󠀁[X-post: HelpHub Localisation Plan Meeting Notes](https://make.wordpress.org/meta/2019/03/27/xpost-helphub-localisation-plan-meeting-notes/)󠁿 X-comment from [+make.wordpress.org/polyglots](https://make.wordpress.org/polyglots/): Comment on [HelpHub Localisation Plan Meeting Notes](https://make.wordpress.org/polyglots/2019/03/27/helphub-localisation-plan-meeting-notes/#comment-282936) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2019%2F03%2F27%2Fxpost-helphub-localisation-plan-meeting-notes%2F%23respond&locale=en_US) [ ](https://profiles.wordpress.org/coreymckrill/) [Corey McKrill](https://profiles.wordpress.org/coreymckrill/) 11:25 pm _on_ March 18, 2019 Tags: [agenda ( 16 )](https://make.wordpress.org/meta/tag/agenda/), [ticket-scrub ( 32 )](https://make.wordpress.org/meta/tag/ticket-scrub/), [wordcamp ( 42 )](https://make.wordpress.org/meta/tag/wordcamp/) # 󠀁[Next WordCamp.org ticket scrub on March 21st, 2019](https://make.wordpress.org/meta/2019/03/18/next-wordcamp-org-ticket-scrub-on-march-21st-2019/)󠁿 This ticket scrub will happen on [2019-03-21 17:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20190321T1700) in the [#meta-wordcamp](https://wordpress.slack.com/archives/meta-wordcamp) channel. The focus is 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. tickets with the [WordCamp Site & Plugins component](https://meta.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&component=WordCamp+Site+%26+Plugins&order=priority). Comment below if there’s a specific ticket or topic you’d like to discuss. [#agenda](https://make.wordpress.org/meta/tag/agenda/) [#ticket-scrub](https://make.wordpress.org/meta/tag/ticket-scrub/) [#wordcamp](https://make.wordpress.org/meta/tag/wordcamp/) +make.wordpress.org/community * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2019%2F03%2F18%2Fnext-wordcamp-org-ticket-scrub-on-march-21st-2019%2F%23respond&locale=en_US) ## Post navigation [← Older posts](https://make.wordpress.org/meta/page/25/?output_format=md) [Newer posts →](https://make.wordpress.org/meta/page/23/?output_format=md)