Page Builder

Addressed Several Page Builder-Related Issues (#3007external link)

With this release, we’ve again shipped a new batch of Page Builder-related fixes and improvements. The following are some of the more important ones.

Theme Border Colors Now Applied Correctly

Prior to this release, in the page editor, upon adding a colored border to an existing page element, if the selected color was defined via theme, it would not get applied correctly. Instead, the default black color would be used.

We’ve taken care of this, so you can expect theme (and non-theme) colors to be correctly applied to a page element’s border.

Resolved Interactivity Issues on Animated Page Elements

In the page editor, when a page element had an animation enabled, it would lose usual interactivity-related features. For example, users would not be able to type text into text-based page elements, nor drop page elements above or below the animated one.

Both interactions now work correctly when an element has animation enabled.

Image Element Now Renders the Image Usingsrcset

When used, the existing image page element now renders the actual image using the srcset HTML attributeexternal link, not src. This greatly improves the overall website performance because, depending on the user’s device screen, browsers serve the image size that’s considered to be most optimal.

Page Title Correctly Saved When Pressing the Enter Key

Prior to this PR, in the page editor, if a user pressed Enter key once they typed a new page title, the new title would not get saved, despite the fact that the user would get presented with a success message.

This issue has now been addressed.

Elements Can Now Be Moved Up and Down on the Canvas (Drag and Drop)

In the page editor, reordering existing page elements via drag and drop method now works correctly.


Ability to Define Multiple Production Environments viawebiny.application.ts(#3014external link)

Upon running the webiny deploy command, when prod is passed as the environment name, a Webiny project is deployed in the so-called production deployment modeexternal link.

But, if a user wanted to use the same mode for, say, staging, that would not be easily possible.

That’s why we’re introducing the productionEnvironments parameter for all project applications, which can be utilized in their respective webiny.application.ts configuration files. For example:


Note that when specifying additional production environments, they should be specified across all project applications, meaning:

  1. apps/core/webiny.application.ts
  2. apps/api/webiny.application.ts
  3. apps/admin/webiny.application.ts
  4. apps/website/webiny.application.ts