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.
Still can’t find what you are looking for? Try ChatGPT.
SW Tabs and SW Tags Filter are listed in the SW module index and master changelog. The changelog does not provide detailed behavior notes for them beyond saying they change less frequently.
Use the AI documentation or ask Smithworks for detailed dated entries when a project needs exact field behavior, setup instructions, or upgrade notes for these modules.
sw-macros.html is a theme file that contains reusable HubL macros used by Smithworks modules. The changelog specifically notes that the sw_feature_list macro is required for SW Cards Products.
When adopting SW Cards Products, include the related theme update so the required macro is available. Without the supporting macro, the module may not render as intended.
The quick module picker is a practical starting point for choosing the right SW page module. It is not a replacement for exact field documentation, but it helps decide which module probably fits the job.
| Module | Choose it when you want to... | Usually skip it if... |
|---|---|---|
| SW Pillar Section | Place image, video, form, or extra content beside main copy; create alternating left/right sections; use a wide Module Outer background behind a narrower two-column layout. | You only need one simple stacked block. |
| SW Text and Media | Create a stacked block with optional headings, foreground image or video, rich text, and optional buttons. | You need side-by-side columns, rich-text bullet columns, or pillar-style multi-band layouts. |
| SW Image & Text | Maintain an older simple stacked block with image above rich text. | You are creating new content; prefer SW Text and Media. |
| SW Gallery Section | Show multiple images or videos in a gallery beside written content. | You only have one image or one video beside text; use SW Pillar Section. |
| SW Pillar Accordion | Use FAQs or steps with one image column that changes when each panel opens. | You want tabs, optional per-item images, forms in panels, or buttons below the whole tab block. |
| SW Magic Accordion | Use tabs or accordion content with optional per-item images, forms, and buttons. | You only need a shared image column that changes with each panel; use SW Pillar Accordion. |
| SW Cards | Build manual cards for services, team members, feature summaries, videos, or highlighted items. | You need real blog posts pulled automatically; use blog modules. |
| SW Cards Products | Create product-style cards, feature lists, optional pricing, or plan columns. | You need a comparison table; use SW Feature List. |
| SW Feature List | Create a comparison table with features down the side and plans or tiers across the top. | Each plan should stand alone as its own card; use SW Cards Products. |
| SW Simple Hero | Create a website or landing page hero with headline, supporting copy, image or video, and buttons. | You are editing a blog listing or single blog post hero. |
| SW Form | Show a standalone HubSpot form with optional headings and a styled form box. | The form should sit beside media, proof, or longer copy; use SW Pillar Section. |
| SW CTA Simple Bar | Add a horizontal in-page CTA band with message content and buttons. | You need a popup, hero, card grid, or full form section. |
After choosing a likely module, use the AI documentation for exact Content and Style tab field paths.
The SW module capability matrix is a quick comparison table. It helps editors see which modules are built for specific content needs before opening the full AI documentation.
Legend: ✓ means the module is built for this. ○ means the module sometimes supports it or supports it in a specific way. – means it is not what the module is for.
| Module | Side-by-side layout | Image | Video | Gallery | Headings | Bullets | CTAs / buttons | HubSpot form |
|---|---|---|---|---|---|---|---|---|
| SW Pillar Section | ✓ | ✓ | ✓ | – | ✓ | ✓ | ✓ | ○ column |
| SW Text and Media | – | ✓ | ○ foreground + background | – | ○ repeater | – | ○ repeater | – |
| SW Image & Text | – | ✓ | ○ background | – | – | – | – | – |
| SW Gallery Section | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | – |
| SW Pillar Accordion | ✓ | ○ panel | – | – | ✓ | – | ✓ | – |
| SW Cards | – | ✓ | ✓ | – | ✓ | – | ✓ | – |
| SW Cards Products | – | ✓ | ✓ | – | ✓ | ✓ | ✓ | – |
| SW Feature List | – | ○ cell | ○ background | – | – | – | ○ in cells | – |
| SW Simple Hero | ○ hero layout | ✓ | ✓ | – | ✓ | – | ✓ | – |
| SW Form | – | – | – | – | ✓ | – | – | ✓ |
| SW CTA Simple Bar | ○ band layout | ○ icon | – | – | – | – | ✓ | – |
Use the matrix for fast comparison, then confirm exact settings in the module documentation before editing fields.
The original SW FAQs Advanced used inline repeaters and optional HubDB source toggles. Current master is SW FAQs Advanced HubDB—HubDB-only, built for FAQ hubs with nav, search, tags, and pagination.
Portals may keep the deprecated module for old pages while new work uses the HubDB module. Version reports need a unique Internal name on the new module so rows do not collapse with the deprecated one.
Replace module instances on hub pages during migration; re-publish CMS pages after changing modules.
No FAQs match your search in SW Modules.
