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 Form resubmit cooldown depends on the visitor staying on the page after submission. It only runs when the HubSpot form’s On submission behavior is set to Show thank you message.
If the form redirects to another page, URL, meeting, payment, or other destination, the visitor leaves before the module can show the inline cooldown state. The feature uses the visitor’s browser localStorage.
Form resubmit cooldown follows the same submission rule in SW Pillar Section and SW Form: the HubSpot form needs to use Show thank you message instead of redirecting away from the page.
The pillar form column uses a different browser storage namespace than standalone SW Form. That means timers are not shared between the two module types, and each module instance has its own cooldown behavior.
SW Blog Listing Hero is for blog listing pages, including the main blog index and similar tag or author listing views. It highlights a featured post with a large visual, title, summary, metadata, and read-more behavior.
For single blog article pages, use SW Blog Post Hero. For website and landing pages, use SW Simple Hero.
SW Blog Cards pulls real blog posts into a grid, slider, or listing-style presentation. It is used on blog listing pages and can also be used on website or landing pages that need to feature blog content.
Use SW Blog Related Posts instead when the goal is a read-next style row at the bottom of a single blog post.
When SW Blog Listing Hero consumes the first post, SW Blog Cards often needs to start at post 2 so the same post does not appear twice. The blog’s posts-per-page setting also needs to line up with the card module settings.
The documented relationship is that HubSpot’s number of posts per listing page should match Posts to show plus Post start minus 1. If the settings are misaligned, posts can be skipped or duplicated across pages.
SW Blog Cards slider behavior does not run at the same time as infinite scroll. If infinite scroll is enabled, turn it off before expecting the slider to work.
The slider also needs more posts than fit in one row. If there are not enough posts to create an overflow, the module may not appear to slide.
These modules work together on single blog post templates. SW Blog Post Hero handles the post hero, featured image, title, and metadata. SW Blog Post Body wraps the article body content.
SW Blog Related Posts is used for a read-next or related-articles area at the bottom of an individual post. It is different from SW Blog Cards, which is used for blog listings or website pages that pull posts.
SW CTA Popup is the quicker option when you need one simple popup, usually in a bottom corner, with one main variant. It can work for a single offer or a straightforward site-wide promotion.
SW Popup Panel is the more flexible option. Use it when you need multiple variants, different content on different pages, announcement-style panels, more positions, or more detailed trigger behavior.
Yes. For a standard Smithworks theme, use the global content editor rather than starting in Design Manager. Open a live page, click the footer, and choose Edit global content.
In the left sidebar, select SW Global Site Footer, using Hidden modules if needed. Add SW CTA Popup or SW Popup Panel in the footer drag-and-drop area alongside the footer module, configure it, and publish global content.
If you only see SW Footer Simple fields, you are probably editing the footer module instead of the full global footer area. Step back in the left sidebar and select SW Global Site Footer.
If you do not see it, check Hidden modules. Once the global footer layout is selected, you should see the drag-and-drop region where SW Popup Panel or SW CTA Popup can be added alongside the footer module.
No FAQs match your search in SW Modules.
