We're rolling out improvements that make Makeswift faster, clearer, and more flexible to use — whether you're publishing changes, logging in, or building new sites with our open-source design system. From better visibility into edits to smoother localization workflows, here's what's new in Makeswift.
📝 Publish dialog now shows who last edited each change
We’ve updated the publish dialog to show who last edited each resource and when it was last updated. This is helpful when collaborating in a team, and is our first step towards even more granular change tracking in the future.
🔐 Multiple login methods, fewer duplicate accounts
Users can now link multiple login methods, like email, Google, BigCommerce and SAML, to a single account. This makes it easier to log in using the method that works best for you, while reducing the chances of duplicate accounts at signup. You can add or remove login methods from your account settings and we’ll now show you the last login method you used, so it’s easier to pick up where you left off. This update helps prevent duplicate accounts and gives you more flexibility in how you access Makeswift.
If you’re using Makeswift to design your Catalyst storefront, this means you can now also directly log in at app.makeswift.com/login without needing to go through the BigCommerce control panel.
⚙️ Draft mode updates and localization workflow with runtime v0.24.0
Version 0.24.0 of the Makeswift runtime includes editing performance improvements and revamps the way we handle Next.js draft mode.
For details on upgrading, see our Upgrading to 0.24.0 documentation.
Additionally, this version introduces new fallback behavior for localized pages. Now, requests to localized pages will default to displaying the content of the base locale page if the localized content is not available. Previously, these requests would result in a 404. This change is also accompanied by a new builder experience for creating localized variants of your pages.
Check out our updated localization guides for a more hands-on look:
🎨 Introducing VIBES: a new kind of design system for the modern web
We’re building websites differently now — with components, not templates. But most design systems haven’t caught up. They’re built for apps, not websites. That’s why we created VIBES.
VIBES is an open-source design system made for expressive, high-performance websites. It’s built with developers in mind: copy/paste simplicity, optimized for Next.js, and focused on real-world interfaces, not just UI primitives. Unlike traditional systems, VIBES is structured around primitives and sections so developers can move faster without sacrificing aesthetic or performance.
Instead of relying on static CSS or generic UI kits, VIBES gives you streamable, plug-and-play components designed specifically for brand-forward websites and storefronts. They’re fast, flexible, and easy to drop into your stack, whether you’re just getting started or scaling a composable frontend.
Our first release, the Soul VIBE, is now live. It’s a growing collection of layout-ready components and design files you can use, remix, or build on. We’re excited to invest in the open-source community, joining the developers that are reshaping how the modern web is built, one component at a time.
💻 Check out the VIBES GitHub repo
Improvements and Fixes
This cycle we focused on fixing high-priority customer issues and improving internal processes. Key updates include resolving layout shift problems, improving Vercel integration, and refining bug reporting templates.
Improvements
- Publishing Callbacks: Introduced a runtime callback in MakeswiftApiHandler to keep “whitelisted” routes in sync after each publish, reducing manual polling for high-traffic sites.
- Troubleshooting Guides: Published a new guide “Layout shift on initial page load”, to help users investigate and fix a layout shift caused by a React update on page hydration.
Fixes
- Investigated and addressed multiple high-priority issues on both BigCommerce and customer sites related to layout shifts.
- Investigated and provided a workaround for the Vercel firewall issue related to Smartling requests being blocked by a customer’s firewall rules.
- Addressed customer issues in the builder with unexpected page reloads by recommending correct data fetching practices over Server Actions.
- Solved CSS and Toast notification bugs affecting Catalyst, improving overall UI reliability.
- Identified and resolved mismatched user IDs affecting OCC database integrity, restoring seamless user authentication.
