Merge branch 'master' into docs/beta-features/widget-variable-types

Author: privatemaker

website/content/docs/beta-features.md

@@ -59,64 +59,7 @@ collections:
 The above config will transform the title field to uppercase and format the date field using `YYYY-MM-DD` format.
 Available transformations are `upper`, `lower`, `date('<format>')`, `default('defaultValue')`, `ternary('valueForTrue','valueForFalse')` and `truncate(<number>)`/`truncate(<number>, '<string>')`  
 
-## Registering to CMS Events
 
-You can execute a function when a specific CMS event occurs.
-
-Example usage:
-
-```javascript
-CMS.registerEventListener({
-  name: 'prePublish',
-  handler: ({ author, entry }) => console.log(JSON.stringify({ author, data: entry.get('data') })),
-});
-```
-
-Supported events are `prePublish`, `postPublish`, `preUnpublish`, `postUnpublish`, `preSave` and `postSave`. The `preSave` hook can be used to modify the entry data like so:
-
-```javascript
-CMS.registerEventListener({
-  name: 'preSave',
-  handler: ({ entry }) => {
-    return entry.get('data').set('title', 'new title');
-  },
-});
-```
-
-## Dynamic Default Values
-
-When linking to `/admin/#/collections/posts/new` you can pass URL parameters to pre-populate an entry.
-
-For example given the configuration:
-
-```yaml
-collections:
-  - name: posts
-    label: Posts
-    folder: content/posts
-    create: true
-    fields:
-      - label: Title
-        name: title
-        widget: string
-      - label: Object
-        name: object
-        widget: object
-        fields:
-          - label: Title
-            name: title
-            widget: string
-      - label: body
-        name: body
-        widget: markdown
-```
-
-clicking the following link: `/#/collections/posts/new?title=first&object.title=second&body=%23%20content`
-
-will open the editor for a new post with the `title` field populated with `first`, the nested `object.title` field
-with `second` and the markdown `body` field with `# content`.
-
-**Note:** URL Encoding might be required for certain values (e.g. in the previous example the value for `body` is URL encoded).
 
 
 ## Remark plugins

website/content/docs/dynamic-default-values.md

@@ -0,0 +1,38 @@
+---
+title: Dynamic Default Values
+group: Fields
+weight: 30
+---
+
+When linking to `/admin/#/collections/posts/new` you can pass URL parameters to pre-populate an entry.
+
+For example given the configuration:
+
+```yaml
+collections:
+  - name: posts
+    label: Posts
+    folder: content/posts
+    create: true
+    fields:
+      - label: Title
+        name: title
+        widget: string
+      - label: Object
+        name: object
+        widget: object
+        fields:
+          - label: Title
+            name: title
+            widget: string
+      - label: body
+        name: body
+        widget: markdown
+```
+
+clicking the following link: `/#/collections/posts/new?title=first&object.title=second&body=%23%20content`
+
+will open the editor for a new post with the `title` field populated with `first`, the nested `object.title` field
+with `second` and the markdown `body` field with `# content`.
+
+**Note:** URL Encoding might be required for certain values (e.g. in the previous example the value for `body` is URL encoded).

website/content/docs/registering-events.md

@@ -0,0 +1,27 @@
+---
+title: Registering to CMS Events
+weight: 80
+group: Customization
+---
+
+You can execute a function when a specific CMS event occurs.
+
+Example usage:
+
+```javascript
+CMS.registerEventListener({
+  name: 'prePublish',
+  handler: ({ author, entry }) => console.log(JSON.stringify({ author, data: entry.get('data') })),
+});
+```
+
+Supported events are `prePublish`, `postPublish`, `preUnpublish`, `postUnpublish`, `preSave` and `postSave`. The `preSave` hook can be used to modify the entry data like so:
+
+```javascript
+CMS.registerEventListener({
+  name: 'preSave',
+  handler: ({ entry }) => {
+    return entry.get('data').set('title', 'new title');
+  },
+});
+```