diff --git a/docs/24.2/design.html b/docs/24.2/design.html index 1a08dcb..56c909c 100644 --- a/docs/24.2/design.html +++ b/docs/24.2/design.html @@ -740,7 +740,7 @@
If a design requires resources from external servers, e.g. from a Content Delivery Network (CDN), two settings must be checked in the BSI Customer Suite and, if necessary, adjusted according to the needs of the design. The settings can be configured by a user with the appropriate permissions in the BSI Customer Suite administration.
++ + | ++Observe the notes on the integration of CSS and scripts in chapter Control Attributes. + | +
The HTTP headers including CSP settings for CX landing pages and websites are configured here. These are relevant for displaying the landing pages and websites in the end user’s browser.
+The HTTP headers including CSP settings for the index page of the BSI Customer Suite are configured here. This includes the CX Content Editor. This setting overrides the server-side configured default values for CSP.
+This setting should be configured more restrictively than the setting for landing pages and websites above. Only what is absolutely necessary for error-free display in the content editor should be allowed. As a rule, styles and fonts are allowed, but not JavaScript.
++ + | ++The CSP settings configured here apply to the entire BSI Customer Suite GUI, not just the CX Content Editor. + | +
While dragging a content element into the content area, you will notice blue lines and blue areas. These areas are called dropzones and identify areas where certain content elements can be placed. Each dropzone has a list of allowed content elements that are specified in the design.
A dropzone is defined by adding the attribute data-bsi-dropzone
to an HTML container element (e.g. <div>
or <table>
).
@@ -1177,7 +1228,7 @@