Myth: "If you use a builder, build every page with it"

Myth: "If you use a builder, build every page with it"

Teams assume consistency means the builder owns blog posts, archives, everything. That's how you load 200KB of widget CSS onto a text article that needed none.

Pros of selective use:
— Builder loads only on the landing pages that actually need it
— Blog/archives stay light on the theme's native styles

Cons / the discipline cost:
— Two editing flows to teach the team
— Conditional asset loading needs setup (or a plugin like Asset CleanUp)
— Design language can drift between builder and non-builder pages

Verdict: a builder is a landing-page tool, not a site-wide religion. Reserve it for pages that earn the weight.

Best for: sites with a few high-design pages and a lot of plain content.