Title: blocks – Make WordPress.org --- # Tag Archives: blocks [ ](https://profiles.wordpress.org/tellyworth/) [Tellyworth](https://profiles.wordpress.org/tellyworth/) 10:44 pm _on_ October 27, 2020 Tags: blocks, [pattern-directory ( 2 )](https://make.wordpress.org/meta/tag/pattern-directory/) # 󠀁[Block Pattern Directory ideas and discussion](https://make.wordpress.org/meta/2020/10/27/block-pattern-directory-ideas-and-discussion/)󠁿 [Block Patterns](https://developer.wordpress.org/block-editor/developers/block-api/block-patterns/) were introduced in WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. in version 5.5 (May 2020) as a way to register predefined blocks in themes and plugins. Once registered on a site, these 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. patterns can easily be inserted into the block editor and then configured by the content creator. Block Patterns help people to add complex block-based layouts to a site in a consistent way. ## Question: Could this feature, the ability to insert community-sourced block patterns into posts from inside the edit screen, help end users unlock the power of the block editor? ## A Few Ideas: * The Block Pattern Directory could be similar to the Block Directory feature introduced in WordPress 5.5, except that no plugins would need to be installed. * Block Patterns could be submitted on 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/). * Users could search the Block Patterns directory from the Block Inserter. * Block Patterns from the directory could be displayed in a visual way. * A one-click installation of Block Patterns could be accessed from the block inserter. ## Additional Questions: * How could the block patterns be represented in the search results? * What should the process and UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. for submitting patterns to a directory look like? * How could previews of Block Patterns account for the visual effect of themes? * How might a Block Pattern Directory accommodate localization? * Should the Block Pattern Directory be limited to patterns using only core blocks? ## Call for Feedback: Some contributors have started exploring some early technical ideas [in this GitHub repo](https://github.com/WordPress/pattern-directory). Check it out to see what technical considerations have been identified so far. Feedback will help this idea to be more successful. Would this idea be helpful for end users? Are there any other things that should be considered? How could this feature be implemented in an easy to use but helpful way? Please share your thoughts and suggestions in the comments below. [#pattern-directory](https://make.wordpress.org/meta/tag/pattern-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%2F2020%2F10%2F27%2Fblock-pattern-directory-ideas-and-discussion%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    # 󠀁[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)