SW 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.

An older module may remain so existing pages keep working while a newer replacement is used for new pages or 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.

Use SW Blog Pagination on blog index pages that need numbered pagination and, when configured, an optional All posts link.

Use SW Breadcrumbs when a site needs a visible breadcrumb trail on blog posts or website pages, with matching BreadcrumbList structured data where supported.

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.

Use SW CTA Simple Bar for an in-page call-to-action band with optional icon, message content, and buttons.

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.