Integrations

RCA Themer integrates with your Helix Ultimate template workflow and with page builders indirectly through live DOM and same-origin CSS. It does not integrate as a formal API with third-party builder products.

Helix Ultimate and custom.css

The retail plugin assumes you keep durable brand overrides in custom.css, which Helix loads after compiled template.css. Themer complements Helix Template Options; it does not replace color pickers in template settings. The hosted lab at https://recreatinganew.com/themer uses Helix-oriented fixture chrome so you can design tokens before paste.

SP Page Builder and JPageBuilder

The plugin works from live page CSS and DOM on pages where builder stylesheets are same-origin. Builder-generated inline CSS is harder to inspect and export cleanly. Prefer moving lasting overrides into custom.css so builder saves do not erase your work. The hosted lab is SP Page Builder fixture oriented for design, not a JPageBuilder-only lab.

CDN and third-party stylesheets

Cross-origin CDN stylesheets are limited for inspection and are never live-write targets. Keep brand overrides in your own same-origin custom.css instead of expecting Themer to rewrite someone else’s CDN.

What Themer does not integrate

Themer does not patch Helix compiled template.css on update, does not manage Joomla core template parameters beyond reading which css files exist for allowlisting, and does not install anything from the hosted lab automatically. Path A and Path B stay separate products surfaces sharing the same RCA voice, not the same install bundle.