[Resolved] Reusable blocks with editable content

Hi there,

you can do it with GenerateBlocks Pro Global Styles:

https://docs.generateblocks.com/article/global-styles/

Natively I would say this is what Block Patterns are used for. In comparison to Reusable Blocks, Patterns inherit styles but not content. However GB global styles allow for more control from the side of the developer.

I would just want to mention two things about global styles.
– One: it looks like global styles are a preparation for custom block/pattern building in generate blocks. Am I wrong?
– Currently the functionality is almost all there, only the usability is a bit difficult. It would be great from that perspective if the global styles could be accessible from a menu, or block selection in gutenberg, so that it is easy for clients to access them. Are there any plans to do something like this?

I am considering to use this approach instead of a native one to have more control over what client can do with gutenberg https://www.billerickson.net/innerblocks-with-acf-blocks/ but then realised global styles could do this. The only advantage I can now see in acf approach is that these can then be accessed as other blocks so it becomes easier for clients to use them. But If I could do all this with GP blocks that would be preferable.

Tnx David

Just to say I just started playing with Local Templates … OMFG this is briliant.

Hi David,
this is perfect, I can really build a an atomic design system like this.

One thing that bugs me though.

I would love to hide the gb blocks controld from other users on the site, the team is quite big, and includes people of various skillsets, and so many options in GB will be overwhelming.

As mentioned here I can set my defaults wich is great, but there can still be overriden locally.

If I allow only some core blocks for editors I am half-way there, they can only use the blocks I have placed on the page or the core blocks, but they can still mess up the padding margin etc.

Core blocks can have their controls removed via theme.json like this https://github.com/thisbit/gutenberg-docs-for-humans/blob/main/Theme.json.md

Can I use theme.json to kill the GB features once I set my defaults fo GB blocks? Or is there another way to do this?

Too much power for casual editors.

Thanks

Thanks for your reply Tom,

this a very important feature for GB if it is meant to be used with clients, because all the great many features (settings) exposed to the dev, become a problem for clients and enforcing the styleguide for the site. So great news that you will be introducing it this year. This is realy great news.

I have tried to use both theme.json for GB, and tried to unregister blocks style, and while I can use these methods with core/blocks it does not work with generateblocks/blocks.

While waiting for the native feature to arrive, I wish to share how I handle this now.

I am loading a css file in the editor on the post type condition so that the blocks settings panels are available (visible) only in, Global styles post type, Local Templates post type, and in Elements post type. The admin has them available in all post types (if local overrides are needed), and I can allow different groups of users (some native, some custom) to access the elements for example (not probable, but possible).

I am leaving the Advanced pannel open to all, and I have added toggles there to enable variations on global styles to be available via classes. So editor can now easily control the size of button, or vertical spacing of a custom built local template via toggle.

This is the way to control the design system so that global styling is a first class citizen. And to control who can access what. Also allowed_blocks method, limits available blocks to the editors group to some basic core ones, and everything else (built with GB), various layouts sections, and more complex blocks/components, are available as local templates only.

I am now testing this solution and so far it seems it works quite nicely. 🙂
Best