Build modules with a Marketplace theme

Page Builder works on the pages of a Marketplace theme, and so does Sprocket Rocket AI. HubSpot locks the files a Marketplace theme installs, so the app cannot change them or read their code.

New work goes in an asset folder beside the theme instead. When you connect a Marketplace theme, the app adds one, named marketplace-<theme>-asset-folder. You do not have to set anything up. Nothing is wrong with the installation, and your existing pages stay on the theme.

Your site is already built on the Marketplace theme

Ask Sprocket Rocket AI on your page, as you would on any theme.

1. For what the theme's modules can already do, it uses their fields, the page layout, and section styles.
2. For anything else, it writes a card for you to confirm. The module is then built in the background, in the asset folder, and placed on your page while you keep working. The card links to the module's own chat.
3. Publish the page as usual.

You can also open the asset folder yourself to work on its modules, or place one with Add from folder.

Changing a module that came with the theme

Those files stay locked. Sprocket Rocket AI builds your own version in the asset folder and swaps it in on that page, and other pages keep the original. It is a rebuild rather than a copy, because the theme's code cannot be read, so review it before you publish.

What the folder path cannot do

• Build pages in the folder. Pages stay on the Marketplace installation.
• Restyle the Marketplace theme. The theme's settings stay read-only.
• Use the theme's settings in a template or coded email. Those live in the folder, outside the theme, so they bring their own styles.

Sprocket Rocket catalog modules in a folder

A shared asset folder you install yourself holds Sprocket Rocket's catalog modules, which rely on the base styles of a recent Sprocket Rocket Marketplace theme. On a different theme or an older install they can appear unstyled. Update the Marketplace theme first, then add the module again. Updating carries some risk on a live site, so review important pages afterwards.

You have not built the site yet

Create a normal app installation and build there from the start. The app installs its own Sprocket Rocket theme, which gives you Page Builder, module code editing, Sprocket Rocket AI, updates, and backups without a folder beside the Marketplace theme.

Your Core or Stack purchase still counts. Connect the portal and the app assigns the matching license. See Connect a Marketplace purchase.

Moving pages does not move modules

There is no migration from a Marketplace theme to the app's theme.

• Installing the app's theme does not change existing pages.
• Changing a page's template to one from the app's theme does not change the modules on that page. The page still renders, because both themes share the Sprocket Rocket styles, but every module on it is still the Marketplace copy. Those stay locked, so their code still cannot be edited.
• To move a page fully onto the app's theme, place the app's modules on it and remove the Marketplace ones.
• Do not uninstall the Marketplace theme while any page still uses its modules, including pages already on the app's template. Uninstalling deletes those modules and breaks the pages.

For a site that is already live, the asset folder path above is usually the better choice. It lets you build modules without rebuilding pages.

Why can't I edit module code on my Marketplace installation?

HubSpot protects the files of every theme installed from the Marketplace, so the app cannot write into them. Editing a module writes its code into the installation, which needs writable files. Ask Sprocket Rocket AI for the change, which builds your own version in the asset folder, or use a separate app installation for a new site.

I edited a module in the app but my page did not change

The page is still using the Marketplace copy of that module. Changing a page's template to the app's theme does not swap the modules on it, so editing a module such as SR Hero 01 in the app's theme changes the app's copy, not the one on your page. The page keeps rendering because both themes share the same styles, which makes this easy to miss.

To see your edit on the page, place the app's version of the module on the page and remove the Marketplace one, or ask Sprocket Rocket AI on the page to build its own version.

Do I need a child theme?

No. Child themes are neither required nor recommended for app-managed installations or for the asset folder path. If you already have one, the app can work on its own files. The child theme guide exists for customizing a Marketplace theme's locked files without the app.