The proposed guidelines for submitting Block 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 to the Block Directory have been revised, with many thanks for the feedback and suggestions from developers and the community. If you haven’t had a chance to see them yet, you can read the most current version of the guidelines here.
In case you missed it, the Block Directory is a new feature coming in WordPress 5.5 that allows specially-written Block Plugins to be instantly and seamlessly installed in the editor, without ever leaving the page. In order for blocks to install seamlessly, they need to meet certain expectations.
These guidelines will be added to the official WordPress Detailed Plugin Guidelines, as a special section that applies to plugins submitted to the Block Directory. This set of guidelines would not apply to general plugins that happen to include blocks — plugins in the main plugin 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 directory need only follow the standard plugin guidelines.
If you are interested in developing a special Block Plugin that will work in the Block Directory, here’s some new documentation and tools to help:
If you have feedback, comments, or questions about the proposed Block Directory guidelines — or about the tools or tutorials — please share them in a comment on this post.