SW Modules

Frequently Asked Questions - SW Sprocket Rocket Modules

Q: When should I use SW Section Divider?

Use SW Section Divider when you need a decorative full-width SVG band at the edge of a content band—most often a wave under a hero or at the bottom of a form band. Required placement: Put the divider in the same HubSpot Section and Column as the module it shapes. For a wave under a hero, add it in the row directly below the hero and set Position to Bottom. For a wave at the top of a band, place it in the row above that module and set Position to Top (flips the shape). Do not use this module for paragraphs, lists, buttons, or forms—use Pillar, Text and Media, Hero, or Form modules instead. See the placement diagram in SW Module Documentation → SW Section Divider → Placement.

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

If the wave looks covered by the next block: Confirm SW Section Divider is in the same Section/Column as the hero or content it shapes—not alone in the following Section. Open the module → Style → raise Pattern Layer so the decorative bar stacks above neighboring content. Confirm Overlap adjacent content and overlap amount match the intended tuck into neighboring modules. Details: AI documentation → SW Section Divider.

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.

Search FAQs

Still can’t find what you are looking for? Try ChatGPT.

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?

Use SW Section Divider when you need a decorative full-width SVG band at the edge of a content band—most often a wave under a hero or at the bottom of a form band.

Required placement: Put the divider in the same HubSpot Section and Column as the module it shapes. For a wave under a hero, add it in the row directly below the hero and set Position to Bottom. For a wave at the top of a band, place it in the row above that module and set Position to Top (flips the shape).

Do not use this module for paragraphs, lists, buttons, or forms—use Pillar, Text and Media, Hero, or Form modules instead.

See the placement diagram in SW Module Documentation → SW Section Divider → Placement.

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

If the wave looks covered by the next block:

Confirm SW Section Divider is in the same Section/Column as the hero or content it shapes—not alone in the following Section.
Open the module → Style → raise Pattern Layer so the decorative bar stacks above neighboring content.
Confirm Overlap adjacent content and overlap amount match the intended tuck into neighboring modules.

Details: AI documentation → SW Section Divider.

Why doesn’t my SW Section Divider attach to the hero?

The divider only shapes a band when it shares that band’s drag-and-drop Section.

Correct outline: Section → Column → SW Hero → SW Section Divider (siblings). Set Position to Bottom when the divider sits under the hero. Use Position Top only when the divider sits in the row above the content module (that setting flips the SVG).

Wrong: one Section with only the hero, then a second Section with only the divider.

See the content-tree diagram: Placement in SW Module Documentation.

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.