Editable Regions, Font Control and Scheduled Publishing

January, 22 2025

Layers panel inside of the Makeswift builder

Editable Regions for any page through new APIs: getComponentSnapshot, <MakeswiftComponent>, and <Slot>

Your team can now bring visual editing to any of your site’s pages, even if they weren’t created in Makeswift. With the new getComponentSnapshot and <MakeswiftComponent> APIs, developers can now define editable regions on pages that non-technical teams can customize in the Makeswift editor. This enables you to bring visual editing to your entire site, and unlocks powerful use cases such as:
  • Product Detail Pages (PDPs) for ecommerce: You can now have dynamic product pages that have unique, visually editable regions — all without having to manually create these pages in Makeswift.
  • Builtin elements across your site: Define built-in elements, like headers and footers, that are visually editable and shared across multiple pages, but can’t be deleted from the Makeswift editor. This gives teams control to update content while maintaining the integrity and consistency of the design.



These APIs also have first-class support for localization, so you can edit across your site’s locales with ease.



How it works: Your developer will need to use the new getComponentSnapshot and <MakeswiftComponent> APIs to set up your pages to be editable. If your developer has completed this, you can simply navigate to these pages in Makeswift and start editing without touching any code. If not, you’ll just need your developer’s help to configure the pages. See our docs for more details.



New Controls

We’ve introduced a new Font control that allows users to select and manage fonts outside of rich text fields. Using the Font control, developers can now give site editors a visual interface to customize font family, style, and weight in any context.



We are also releasing a new ‘Group’ control that will replace ‘Shape’. This ‘Group’ control offers an improved visual hierarchy for grouped controls when rendered in the Makeswift builder, along with new options for specifying the group label and preferred layout. For more details, check out our docs.



Scheduled Publishing

The ability to schedule a set of changes to your site to go out at a later time is now available. It works similarly to our normal publishing workflow, but with the ability to set a time.



Our “Scheduled” section of the publish dialog allows you to expand, rename, cancel, or publish immediately a scheduled publish.



Layers panel inside of the Makeswift builder



While you can schedule multiple publishes at a time, we do not recommend publishing different versions of the same page across multiple scheduled publishes, as it can get confusing.

We believe this feature is most useful for marketing launches and blog posts, but we look forward to hearing how you use it.



For more information, check out our docs.



Improvements and Fixes

Improvements

  • Layers panel has been renamed to Elements panel.
  • A new deployment option is now available with Netlify — view our docs.
  • Added a confirmation dialog for plan upgrades and downgrades, ensuring users are notified when their plan is successfully updated.
  • Added a reset date to monthly publishes, so users can easily see when their publish limits will reset.

Fixes

  • Resolved a performance issue where scrolling through medium-sized pages on the canvas caused excessive CPU usage and disconnection from the Makeswift builder. This was due to recent changes in the v0.22.0 runtime, which was making more extensive use of the getElementId selector.
  • Introduced a confirmation dialog when users publish content live to prevent exceeding publish limits. Previously, the publish limits were delayed, causing users to hit their limit without warning.
  • When errors occurred in Files Manager, it had the potential to cause the entire app to crash. We added an error boundary to prevent this from happening.
  • Fixed a bug where users couldn’t take pages offline when reaching their publishing limit. Now, users can take pages offline regardless of their publishing limit status.
  • Fixed a visual bug in the builder where the toggle did not adjust properly for “pages” and “layers” when the sidebar was resized.
  • Removed the folder name from being displayed when a component is selected in the builder, as it was obscuring most of the component's name.
  • Fixed a bug where the default value of the select control was not appearing in the panel when a user registered a component. This issue has now been resolved, and the default value will correctly display.
  • Fixed an issue with the Smartling integration where translation jobs would result in error due to immediate job initiation after the text upload. Now, we wait for processing to complete before retrying, reducing failure rates for large translations.