Best Practices for Managing Large Sections – Modular Approach vs. Performance

How To
, , ,
1

Hi everyone,

I’ve been working with Bricks Builder and came across a challenge that I’d love to get your input on.

Sometimes, a single section in a layout can become quite lengthy , containing many nested elements and very large structure panel. This makes it difficult to maintain—especially when one developer initially builds the section and another team member later needs to make modifications.

To improve maintainability, I was considering breaking down these sections into smaller, reusable templates or components. However, I’m also concerned about the potential performance impact of using too many components/templates

Has anyone here adopted a modular approach successfully? What’s your strategy for keeping complex sections organized without sacrificing speed? Any insights on how much overhead components might introduce in Bricks?

Appreciate any tips or tricks!

Thanks in advance,

1 Like
2

I don’t know if anyone else has come across this, but I once took multiple sections in a large page that was loading slow in the builder and put them into templates. The page then loaded faster in the builder. When reversing that later on by copying those sections back into the page, my page speed seemed to get worse.

It could just be me, though. Interested in knowing if anyone else had a similar experience.