SW Modules

Frequently Asked Questions - SW Sprocket Rocket Modules

These FAQs explain how Smithworks SW Modules work inside HubSpot, especially for Sprocket Rocket-style themes. Use them to choose the right module, understand common settings, and give AI agents better context before they start guessing.

Can different pages show different popups?

SW Popup Panel can show different popup variants on different pages by using Label & Body Class matching. Each page needs the matching token on the page body class so the correct variant can appear.

On normal website or landing pages in Smithworks themes, the Body Class field is in the page editor under Page contents, then Hidden modules, then Body Class. Blog posts may already receive tag-based body classes from the template.

When should I use SW Quiz Simple?

SW Quiz Simple is for assessment-style offers, such as helping a visitor choose a plan or result. It supports a linear question flow, configurable weighted outcomes, and optional email capture.

If you only need a regular form, use SW Form. If the form needs to sit beside content, use SW Pillar Section with the secondary column set to Form.

Why does SW Quiz Simple ask for form embed code instead of letting me pick a form?

SW Quiz Simple uses a custom submit flow through HubSpot’s Forms API. Because of that, the module asks for the HubSpot form embed snippet instead of simply selecting a form in the editor.

The embed snippet provides the form ID and portal ID the quiz needs for the submission flow. A marketing operations or development partner can get the embed snippet from HubSpot forms.

When should I use SW Section Divider?

SW Section Divider is a visual divider module. Use it between content sections when you want a decorative wave, angle, or custom SVG band across the full browser width.

The module can overlap adjacent sections and can be adjusted for pattern height and layering. If the section needs real content, use a content module such as SW Pillar Section, SW Text and Media, or SW Simple Hero instead.

What should I change if the SW Section Divider wave is hidden behind the next section?

If the SW Section Divider pattern is hidden behind a neighboring section, open the module and raise the Pattern Layer setting in the Style tab. This controls how the decorative pattern stacks relative to nearby content.

Also confirm that Overlap adjacent section is configured the way you want. The overlap amount and pattern height can affect how the divider meets the previous or next section.

What does the Smithworks version report show?

The Smithworks version report compares the modules in a live HubSpot theme against the current Smithworks master reference. It helps show whether modules are up to date or may need review before an upgrade.

The report can surface statuses such as Up to date, Needs upgrade, Fields differ, Version mismatch, Not in master, and Deprecated or legacy. Some modules may also include an SW Version Note that adds more context.

What does Needs upgrade mean in the Smithworks version report?

Needs upgrade means the module in the live theme is behind the Smithworks master reference. It does not necessarily mean the site is broken, but it does mean an update is available.

The upgrade should happen when the client and Smithworks agree that it is the right time to roll down the newer version and review affected pages or templates.

What does Fields differ mean in the Smithworks version report?

Fields differ means the module’s editor structure, such as labels, groups, or controls, does not match the Smithworks master version. It does not mean the site is broken right now.

When the module is upgraded, HubSpot usually preserves what it can, but saved content may need review. Heroes, headers, footers, cards, and blog modules are especially important to spot-check after deployment.

What does Version mismatch mean in the Smithworks version report?

Version mismatch means files inside the same module folder, such as HTML and fields files, do not agree on version metadata. That makes the report less reliable for that row.

The version metadata should be aligned before treating the row as authoritative or before making upgrade decisions based on that status.

What does Not in master mean in the Smithworks version report?

Not in master means the module appears in the theme but is not part of the standard Smithworks master module set being compared. It may be theme-specific, custom, or part of a replacement path.

The recommended next step is to compare any related report rows and follow the SW Version Note or Smithworks guidance before deleting, replacing, or upgrading the module.