1. Marcus Tibesar

    Copy blocks is very useful! Thank you GB development team!


  2. Save Gutenberg!

    Gutenberg needs a “Save/Add Block to Library” tool. This would allow a non programmer to use nested Gutenberg Blocks to create simple reusable layout templates for clients or employees to build things like product pages.

    Bonus points for an “Export/Import” block tool!

    My current solution is to create the layout I need, then open the Gutenberg “Edit Code” and copy the layout into a text file. I often do this myself, but teaching a client how to (non-destructively) paste code into the visual editor is far more difficult than it seems like it would be.


  3. Jeffrey Carandang

    Quite interesting the more and more features from EditorsKit( https://wordpress.org/plugins/block-options/ ) has been added on the core Gutenberg. The “copy” feature receives a lot of love from the users and kinda sad to let it go on EditorsKit :D


  4. Phil Johnston

    While cool on the surface, a testimonials pattern could end up causing you headaches in the future. For example, what if you want to show a “random” testimonial somewhere on your site in the future? Because you’ve stored the actual content of the testimonial in a block, it is almost impossible to query.

    Data for things like testimonials should not live in blocks, but rather in an organized and queryable table, and blocks should be used only for the layout.

    Otherwise you box yourself into a corner with what you can do with your data.

    I feel like the testimonials block pattern example isn’t something people should use without carefully considering how their data is being stored.

    These data storage decisions are the types of decisions end users will have to make with blocks.


    • Justin Tadlock

      It depends on the use case. Generally speaking, I would rather store my testimonials elsewhere and query them as needed. However, there are plenty of use cases where a one-off testimonial pattern would be fine. Think, something like a book landing page where the user will only ever want to show a testimonial on that particular page.

      The current patterns are experimental. There are no indications of what will ship when they land in core. But, I could see some type of testimonial pattern making the cut.


      • Phil Johnston

        I agree that it does depend on the use case, yeah. Just something to think about before putting too much data (of any kind) into block form though.

        I’m personally not sure that making people think testimonials should be a pattern is helpful to them.

        Testimonials have a lot of connected data, like the person’s name, email, picture, date of testimonial, thing testimonial is about (product a), and the testimonial text itself. Separating all of those pieces of data into hard-to-query separate blocks may not be helpful down the road. Especially if you want to re-use testimonials in another context ever.

        But if its only 1 or 2 testimonials, and the site will never scale to the point of having dozens or more, than a testimonial block pattern might be helpful.

        I’m not certain if that covers the helpful-to-80% rule to get in core though.


    • Kristian

      The problem with this is that you assume the user knows how to seperately store and then query testimonials. While what you’re describing is technically better it is also a lot more demanding to implement for the user.

      The patterns aren’t there to displace structured content, but to let more people implement features they want. Even if it isn’t the best technical solution.


      • Phil Johnston

        Plugins like Strong Testimonials do this very well, and put a lot of thought into it so users don’t have to.


        • Phil Johnston

          What I mean is, this type of data is plugin territory in my opinion, and can be handled better, even within and using Gutenberg blocks. A testimonial block from a plugin which properly stores testimonials is a much better UX, especially down the road, than using generic blocks which have no concept of what they are storing.

          I am not assuming users know how to write a query. It’s exactly the opposite of what I mean. Users don’t know, and shouldn’t have to know. They should be able to trust that core developers have their best interests in mind.

          With it as a plugin, if its poorly done, there are ratings to warn. But if poorly done in core, there’s no way to rate that as a user. This I felt it was worth mentioning.

          Blocks are great, but core shouldn’t be advising storing data in a certain way for something as specific as a testimonial (in my opinion), unless they are going to help you store it more properly.


  5. Aarhan Sharma

    copy block is useful, plus I have been able to make blocks within the post as well to highlight the content, thanks development team.


  6. Paal Joachim Romdahl

    Hey Justin

    I just want to mention that Embedding a link is being worked on. The first PR transforming Embed into a Paragraph was merged into 8.1: https://github.com/WordPress/gutenberg/pull/17413

    Work is also happening on adding a placeholder.


    • Peter Shaw


      That is great but why all the harmful features in the Gutenberg plugin? Is there a way of turning off programmatically many of the more page builder like features?

      Any guides to this?



  7. Joseph

    How are changes to Gutenberg incorporated into core?

    If changes are incorporated into core, I guess then that WP 5x users without the Gutenberg plugin would see those changes in the next minor update of WP – would that be correct?


  8. Amin

    Gutenberg has come a long way from its first release, and, as I anticipated a lot of theme & plugin vendors and WP developers are rising to meet the need of doing things in Gutenberg more easily, including making your own blocks. I’m working on a website with a very popular “page builder” plugin right now, and although leading page builders have also come a long way, nothing compares to how good Gutenberg and the block system really are.


  9. Peter Shaw

    Please, please, STOP throwing features at gutenberg.

    Many of us use WordPress strictly as a CMS and we just want content in the editor. We don’t want our users messing with colour palettes or typograhies, and if we want to add a testimonial we’ll use a dedicated plugin.

    If some people need a pagebuilder that is fine, just provide the APIs to do so and let developers add the required features.

    But many don’t and Gutenberg is actually being made worse by some of these changes


Comments are closed.

%d bloggers like this: