Shared asset folders

A shared asset folder installs Sprocket Rocket modules and the CSS, JavaScript, and macros they need as a plain HubSpot Design Manager folder instead of a theme. Any theme in the same portal can use its modules.

Turn on Install as a shared asset folder when you install Sprocket Rocket from Add theme and want modules without a full theme. Leave it off to install the full Sprocket Rocket theme. See create an installation.

A shared asset folder is not a theme:

• It has no theme settings, and pages cannot be built in it. Everything else works: the rail has Chat, and the top bar has Modules, Blogs, Emails, Templates, and Files, with no Pages or Library. You can make templates and emails there. Module updates are on Modules, with Update all.
• Opening the folder shows its modules beside Sprocket Rocket AI's chat. Describe a module in the chat and Sprocket Rocket names it and writes the brief; confirm the card and Sprocket Rocket builds it and publishes it to the folder. Each module in the list has Ask Sprocket Rocket, to have it change the module, and Edit code, to open the code yourself. A folder has no theme of its own, so the module preview starts with no theme styles. Pick one of the portal's themes from Preview theme above the preview to see the module with that theme's colors, fonts, and classes. Themes from other portals and HubSpot Marketplace themes are not listed.
• A module gets its thumbnail once a theme adds it with Add from folder. On a theme page, you can also ask Sprocket Rocket AI to add a module from the folder by name.

An organization owner or admin can turn the folder into a full theme with Convert to full theme on the folder's page. The conversion adds the missing theme files and leaves existing modules unchanged. It cannot be undone, and it affects every organization that shares the installation.

Add a folder you already have

A folder already in the Design Manager can become a shared asset folder too, as long as it is not a theme (it has no theme.json). In Add theme, enter its path. Sprocket Rocket says the folder is not a theme and offers two ways forward: choose a different path, or Add as a shared asset folder. Adding it turns on Install as a shared asset folder; then select Add folder. Only an organization owner or admin can add one.

Nothing in the folder is overwritten:

• Its modules stay where they are and show up in the folder's module list.
• Sprocket Rocket adds the default CSS, JavaScript, and macros its own modules need, but only the files the folder is missing.
• If the folder already has its own file at one of those paths, that file is kept. Add theme lists these files before you add the folder, because Sprocket Rocket modules may look different with them.

Edit a module from another folder

A theme page can use a module from another folder through Add from folder. In the module palette these modules sit under Other, after the theme's own modules. Hover a module's name to see which folder it comes from.

Edit code opens such a module's code in its own folder, not in the theme. If the folder is not in Sprocket Rocket yet, an owner or admin is asked once to add it as a shared asset folder first, the same way as above. Other members are asked to have an owner or admin add it. A module from a HubSpot Marketplace theme cannot be changed there.

Use with a Marketplace theme

Marketplace files are locked, so module code can't change in that theme, but it can in a folder beside it. You don't have to set this up: connecting a Marketplace theme adds a folder named marketplace-<theme>-asset-folder, with none of Sprocket Rocket's files in it, and Sprocket Rocket AI builds there when you ask from the theme's pages. See Build modules with a Marketplace theme.