Frontend Studio Releases

This feature improves frontend observability capabilities because it helps you with performance monitoring and debugging.

We updated the order of the Developer area in the Studio so that the most used areas appear first, to allow for faster and easier navigation.

This helps you to discard builds that you do not want deployed to your production site.

When you delete a build, both the backend build and the frontend build from Netlify are deleted.

The following usability enhancements and bug fixes are now available in the Studio.

• In the Site builder and Dynamic pages areas, you can no longer schedule, make live, or mark as default a page version that contains Frontend components that are missing a required field. This helps reduce errors and consequent issues on your website. Previously, you were only warned not to publish the page version.
• In the Deployment area, when clicking Deploy frontend and backend in the Staging or Production section, the dialog displays the builds that you can deploy for that environment based on your Netlify settings. If a build cannot be deployed in production, it appears in the list of the production builds but it is greyed out. This ensures that you can only release deployable builds, thus reducing errors.
• In the Site builder area, when working in the Staging or Development environment, you can now use a checkbox to display only the page folders relevant for that environment. This helps you identify the page folders you can edit.
• From the user account menu you can now see both your name and email address. Additionally, the links to the Merchant Center, Netlify, and Humio now appear as buttons.

• You can now use spaces in page version names.
• When a page version is waiting for review, you can now see the Frontend component settings.
• In the email notification requesting a page version review, the link to the page now contains the project.
• The page builder's UI now appears correctly. Previously, some visualization problems occurred.

• Collaborator
• Developer
• Junior developer
• Viewer

These new roles let you assign more granular permissions to users and improve collaboration without compromising access control.

To align with the new roles, we've updated the assigned roles for existing users as follows:

• The Lead Editor role is now called Editor.
• The legacy Editor role is now called Collaborator.

• You can now choose to deploy only backend builds.

You can now access and restore previous versions of page versions, schemas, and component groups that were saved up to 90 days before. You can do it from:

• The Page builder for page versions
• The Schema editor for schemas
• The Component group builder for component groups

Accessing version history directly from the builder/editor speeds up the inspection and restoration of previous versions of your work.

This saves you time and eases your workflows because you no longer need to access Netlify to see your deploy previews or share the preview links.

• Added the API Keys area, where you can manage your API keys.
• The Continuous Integration area now support builds from custom CI environments.

You can now collaborate with teammates by commenting on page versions, component groups, and page templates. You can also tag users in comments and assign them to review page versions.

• Sandboxes is no longer available in the Developer area.
• From Deployment in the Developer area, you can now deploy the frontend and backend of your website at the same time.
• Using the Project schema and the Project area, you can now manage additional project configurations, such as API credentials.

Our documentation is updated to reflect the changes.

This speeds up and facilitates the process to create Frontend components.

With this preview, you can see the data retrieved from a data source according to the filters you set, without having to check the preview of the entire page.

From the commercetools system status page, you can also subscribe to be notified of status updates.

The old commercetools Frontend system status page will no longer be available.

{/* vale commercetools.Acronyms = NO */}

Protecting your privacy is crucial for our business, and we're committed to being a responsible, trustworthy custodian of our personal information. For this reason, we've added cookie consent to the Studio.

We're asking for cookie consent mainly for two tools: FullStory and UserGuiding.

FullStory allows us to understand how you’re using the Studio. We don't gather personal information. We only collect usage information to understand how to improve our product and deliver the best user experience.

UserGuiding allows us to create in-app notifications about the latest releases, create tutorials on using those features, and help onboard new users. We don't gather personal information, and it's only to deliver information about the Studio to you.

Cookie settings are of two types:

• Strictly necessary: Enables UserGuiding, but FullStory stays turned off.

• Performance: Enables both UserGuiding and FullStory.

To change your cookie settings, reactivate the cookie consent banner by clearing the cookies from your browser settings. Then, select your preference using the cookie consent banner.

You can find our privacy notice for the Studio below.

This way, if you create a page version that can be reused in your commercetools Frontend project, you can easily make it a template.

Previously, to make a copy of a page folder, you had to manually create a page folder and configure it with the same settings and page versions as the page folder you wanted to copy.

Before, the commercetools Frontend support team was in charge of importing bulk redirects, now you can do it autonomously. This speeds up the migration process to commercetools Frontend.

In the page builder, you can now move between page versions using the page versions drop-down.

Apart from the above feature, here are other two enhancements coming with this release:

• The sandbox debugging modal is now consistent with the Studio design system. The transient sandboxes will appear grayed out while they're unusable.
• You'll now see the information about each role in the invitation drop-down when inviting a user to the Studio. This will help you decide which role to assign to your new user.

Apart from the above feature, here are some other enhancements coming with this release:

• Clicking on Save or Publish in the page builder will keep you in the page builder. You can save your changes and complete other actions without leaving the site builder.
• You can now access the Merchant Center login page by clicking on the profile icon and selecting Merchant Center.
• You'll see an information notification within the preview of a component schema to clarify the correct usage.
• You can now duplicate the component setting inputs of a group type field.
• The color of primary buttons is now updated to commercetools brand green.
• All documentation links now point to the commercetools Frontend documentation website.

• We fixed a bug on translatable fields containing links. If the field was within a group and was not the first field, the link was not saved.
• We fixed a bug on the schema editor buttons that were displayed incorrectly on small screens.

The release notes published before 4 November 2022 are archived below.