I’m testing SP Page Builder 7 (beta) on Joomla 6 with Helix Ultimate, and I have a question about upgrading existing sites that rely on custom CSS.
In SPPB 6 the button markup is sppb-btn sppb-btn-primary sppb-btn-lg (plus sppb-btn-outline for the outline look). In SPPB 7 the same button is rendered as:
<button class="sppb-el sppb-el-button sppb-el-button--lg sppb-el--ds2 sppb-btn-outline">
<span class="sppb-el sppb-el-text btn-primary">Button</span>
</button>
The type (btn-primary) is now on the inner text element, not on the button. Custom CSS written for SPPB 6, such as .sppb-btn-primary, .sppb-btn-outline.sppb-btn-primary or .btn-primary, no longer matches the button, and a generic .btn-primary rule now hits the text span instead. I see this affects more than buttons, since the whole class naming changed to sppb-el-*.
My questions:
When a site is updated from SPPB 6 to 7, are existing pages converted to the new markup, or do old addons keep rendering with the old classes?
Will the old class names (sppb-btn, sppb-addon-* and so on) stay available as a compatibility layer, and for how long? I noticed some .sppb-el-button.sppb-btn rules in elements.css, which suggests partial support.
Is there a documented, stable way to style elements globally (for example the CSS variables of the new design system, or fixed hooks) so custom CSS survives future updates?
Is there a migration guide or a list of old-to-new class names for people who maintain a lot of custom CSS?
Is there a setting to keep the SPPB 6 markup on existing sites while upgrading?
For agencies with many client sites this decides how much work the upgrade will be, so any guidance would be very helpful.
Thanks,
Robert