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.
Sometimes an older module remains in a theme while a newer module replaces it for new work. This protects existing pages that still depend on the legacy module.
Do not delete or overwrite the legacy module while old pages still use it. Use the replacement module named in the report, note, or documentation for new pages and planned migrations.
Before approving a Smithworks module upgrade, read the SW Version Note on the report row if one is present. Note whether the module is global, such as a header or footer, or used on high-traffic templates.
If the change may affect important pages, ask Smithworks about a staged rollout or a quick walkthrough. After go-live, review representative pages and confirm layout, buttons, forms, and blog modules still look right.
The documentation points users to the Smithworks hubspot-modules page when they need SW modules added to their HubSpot account, custom Sprocket Rocket-aligned modules, or client portal access after installation.
For other module support, implementation questions, or bug reports, use the Smithworks contact path.
SW Blog Pagination is the listing pager for Smithworks blog index pages. The changelog notes that SW Blog Listing places this module by default for numbered pages and an optional All posts link.
Older themes may still use a legacy custom pager. If pagination behavior matters on a customized blog stack, ask the developer to align the blog templates with the current master.
SW Breadcrumbs is a global breadcrumb module for blog posts and site pages. On blog posts, it can output a visible trail such as Home, blog name, and post title, plus matching BreadcrumbList structured data for search.
Trail mode defaults to Auto. Blog posts and listings can use blog-style trails, while website pages can use a navigation-menu trail. The changelog notes that SW Blog Single Post includes the module above the hero.
SW Breadcrumbs is edited as global content. If spacing or colors look unchanged after a theme update, the saved global module values may still be overriding the new defaults.
Open Global content → SW Breadcrumbs, use Reset to default on the style groups you want refreshed, and publish global content. This keeps updates from unexpectedly overwriting saved global design choices.
SW CTA Simple Bar is for an in-page CTA band or strip. The changelog describes it as supporting an optional icon, content area, and buttons, with module outer and inner styling controls.
Use it when the CTA should read as a horizontal band inside the page rather than a popup, card grid, hero, or form-focused section.
The changelog notes that newer SW CTA Simple Bar instances start with a subtle Module Inner border by default. That inner layer can include border style, weight, color, opacity, and radius settings.
If the CTA bar should not output its own inner border or corner radius, turn Override Module Inner Border off. After updating from an older copy, reopen important CTA bars and confirm the inner border/radius and outer border position settings.
SW FAQs Simple is for visible FAQ sections on HubSpot pages or blog posts. Editors can enter questions directly in the module for one-off FAQ sections or pull reusable FAQ rows from HubDB.
When using HubDB mode, rows can be matched by page path or group key. The module can also output optional FAQPage schema when the visible content and schema settings are appropriate.
SW Share This is listed in the SW module index and changelog as a Smithworks module for social sharing behavior. The public changelog does not provide detailed behavior notes beyond saying it changes less frequently.
If a specific implementation needs exact fields or behavior, use the AI documentation or ask Smithworks for the detailed dated entries.
No FAQs match your search in SW Modules.
