Frequently Asked Questions - SW Sprocket Rocket Modules

Version mismatch means the module needs a technical consistency check before the report result can be relied on. It is a review signal, not a request for you to edit the module. Contact Smithworks support and include the portal or website name plus the affected item.

Not in master means the item is not part of the standard maintained Smithworks library used for the report comparison. It may be custom for your website, supplied by another vendor, or intentionally maintained outside that library. Confirm who owns and supports the item before approving changes. The status does not mean the item should be deleted.

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 you approve an update, ask for a short plan that covers:

• Which pages, templates, or sitewide areas use the module
• What visitors or editors may notice after the update
• When the work will happen and whether publishing should avoid a busy period
• How the current state will be backed up, where the update will be tested, and how the result will be checked
• Who at Smithworks owns the update and your follow-up questions

You should understand the business impact and review plan without needing to manage the technical work yourself. Use the Smithworks client portal to open the report, then confirm the plan with the named Smithworks contact.

Visit the Smithworks HubSpot modules page to request access. Choose an existing SW Module when the available module already fits your content and design needs. Request a custom module when your requirements cannot be handled cleanly by the existing options. Describe the page goal and required behavior so the request can be evaluated against the right module 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.

A saved SW Breadcrumbs module can keep its existing style values instead of adopting updated defaults. Open the Breadcrumbs module instance on the page or template and review the saved spacing and color settings. Before resetting anything, note the custom values you want to keep. Use Reset to default only on the specific style group you want to refresh, then preview the result before publishing.

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.

SW CTA Simple Bar includes a subtle inner border by default to help the content area stand apart from the surrounding band. To remove it, open Style → Module background and turn off Override Module Inner Border. Preview the bar afterward to make sure its remaining background and corner settings still fit the page. The border can be removed without recreating the module.