Added custom collection and muted document parameter.

developer/nodes-system/node_type_fields.rst

@@ -33,6 +33,7 @@ This following fields stores simple data in your custom node-source database tab
 - YAML code
 - Many to many join
 - Many to one join
+- Custom collection
 
 .. note ::
     *Single geographic coordinates* field stores its data in JSON format. Make sure you
@@ -116,3 +117,23 @@ You must fill the *default values* field for these two types.
     orderBy:
         - field: slug
           direction: ASC
+
+Custom collection
+^^^^^^^^^^^^^^^^^
+
+Last but not least, you can create a custom collection field to store read-only data using
+a dedicated *Symfony* ``AbstractType``.
+
+You must fill the *default values* field for this type:
+
+.. code-block:: yaml
+
+    # AbstractType class name
+    entry_type: "Themes\MyTheme\Form\FooBarType"
+
+You must understand that *custom collection* data will be stored as JSON array in
+your database. So you won’t be able to query your node-source using this data.
+
+In your ``FooBarType``, you’ll be able to use *Symfony* standard fields types and
+**Roadiz** non-virtual fields too such as ``MarkdownType``, ``JsonType``, ``YamlType``.
+

developer/themes/display_documents.rst

@@ -63,6 +63,7 @@ Audio / Video options
 * **autoplay** (boolean)
 * **controls** (boolean)
 * **loop** (boolean)
+* **muted** (boolean)
 * **custom_poster** (string): URL to a image to be used as video poster
 
 You can use **multiple source files** for one video document or audio document.
@@ -126,7 +127,7 @@ You can find more details in `our API documentation <http://api.roadiz.io/RZ/Roa
 * If document is an **image**: ``getDocumentByArray`` method will generate an ``<img />`` tag with a ``src`` and ``alt`` attributes.
 * If it’s a **video**, it will generate a ``<video />`` tag with as many sources as available in your document database. Roadiz will look for same filename with each HTML5 video extensions (filename.mp4, filename.ogv, filename.webm).
 * Then if document is an external media **and** if you set the ``embed`` flag to ``true``, it will generate an iframe according to its platform implementation (*Youtube*, *Vimeo*, *Soundcloud*).
-* Get the external document URI (the one used for creating iframe for example) with ``(document|embedFinder).source`` twig command. 
+* Get the external document URI (the one used for creating iframe for example) with ``(document|embedFinder).source`` twig command.
 
 Manage global documents
 -----------------------