diff --git a/Documentation/ContentBlocks/Carousel.rst b/Documentation/ContentBlocks/Carousel.rst
index 6cedbc0..afea303 100644
--- a/Documentation/ContentBlocks/Carousel.rst
+++ b/Documentation/ContentBlocks/Carousel.rst
@@ -89,7 +89,11 @@ Frontend template: Fluid template for a Content Block with a Collection
 Line 1: We use `Asset.css ViewHelper <f:asset.css> <https://docs.typo3.org/permalink/t3viewhelper:typo3-fluid-asset-css>`_
 to load the provided CSS file only if a carousel is displayed on that page. The
 `Asset collector <https://docs.typo3.org/permalink/t3coreapi:asset-collector>`_
-takes care that the file is not loaded more then once per page.
+takes care that the file is not loaded more then once per page. All Fluid
+ViewHelpers prefixed with `cb:` are provided by :composer:`friendsoftypo3/content-blocks`
+they are therefore not listed in the official View Helper reference. The inline
+ViewHelper `cb:assetPath()` resolves paths to the `asset` folder of the current
+content block.
 
 Line 2: We use the `Asset.script ViewHelper <f:asset.script> <https://docs.typo3.org/permalink/t3viewhelper:typo3-fluid-asset-script>`_
 to load the JavaScript file the same way.
@@ -99,18 +103,18 @@ to loop through each item. We then render a button for each carousel item.
 
 Line 11: We loop the items a second time to now display all carousel slides.
 
-Line 13: As the field of type "Files" may contain more then one file, the
-variable {data.carousel_items} contains an array. We loop through the array
-and display all images found.
-
-Line 14: We use the `Image ViewHelper <f:image> <https://docs.typo3.org/permalink/t3viewhelper:typo3-fluid-image>`_
+Line 13: The field `image` was defined with option `relationship: manyToOne` in
+the :ref:`config.yaml <carousel-configuration>` it can therefore only contain
+one image at maximum. As supplying an image is also mandatory `minitems: 1`
+we can be sure there is always exactly one image. And just use the
+`Image ViewHelper <f:image> <https://docs.typo3.org/permalink/t3viewhelper:typo3-fluid-image>`_
 to display the image.
 
-Line 18: As the field `{item.description}` is of type Textarea with rich-text
+Line 16: As the field `{item.description}` is of type Textarea with rich-text
 enabled we have to use the `Format.html ViewHelper <f:format.html> <https://docs.typo3.org/permalink/t3viewhelper:typo3-fluid-format-html>`_
 to properly display it.
 
-Line 25, 29: The previous and next buttons use localized text for their labels.
+Line 23, 27: The previous and next buttons use localized text for their labels.
 We use the `Translate ViewHelper <f:translate> <https://docs.typo3.org/permalink/t3viewhelper:typo3-fluid-translate>`_
 to translate these labels and a view helper provided by the Content Block
 extension to determine the path to the language file.
@@ -128,4 +132,51 @@ should be displayed in the TYPO3 backend in the Page module:
     :linenos:
 
 The same fields like for the frontend template are available and the same
-ViewHelpers can be used.
+ViewHelpers can be used. However we display them in a simplified form.
+
+Line 1: We are using the layout `Preview`, which already gives some structure to
+the display of the backend element:
+
+..  figure:: /Images/ContentBlocks/BackendLayout.png
+    :alt: Screenshot of a Content Block in the TYPO3 Backend, demonstrating the sections of the layout
+
+    The sections of a content element backend layout: (1) Header, (2) Content, (3) Footer
+
+The line on the very top with the name of the content element, the icon and the
+edit buttons is generated by TYPO3 automatically and cannot be influenced by
+a backend template. It uses the label `title` defined in :file:`language/labels.xlf`
+and the icon :file:`assets/icon.svg`.
+
+As always we use the `Layout ViewHelper <f:layout> <https://docs.typo3.org/permalink/t3viewhelper:typo3fluid-fluid-layout>`_
+to select the `Preview` layout.
+
+Each section is declared using the `Section ViewHelper <f:section> <https://docs.typo3.org/permalink/t3viewhelper:typo3fluid-fluid-section>`_.
+
+Line 10: We once more use the
+`For ViewHelper <f:for> <https://docs.typo3.org/permalink/t3viewhelper:typo3fluid-fluid-for>`_
+to loop through all items of the slider and display them one by one.
+
+Line 21: Labels can and should also be localized in the backend. To not lose
+context we prefixed all labels to be used in the backend with `backend.`.
+
+..  tip::
+    See also chapter `Backend Preview in the Content Blocks
+    manual <https://docs.typo3.org/permalink/friendsoftypo3/content-blocks:api-backend-preview>`_.
+
+
+..  _carousel-assets:
+
+Content Block specific assets
+=============================
+
+The assets in folder :directory:`assets` can be loaded in the
+:ref:`Frontend Template <carousel-fluid>`. They will only be loaded when the
+Content Block is loaded on the current page. If compression
+(:ref:`config.compressCss <t3tsref:confval-config-compresscss>`,
+:ref:`config.compressJs <t3tsref:confval-config-compressjs>`) and concatenation
+(:ref:`config.concatenateCss <t3tsref:confval-config-concatenatecss>`,
+:ref:`concatenateJs <t3tsref:confval-config-concatenatejs>`) are enabled
+all assets are compressed and concatenated into as few as possible small asset
+files.
+
+This also has the advantage that your JavaScript is only loaded if needed.
diff --git a/Documentation/Images/ContentBlocks/BackendLayout.png b/Documentation/Images/ContentBlocks/BackendLayout.png
new file mode 100644
index 0000000..f261d88
Binary files /dev/null and b/Documentation/Images/ContentBlocks/BackendLayout.png differ