Global Element Templates and 'Best Practices'

I wanted to clarify that my workflow was currently the best option in relation to repeating content.

If, for example I have a Section with a query loop of ‘Room Options’ displayed as a grid. That section of content will be used in multiple locations throughout the site and must be identical. I currently create a template and add it to pages via a shortcode block (with the template shortcode) that is set as a global element. So anytime I need to update the content, I do so within the template itself and those changes are automatically deployed throughout the site where ever I have that specific global shortcode block element.

Components are rather limited at the moment and until those improve, this is the best solution I have found. I just wanted to verity from other devs that I am indeed correct.

CleanShot 2025-04-01 at 08.32.42
CleanShot 2025-04-01 at 08.33.04

1 Like

Great idea! :+1: I wonder if this approach has any effect on performance?

1 Like

It doesn’t. I’ve been using templates as “components” for years. Also works with conditions, and also works with templates in templates in templates. Also works for loops, but you have to wrap the template in a div and give the div the query

I use the template widget rather than the shortcode one though for convenience.

1 Like

That is the same experience I have had with conditions and these global templates. All ok so far. The only issue I have ran into is with more complicated templates they don’t render correctly in the builder. But on the frontend they are grand.

Now components are excellent for a design that you would like to use elsewhere, but with different content and different colour variations/spacing/size for example. Currently Bricks components are lacking in options/versatility which I hope will soon improve. At least a visibility condition ‘switch’ for elements is greatly needed for a button for an example.