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 @@

Design Documentation: BSI CX 24.2

BSI Product Development
-Version Date 2024-02-22 +Version Date 2024-06-21
Covered Topics
@@ -754,9 +754,15 @@

Design Documentation: BSI CX 24.2

  • 1.5. Designs since BSI CX 22.0
  • 1.6. File format
  • 1.7. Content Editor
  • -
  • 1.8. Structure Reference
  • -
  • 1.9. Dropzones
  • -
  • 1.10. Groups
  • +
  • 1.8. Content Security Policy (CSP) + +
  • +
  • 1.9. Structure Reference
  • +
  • 1.10. Dropzones
  • +
  • 1.11. Groups
  • 2. design.json @@ -1134,7 +1140,52 @@

    1.7. Conten

  • -

    1.8. Structure Reference

    +

    1.8. Content Security Policy (CSP)

    +
    +

    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.

    +
    +
    +
    +

    1.8.2. HTTP headers for the index page of the BSI Customer Suite

    +
    +

    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. +
    +
    +
    +
    +
    +

    1.9. Structure Reference

    The file design.html contains the frame of the design and must include at least one outermost dropzone. It must contain valid, XHTML conform HTML with Doctype, <html>, <head> and <body> tags.

    @@ -1150,7 +1201,7 @@

    1

    -

    1.9. Dropzones

    +

    1.10. Dropzones

    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 @@

    1.9. Dropzones

    -Problems can occour when placing a dropzone into a link or button element. +Problems can occur when placing a dropzone into a link or button element. In this case, we recommend using a style. @@ -1185,7 +1236,7 @@

    1.9. Dropzones

    -

    1.10. Groups

    +

    1.11. Groups

    @@ -5992,7 +6043,7 @@
    diff --git a/docs/24.2/design.pdf b/docs/24.2/design.pdf index a18b0a5..1f36eb0 100644 Binary files a/docs/24.2/design.pdf and b/docs/24.2/design.pdf differ