Title: Getting ready for Gutenberg Author: rabmalin Published: March 7, 2018 --- [ ](https://profiles.wordpress.org/rabmalin/) [rabmalin](https://profiles.wordpress.org/rabmalin/) 5:29 am _on_ March 7, 2018   # Getting ready for Gutenberg You may be already aware of [Gutenberg](https://wordpress.org/gutenberg/) editor which is under rapid development and targeting to be merged in WordPress 5.0. The concept “get ready to make your words, pictures, and layout look as good on screen as they do in your imagination, without any code” has been represented with 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/). It has simplified to unlock the power of WordPress without being pro on coding. Gutenberg is going to be available on coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., exact date is not fixed yet. It provides the ability to create own custom blocks for theme and 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. developers and also works great on mobile if you need a quick edit on your phone. The Gutenberg editor uses blocks to create all types of content, substituting a half-dozen inconsistent ways of customizing WordPress, bringing it in line with modern coding standards and aligning with open web initiatives. These custom blocks change how users, developers, and hosts interact with WordPress for building rich web content easier and more intuitive, democratizing publishing and work for everyone, regardless of technical ability. Theme review team needs to make a decision about custom blocks that we should allow it or not on the theme? Before the Gutenberg merges into core, Theme Review Team need concrete decision regarding the custom blocks. So please provide your views and suggestions about the custom 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. that we should allow it or not in the theme. If you recommend us to allow such blocks, please send us your reasons behind it and share your precious suggestions to clarify your view. If allowed then what types of custom blocks are good to be allowed. Similarly, if you don’t like to allow this, share your views as well, so that we can decide what would be best among them. Feel free to give your views, so that we can make the better environment here in theme review for Gutenberg and custom blocks. We’re looking forward to hear from you! ### Share this: * [ Threads ](https://make.wordpress.org/themes/2018/03/07/getting-ready-for-gutenberg/?share=threads) * [ Mastodon ](https://make.wordpress.org/themes/2018/03/07/getting-ready-for-gutenberg/?share=mastodon) * [ Bluesky ](https://make.wordpress.org/themes/2018/03/07/getting-ready-for-gutenberg/?share=bluesky) * [ Facebook ](https://make.wordpress.org/themes/2018/03/07/getting-ready-for-gutenberg/?share=facebook) * [ X ](https://make.wordpress.org/themes/2018/03/07/getting-ready-for-gutenberg/?share=x) * [ LinkedIn ](https://make.wordpress.org/themes/2018/03/07/getting-ready-for-gutenberg/?share=linkedin) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fthemes%2F2018%2F03%2F07%2Fgetting-ready-for-gutenberg%2F%23respond&locale=en_US) 1. ![](https://secure.gravatar.com/avatar/e03031ff27ac8faa6ea78c24b80036605a505885833dd806b53ce22e1746780b? s=32&d=mm&r=g) 2. [TallyThemes](https://profiles.wordpress.org/tallythemes/) 5:44 am _on_ March 7, 2018 3. I think custom 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. in theme should not allow. It should be in plugins. 4. If we use custom block in theme user will lost content after theme change. 5. ![](https://secure.gravatar.com/avatar/27c0751de5ed93222d17118b8e8b3ea1f97be0c79dafaa270e454df903f1afd1? s=32&d=mm&r=g) 6. [kevinhaig](https://profiles.wordpress.org/kevinhaig/) 6:22 am _on_ March 7, 2018 7. I will repeat the comments I made back on Dec19 in SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/): 8. After building a custom 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. I can’t see where TRT can allow them in themes. Here is my reasoning : 1) They can be used anywhere in a theme post or page content area and if a user switches themes all the custom content in posts and pages would have to be changed by the user because all the custom styles would be lost. **Theme switch will be a bad user experience.** 2) This is a very similar situation to presentational shortcodes if allowed in a theme and the user switches themes. The 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. becomes invalid and the user must fix all the content where they were used. 3) However in the case of custom blocks, the user would have much more significant content to fix than even shortcodes, given the htmlHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. enriched content with styles custom to the theme. I can’t imagine the mess a user without html/css knowledge would be in when they switch themes. 4) The only way I can see it being permitted would be if inline styles were permitted for custom blocks. That way users would not have to give up the content blocks created. But that would be very messy, and somewhat risky for breaking sites. 5) If you are going to allow any custom blocks, then you might as well allow presentational shortcodes back in themes. 9. ![](https://secure.gravatar.com/avatar/437dbaaecb3780c9ffeb6f7df0a407d81ec50d0393e6862d75a868c8e38fcd52? s=32&d=mm&r=g) 10. [MH Themes](https://profiles.wordpress.org/mh-themes/) 8:03 am _on_ March 7, 2018 11. In our opinion custom blocks **definitely** should be allowed in themes. Anything else wouldn’t be a viable solution, especially when you think about backwards compatibility and what previously was allowed in themes. 12. For example when you look at the tons of magazine themes in the directory. These themes usually were built with a widgetized front page, allowing users to build their front page with widgets and display posts in different ways. These kind of widgets have always been allowed in themes, the widgets don’t create content, they just display content that is already available. 13. While 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/) will replace widgets at some point, it would be unacceptable to not allow custom widgets in themes and replace the available widgets with blocks. Themes that were previously using widgets for layout purposes should be allowed to be updated while using blocks instead. That way there can be a nice transition period where users will have the widgets and blocks available at the same time so that they can convert their front pages from widgets to blocks without breaking their sites. 14. Users may already get quite confused during the Gutenberg transition and make them install all kinds of additional plugins for things that previously were possible out of the box wouldn’t be good, neither from a marketing point of view nor in regards to usability. 15. * ![](https://secure.gravatar.com/avatar/625d8076bccadd98602e7e0099c070656d968b5d58ce30d7d58b04bdb4a73fdf? s=32&d=mm&r=g) * [ashiquzzaman](https://profiles.wordpress.org/ashiquzzaman/) 1:06 pm _on_ March 7, 2018 * +1 for custom blocks in themes. Because _While 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/) will replace widgets at some point, it would be unacceptable to not allow custom widgets in themes and replace the available widgets with blocks. Themes that were previously using widgets for layout purposes should be allowed to be updated while using blocks instead. That way there can be a nice transition period where users will have the widgets and blocks available at the same time so that they can convert their front pages from widgets to blocks without breaking their sites. * ![](https://secure.gravatar.com/avatar/6a97b9fdf799797b7e29604f11d3c6ba1da31e57f4fdb9f76dba09cb052770b1? s=32&d=mm&r=g) * [Joy](https://profiles.wordpress.org/joyously/) 2:41 pm _on_ March 7, 2018 * Your argument does not quite make sense. Themes providing custom widgets would still be able to. All of the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. widgets (and more!) are already being defined as blocks in 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/), so the theme does not need to define them. The theme can continue to use widgets for **backward compatibility**. When they decide to remove widgets, there will be plenty of time to transition the thousands of plugins that provide widgets… - ![](https://secure.gravatar.com/avatar/437dbaaecb3780c9ffeb6f7df0a407d81ec50d0393e6862d75a868c8e38fcd52? s=32&d=mm&r=g) - [MH Themes](https://profiles.wordpress.org/mh-themes/) 2:54 pm _on_ March 7, 2018 - Sorry, but you don’t seem to understand what we’re referring to. This isn’t about coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. widgets or widgets that may be provided by plugins. It’s about widgets to display posts in various different ways to create all kinds of layouts. This is a common practice in magazine themes, it has been for years and still is. - If custom blocks wouldn’t be allowed in themes, these themes can’t be updated properly in order to provide users the same functionality and usability they are used to. Just imagine a magazine theme with 10+ custom widgets to display posts in various different ways. When widgets will be deprecated, themes can’t replace these widgets with blocks if it’s not allowed… - So we’re basically telling users: _“Well, here is this great new 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/) thing, you’ve never asked for it, but here it is. Oh, before we forget, the widgets you’ve used to build your site for years are blocks now, but your site won’t work anymore because your theme doesn’t include these blocks. You first need to download 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. XYZ and then have fun rebuilding your site.” - Change is good and necessary to move WordPress forward. But really, making things more difficult and harder for users than necessary doesn’t lead anywhere. * ![](https://secure.gravatar.com/avatar/6a97b9fdf799797b7e29604f11d3c6ba1da31e57f4fdb9f76dba09cb052770b1? s=32&d=mm&r=g) * [Joy](https://profiles.wordpress.org/joyously/) 2:58 pm _on_ March 7, 2018 * Yes, I understand that you are saying that widgets are going away at the same time that 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/) comes in. That is not happening. - ![](https://secure.gravatar.com/avatar/437dbaaecb3780c9ffeb6f7df0a407d81ec50d0393e6862d75a868c8e38fcd52? s=32&d=mm&r=g) - [MH Themes](https://profiles.wordpress.org/mh-themes/) 3:04 pm _on_ March 7, 2018 - Of course widgets won’t go away in WP 5.0. But eventually they will go away in phase 2 or 3 of 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/). When making decisions about what is allowed in themes and what not it would be highly appreciated if we could keep in mind where Gutenberg is heading and not where it is today. Unless you want to discuss everything over and over again every few months. * ![](https://secure.gravatar.com/avatar/6a97b9fdf799797b7e29604f11d3c6ba1da31e57f4fdb9f76dba09cb052770b1? s=32&d=mm&r=g) * [Joy](https://profiles.wordpress.org/joyously/) 3:12 pm _on_ March 7, 2018 * Yes, I think there will be a good solution for transitioning away from widgets, so we should not jump the gun and decide something without all the facts. We should definitely discuss it again when it is more clear what the future WordPress will provide. * It would be premature to say that “widgets are the same as blocks, so they should be allowed in themes”. Wait to see what is next, please. - ![](https://secure.gravatar.com/avatar/437dbaaecb3780c9ffeb6f7df0a407d81ec50d0393e6862d75a868c8e38fcd52? s=32&d=mm&r=g) - [MH Themes](https://profiles.wordpress.org/mh-themes/) 3: 18 pm _on_ March 7, 2018 - Sure, if we go that way, we need to postpone a decision if custom blocks are allowed in themes until it’s clear what happens with widgets (which may take several months). But I don’t think that this was the purpose of this post. Anyway, thanks for sharing your thoughts. * ![](https://secure.gravatar.com/avatar/27c0751de5ed93222d17118b8e8b3ea1f97be0c79dafaa270e454df903f1afd1? s=32&d=mm&r=g) * [kevinhaig](https://profiles.wordpress.org/kevinhaig/) 5:28 pm _on_ March 7, 2018 * The big difference between custom widgets and custom blocks is when you switch themes all custom widgets are gone, there are no remnants to clean up. For custom blocks the content is now displayed in a different way using default or new theme styles. All custom styles are lost. So all content using custom blocks must be fixed in some way. * This is not a good user experience, and would promote theme lock in. * ![](https://secure.gravatar.com/avatar/4bbfba8ca7da1eddb9951e797a0f53a6359c385679365ce12ebcebdd748857fd? s=32&d=mm&r=g) * [adrianwackernah](https://profiles.wordpress.org/adrianwackernah/) 1:13 pm _on_ March 13, 2018 * I don’t think so MH Themes, even if a theme does have it’s own layout builder you have the option to disable 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/) and use your own. In that way users have to know, that they will loose the ability to switch to another theme but on their own risk. For users who have setup their site before Gutenberg with a layout builder they may wan’t to stay with it. * I had this situation were I had setup my own site with layout builder and as I tried to switch to another theme, I gave up three times because of huge work. After third try I changed all and promise never to use a layout builder again. * Do not allow themes to have blocks integrated. A 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. for this would be much better. 16. ![](https://secure.gravatar.com/avatar/79224154acc46ba1a1569981c922bd0a33e3d30d42d19982fed7fade75998ca3? s=32&d=mm&r=g) 17. [derweili](https://profiles.wordpress.org/derweili/) 11:21 am _on_ March 7, 2018 18. I think custom 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. in theme should not allow generally. Blocks should be in plugins. Themes were always meant to handle the styling of a page, not the content. To allow blocks means to provoke a content loss. No WordPress beginner will understand this and WordPress was always build for Non-Developers. 19. The only thing I could accept are layout blocks (nested blocks) which enable an advanced layout. Because they will only work if the Theme can handle them. 20. ![](https://secure.gravatar.com/avatar/6d2eeedac545171ca1e20f49e034c57c8fe0ee9272c5e052b365a3723a87acf8? s=32&d=mm&r=g) 21. [Dane Morgan](https://profiles.wordpress.org/dane-morgan/) 1:46 pm _on_ March 7, 2018 22. I see blocks as 100% 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. territory. The purpose of a theme is in controlling how and where blocks are displayed. 23. I understand the widgets argument, but when ( and given that this is WordPress, a bigger if ) widgets are actually deprecated, it will happen more than slowly enough to consider with a clearer understanding of what that means and how it affects themes. 24. * ![](https://secure.gravatar.com/avatar/0fb3ae21a26d50f43ed2df912889e58c3945e0635b155a19e41cfaed2d7e7e9f? s=32&d=mm&r=g) * [Dane Morgan](https://profiles.wordpress.org/danemorgan/) 1:51 pm _on_ March 7, 2018 * Sorry. I posted that under that old account… 25. ![](https://secure.gravatar.com/avatar/6a97b9fdf799797b7e29604f11d3c6ba1da31e57f4fdb9f76dba09cb052770b1? s=32&d=mm&r=g) 26. [Joy](https://profiles.wordpress.org/joyously/) 2:49 pm _on_ March 7, 2018 27. I really don’t see why this question even comes up. If the project had been to revamp the look of the current editor, would we be suggesting that theme guidelines change? Themes should not be involved in content editing, regardless of which editor is used. However, themes are currently allowed to provide metaboxes for presentational options, so that sort of thing should still be allowed. I don’t see why a metaboxMetabox A post metabox is a draggable box shown on the post editing screen. Its purpose is to allow the user to select or enter information in addition to the main post content. This information should be related to the post in some way. would ever equate to a 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., though. 28. If you read back through SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/), you’ll see that the current leader of 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/), who used to be very involved in theme review, thinks that themes should _not_ be making custom blocks. 29. ![](https://secure.gravatar.com/avatar/c279d00cf8d7c55faab3acb6ee3a7f2eb5bb2e5e81aa73c143e627ca3902884e? s=32&d=mm&r=g) 30. [David A. Kennedy](https://profiles.wordpress.org/davidakennedy/) 3:34 pm _on_ March 7, 2018 31. Themes should **not** come with custom blocks. 32. 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/) represents a fresh start for themes to be consistent experiences across any WordPress install. That doesn’t happen if many themes come with different blocks and options. We’d recreate the same landscape we have now, where every theme is a system you have to learn to setup, separate from WordPress. Themes should be about just the design, and the user should be able to build whatever they want within that design. 33. If you’re a theme shop, developing blocks in a 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. should be an exciting opportunity. You get to make it easy not just for your themes to work with your custom blocks, but any theme. That means more customers. More sites doing awesome stuff with your products. 34. * ![](https://secure.gravatar.com/avatar/0eff1a02b114621a84d70475314dd69b6bfc43994c699bf1c652082a015e06eb? s=32&d=mm&r=g) * [Rinku Y](https://profiles.wordpress.org/rinkuyadav999/) 4:49 pm _on_ March 7, 2018 * +1 * ![](https://secure.gravatar.com/avatar/c5876422a37fd6194f1443154e5b8dc0920c99df2e3cc83f3d146bf34992abc5? s=32&d=mm&r=g) * [Mark Uraine](https://profiles.wordpress.org/mapk/) 4:57 pm _on_ March 7, 2018 * I second this! Today I see themes come with plugins all the time to add advanced features. While I still think this can be daunting to users, I believe it’s the way to go if your theme absolutely requires it. * Theme switching is HUGE for people. Trends change, design tastes change, and even needed functionality changes. People should have the FREEDOM to switch between themes without worrying about losing content. * I vote for **NO** custom blocks within themes. - ![](https://secure.gravatar.com/avatar/27c0751de5ed93222d17118b8e8b3ea1f97be0c79dafaa270e454df903f1afd1? s=32&d=mm&r=g) - [kevinhaig](https://profiles.wordpress.org/kevinhaig/) 6:33 pm _on_ March 7, 2018 - Just so you understand, content would not be lost, However, how that content appears on the page would change because the custom styles associated with 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. would be lost. - I believe that the custom styles are as important as the content itself, so I am strongly against custom blocks. * ![](https://secure.gravatar.com/avatar/0d0e3a9588b024435dde731c124bad22ffa20d6f5642ccdca046c50973266d94? s=32&d=mm&r=g) * [Marcio Duarte](https://profiles.wordpress.org/pagelab/) 2:48 pm _on_ March 9, 2018 * > (…) custom styles associated with 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. would be lost. * Then we should make the inclusion of default styles in custom blocks a requirement. * Also, we should add easy methods to remove, overwrite or complement custom block styles in themes. * This would solve the issue. * ![](https://secure.gravatar.com/avatar/5612a0b1e26e958b7cb153ad8d69325be61525b2bba4819361bb69f127ec34b4? s=32&d=mm&r=g) * [Mark Root-Wiley](https://profiles.wordpress.org/mrwweb/) 10:55 pm _on_ March 8, 2018 * Big +1. While some blocks might have a theoretically acceptable fallback, drawing that line would be nearly impossible. 35. ![](https://secure.gravatar.com/avatar/cac75fad8e5acce00bcf71cb5ac29612703b7fc2479eba645d790303fe7a3110? s=32&d=mm&r=g) 36. [allancole](https://profiles.wordpress.org/allancole/) 5:33 pm _on_ March 7, 2018 37. In my view, the biggest selling point about Blocks is that it gives users far more control over how their content is presented and organized regardless of the theme they have installed. If themes start adding their own custom blocks, then that advanced control becomes theme specific and may force users to settle for a theme that doesn’t look the way they want just to use a 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. that is only available in one particular theme (or vice-versa). 38. Users should be able to find the theme that they like aesthetically and not have to worry about whether it has or doesn’t have a block or feature that they expect to be compatible with their theme. 39. I also vote for **NO** custom blocks within themes. 40. ![](https://secure.gravatar.com/avatar/0608b540c7da83b396fd9a453ad1ac0298152522bc3a06888d41649e4024a089? s=32&d=mm&r=g) 41. [Ahmad Awais](https://profiles.wordpress.org/mrahmadawais/) 5:40 pm _on_ March 7, 2018 42. Custom blocks in companion 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. gets my vote. It should be a best practice, not a requirement for backcompat. 👋🤔 43. ![](https://secure.gravatar.com/avatar/73511af463288236f96ca58d2703c605f6d1fb974ebce82463d6c0c0fe6df244? s=32&d=mm&r=g) 44. [Kathryn](https://profiles.wordpress.org/zoonini/) 5:43 pm _on_ March 7, 2018 45. > In my view, the biggest selling point about Blocks is that it gives users far > more control over how their content is presented and organized regardless of > the theme they have installed. If themes start adding their own custom blocks, > then that advanced control becomes theme specific and may force users to settle > for a theme that doesn’t look the way they want just to use a 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. > that is only available in one particular theme (or vice-versa). 46. Completely agree with what allancole said above, as well as with kevinhaig’s point about the pain users experience when they lose functionality and content when switching themes. 47. My vote is also to leave custom blocks to 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. territory. 48. ![](https://secure.gravatar.com/avatar/98f214827a4b662f91a1d6d1a956a0837fa03921b6a947cda6625cc3525e5bff? s=32&d=mm&r=g) 49. [smartcat](https://profiles.wordpress.org/smartcat/) 6:37 pm _on_ March 7, 2018 50. I don’t believe custom blocks should be allowed, for the same reasons we don’t allow custom content in customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. or widgets. Users will lose their content when switching themes, and will wonder why blocks are no longer an option. 51. Custom blocks should be 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. territory, as everything which is content-creating should be. 52. * ![](https://secure.gravatar.com/avatar/27c0751de5ed93222d17118b8e8b3ea1f97be0c79dafaa270e454df903f1afd1? s=32&d=mm&r=g) * [kevinhaig](https://profiles.wordpress.org/kevinhaig/) 6:39 pm _on_ March 7, 2018 * I don’t think content is lost, custom styles are lost. - ![](https://secure.gravatar.com/avatar/98f214827a4b662f91a1d6d1a956a0837fa03921b6a947cda6625cc3525e5bff? s=32&d=mm&r=g) - [smartcat](https://profiles.wordpress.org/smartcat/) 6:41 pm _on_ March 7, 2018 - thats good to know, thank you for that. But i guess that still creates a bad user experience if styles are lost. * ![](https://secure.gravatar.com/avatar/27c0751de5ed93222d17118b8e8b3ea1f97be0c79dafaa270e454df903f1afd1? s=32&d=mm&r=g) * [kevinhaig](https://profiles.wordpress.org/kevinhaig/) 6:42 pm _on_ March 7, 2018 * Yes it does. 53. ![](https://secure.gravatar.com/avatar/ee688e454076072936e2f07ceea1727351cda523c1c8925b90e5040a858463e1? s=32&d=mm&r=g) 54. [Carolina Nymark](https://profiles.wordpress.org/poena/) 7:18 pm _on_ March 7, 2018 55. I don’t believe that the new editor will mean that there will be a consistent experience, even without custom blocks, the custom 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. boxes are still widely used and there are no plans to forbid them in themes. 56. I think we should keep the current guideline: only minor content creation or design related blocks. 57. -I still haven’t seen any actual examples of what kind of blocks authors want to add. 58. I think that 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. templates will be more important than custom blocks. 59. * ![](https://secure.gravatar.com/avatar/27c0751de5ed93222d17118b8e8b3ea1f97be0c79dafaa270e454df903f1afd1? s=32&d=mm&r=g) * [kevinhaig](https://profiles.wordpress.org/kevinhaig/) 7:23 pm _on_ March 7, 2018 * What is a design related 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.? * Not sure what a block template is either? - ![](https://secure.gravatar.com/avatar/80421bda390b2c381e57ea8641a4d7897910a76bd09f729cca2b446f920d6ce0? s=32&d=mm&r=g) - [Chris Runnells](https://profiles.wordpress.org/crunnells/) 8:03 pm _on_ March 7, 2018 - > What is a design related 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.? - I’ve been thinking about this for a while too. I think the idea is to have a block that has some _style-related difference_ that you can’t get in a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. block. Maybe a paragraph with large text, a background image, and a call to action button? - > Not sure what a block template is either? - This: [https://github.com/WordPress/gutenberg/issues/3588](https://github.com/WordPress/gutenberg/issues/3588) - > In its most general sense, a block template is a definition that includes > a list of block items. Those blocks can have predefined attributes, placeholder > content, be static or dynamic. - I think this is going to be where themes are going to provide a lot of value. * ![](https://secure.gravatar.com/avatar/27c0751de5ed93222d17118b8e8b3ea1f97be0c79dafaa270e454df903f1afd1? s=32&d=mm&r=g) * [kevinhaig](https://profiles.wordpress.org/kevinhaig/) 8:25 pm _on_ March 7, 2018 * I have no problem if the styles for a custom 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. in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. are changed, because on theme switch the core styles for the block are returned. * Block templates that include pre-set core blocks would also be fine. * But defining custom blocks with custom styles would not. - ![](https://secure.gravatar.com/avatar/ee688e454076072936e2f07ceea1727351cda523c1c8925b90e5040a858463e1? s=32&d=mm&r=g) - [Carolina Nymark](https://profiles.wordpress.org/poena/) 5:04 am _on_ March 8, 2018 - This is a design related 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.. It adds decorative _pre defined_ christmas images. It is theme specific and does not make sense to add to a 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., because they wouldn’t look good in other themes, they match the christmas design and headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. of this particular theme. [https://themes.svn.wordpress.org/christmas-sweets/0.4/js/block.js](https://themes.svn.wordpress.org/christmas-sweets/0.4/js/block.js) * ![](https://secure.gravatar.com/avatar/27c0751de5ed93222d17118b8e8b3ea1f97be0c79dafaa270e454df903f1afd1? s=32&d=mm&r=g) * [kevinhaig](https://profiles.wordpress.org/kevinhaig/) 5:46 am _on_ March 8, 2018 * Ah but what if a user wants a different Christmas theme? It is more likely that users will switch to these other themes more often, because they are seasonal. * In my opinion they should not be allowed. - ![](https://secure.gravatar.com/avatar/ee688e454076072936e2f07ceea1727351cda523c1c8925b90e5040a858463e1? s=32&d=mm&r=g) - [Carolina Nymark](https://profiles.wordpress.org/poena/) 6:32 am _on_ March 8, 2018 - As long as the theme is _installed_, the images will show. If the theme is removed, the images will be missing (404). Another option would be to put the images in the uploads directory so that they are always available. * ![](https://secure.gravatar.com/avatar/27c0751de5ed93222d17118b8e8b3ea1f97be0c79dafaa270e454df903f1afd1? s=32&d=mm&r=g) * [kevinhaig](https://profiles.wordpress.org/kevinhaig/) 6:48 pm _on_ March 8, 2018 * I know your theme as I used it to learn 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/) so thanks for that 🙂 * Having an image specific to a theme used in a Gutenberg 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., does not seem the right thing, even if they were allowed. The reason being that the image is stored in the theme’s directory and there is no guarantee the user will not delete it. 60. ![](https://secure.gravatar.com/avatar/8013a62d7397c006bae48b96d6832a573ea71a7d5d3597fe584210567b508c05? s=32&d=mm&r=g) 61. [Justin Tadlock](https://profiles.wordpress.org/greenshady/) 7:41 pm _on_ March 7, 2018 62. The only circumstance in which I’m in favor of allowing custom blocks is if that 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. doesn’t break on output when a user switches themes. I’ve previously given an example of this in the form of a “note” block where it’s just simply a wrapping element with a custom class. The only thing lost on theme switch in that case is the style. 63. The vast majority of blocks are going to be far more complex and not a great fit for themes. Reviewing custom blocks on a case-by-case basis to allow a minority of blocks that might fit into a theme doesn’t seem like a good use of anyone’s time. There’s also too much subjectivity there between various reviewers. 64. I like what [@davidakennedy](https://profiles.wordpress.org/davidakennedy/) said above: 65. > 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/) > represents a fresh start for themes to be consistent experiences across any > WordPress install. 66. Gutenberg feels like a clean slate for both theme authors and the TRT in making sure that there’s a distinction between presentation and functionality. 67. We should take this opportunity and go ahead and disallow custom blocks. That’s going to be my official recommendation. 🙂 68. With that said, any theme author who wants custom blocks should present a real- world use case. Build out a test block and explain why it should be allowed. 69. **Overwriting block output** 70. The far more likely thing to happen with themes is that they will overwrite coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and 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. block output by setting a custom` render_callback` property. That’s something we’ll want to discuss. 71. * ![](https://secure.gravatar.com/avatar/34960dca4740f460d324c10e595700ec29af9912fe6b5a1796cd38e342799b07? s=32&d=mm&r=g) * [Sky](https://profiles.wordpress.org/skyshab/) 7:54 pm _on_ March 7, 2018 * That actually makes me think: you can define “Transforms” in the create 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. 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.. As long as the custom block has a transform “to” set that was somewhat equivalent to a default block, would this be a good enough fallback? - ![](https://secure.gravatar.com/avatar/7ad325c24fa7c21069444a3fb9a809ee2ce5e176ef834eab25f87d550569ce0a? s=32&d=mm&r=g) - [Nikola Nikolov](https://profiles.wordpress.org/nikolovtmw/) 1:15 am _on_ March 8, 2018 - Problem with that is that when you disable the theme, 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/) no longer recognizes the custom 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. and therefore doesn’t know what it can transform to 🙂 So unfortunately I don’t think that it would work that way. * ![](https://secure.gravatar.com/avatar/34960dca4740f460d324c10e595700ec29af9912fe6b5a1796cd38e342799b07? s=32&d=mm&r=g) * [Sky](https://profiles.wordpress.org/skyshab/) 1:53 am _on_ March 8, 2018 * Ha! Good point. - ![](https://secure.gravatar.com/avatar/7ad325c24fa7c21069444a3fb9a809ee2ce5e176ef834eab25f87d550569ce0a? s=32&d=mm&r=g) - [Nikola Nikolov](https://profiles.wordpress.org/nikolovtmw/) 1:22 am _on_ March 8, 2018 - Totally agree. Binary rules are much easier to follow for both theme authors and anyone reviewing themes. The one time I did a theme review, I was overwhelmed with how many things there are to check. Adding a “if/else” rule will only make reviewing themes more difficult and time consuming. - And while it would be more work for theme authors to create companion plugins, if done correctly I believe they have great potential. By “correctly”, I mean if 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. ships with default styles for the custom blocks that the theme can then override – that way the plugin could be used regardless of the theme and won’t lock-in the user. After all we don’t want a plugin that only registers custom blocks and leaves 100% of the styling to the theme(otherwise theme switching will again be a pain, but a tiny bit less) – but that’s beyond the reach of the TRT 🙂 * ![](https://secure.gravatar.com/avatar/27c0751de5ed93222d17118b8e8b3ea1f97be0c79dafaa270e454df903f1afd1? s=32&d=mm&r=g) * [kevinhaig](https://profiles.wordpress.org/kevinhaig/) 8:27 pm _on_ March 7, 2018 * I think custom styling of coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blocks is more acceptable because on theme switch some level of styling integrity will be maintained. 72. ![](https://secure.gravatar.com/avatar/213ffa27eb35ac4a16040157d8d9d8c9a1be19971a387774a8891893215ed084? s=32&d=mm&r=g) 73. [Emil Uzelac](https://profiles.wordpress.org/emiluzelac/) 10:23 pm _on_ March 7, 2018 74. Custom blocks = 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. territory all day long 🙂 That’s my vote! 75. ![](https://secure.gravatar.com/avatar/46e16a98e58c6b2dc73618dc374d84092efaa0cf7628bfc3df2502262d9c688e? s=32&d=mm&r=g) 76. [Sajedeh Gooklani](https://profiles.wordpress.org/gookaani/) 1:09 pm _on_ March 8, 2018 77. Technically it shouldn’t be allowed, even .org theme guidelines always advise against content creation in themes. 78. But we might be able to allow this for the greater good of WordPress. Just imagine installing tens of plugins and loading dozens of static resource files which will end up in increasing page size and lower site load speed. 79. Besides, theme authors need to maintain an additional 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. just for providing some simple blocks for displaying in the theme. 80. Last but not least with not allowing this in themes what can we expect from theme authors who are always willing to come up with new and brilliant solutions to make their themes worthy. 81. * ![](https://secure.gravatar.com/avatar/625d8076bccadd98602e7e0099c070656d968b5d58ce30d7d58b04bdb4a73fdf? s=32&d=mm&r=g) * [ashiquzzaman](https://profiles.wordpress.org/ashiquzzaman/) 1:40 pm _on_ March 8, 2018 * Generally it makes sense to NOT include any sort of custom blocks into .org themes, also it will make the whole theme review process easier. But making 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.(s) for every 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. is overkill. And If we don’t allow custom blocks, most of the theme will have the same functionality and I think there will be no real value proposition for visitors (Apart from different styles for the same blocks) to browser themes in official theme repo . Be it Magazine, business, portfolio or kind of multipurpose theme, every theme will have the same coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blocks and functionality. I believe we have to find a middle ground - ![](https://secure.gravatar.com/avatar/2a9a436a279049025e6d68d400ef12f39d4ef00898b745428aaabecbc42a171d? s=32&d=mm&r=g) - [Sallie Goetsch](https://profiles.wordpress.org/wpfangirl/) 12:44 am _on_ March 9, 2018 - > There will be no real value proposition for visitors (Apart from different > styles for the same blocks) - How is that different from what we have now? Themes create styles for the default WP widgets, and also (very often) for popular plugins like WooCommerce. Eventually, I’m pretty sure some custom 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 (produced by page builder teams?) will be used by hundreds of thousands of sites, and theme developers will create styles for those blocks. * ![](https://secure.gravatar.com/avatar/625d8076bccadd98602e7e0099c070656d968b5d58ce30d7d58b04bdb4a73fdf? s=32&d=mm&r=g) * [ashiquzzaman](https://profiles.wordpress.org/ashiquzzaman/) 1:15 am _on_ March 9, 2018 * _How is that different from what we have now?_ Currently there’s a tiny bit of room for custom content. - ![](https://secure.gravatar.com/avatar/4bbfba8ca7da1eddb9951e797a0f53a6359c385679365ce12ebcebdd748857fd? s=32&d=mm&r=g) - [adrianwackernah](https://profiles.wordpress.org/adrianwackernah/) 1: 20 pm _on_ March 13, 2018 - Well [@ashiquzzaman](https://profiles.wordpress.org/ashiquzzaman/), theme could bring us some kind of saved blocks as layout placeholder within and those blocks will remain after theme change. 82. ![](https://secure.gravatar.com/avatar/eb5d081232974bf03b5342543996762577822cf6c5f5e61d0200ed7a413a145a? s=32&d=mm&r=g) 83. [acosmin](https://profiles.wordpress.org/acosmin/) 12:50 pm _on_ March 9, 2018 84. +1 to allow custom blocks in themes 85. Unless you want hundreds of companion plugins with the same functionality 🙂 86. ![](https://secure.gravatar.com/avatar/0d0e3a9588b024435dde731c124bad22ffa20d6f5642ccdca046c50973266d94? s=32&d=mm&r=g) 87. [Marcio Duarte](https://profiles.wordpress.org/pagelab/) 3:25 pm _on_ March 9, 2018 88. Like the majority here, I think we should avoid custom blocks in themes. 89. But WordPress should definitely work towards creating better interoperability between themes and plugins, so we could, for example, easily recommend custom 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 on theme activation, without using third-party solutions for that. 90. ![](https://secure.gravatar.com/avatar/fa1675858df18178ecaee955ff16f29142492a5d2973b6461c11d4675f6db69f? s=32&d=mm&r=g) 91. [Morten Rand-Hendriksen](https://profiles.wordpress.org/mor10/) 9:14 pm _on_ March 10, 2018 92. Like others have said, custom blocks in themes would lead to a confusing experience for end-users when they switch to a new theme. Custom blocks are 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. territory. 93. ![](https://secure.gravatar.com/avatar/35fbfd5445c46796863345b88f04e855ee611cd552a0c8de8d0a35a0a07f514b? s=32&d=mm&r=g) 94. [archana17](https://profiles.wordpress.org/archana17/) 3:44 am _on_ April 18, 2018 95. I believe its really great news for us. 96. ![](https://secure.gravatar.com/avatar/6845456dbc9056f20a4cd50a6b95db78f2ae31df5c0601c613ee5b8939c41a82? s=32&d=mm&r=g) 97. [Jon Brown](https://profiles.wordpress.org/jb510/) 3:32 pm _on_ May 4, 2018 98. Blocks are too important to disappear with a theme change, but there is a solution. 99. WordPress should have a 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. registration mechanism where blocks can persist when a theme (or 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.) is deactivated. It shouldn’t matter if a block is originally brought in by theme or plugin, and they should be independently managed, essentially duplicating the plugin interface but just form ”blocks”. ### Leave a Reply 󠀁[Cancel reply](https://make.wordpress.org/themes/2018/03/07/getting-ready-for-gutenberg/?output_format=md#respond)󠁿 You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fthemes%2F2018%2F03%2F07%2Fgetting-ready-for-gutenberg%2F&locale=en_US) to post a comment. This site uses Akismet to reduce spam. [Learn how your comment data is processed.](https://akismet.com/privacy/) # Post navigation [← Agenda for 2018 February 27](https://make.wordpress.org/themes/2018/02/27/agenda-for-2018-february-27/) [Meeting notes for 2018 March 13 →](https://make.wordpress.org/themes/2018/03/22/meeting-notes-for-2018-march-13/)