add more info to automation actions

Author: jannes-io

src/app/layout.tsx

@@ -47,6 +47,7 @@ const RootLayout = ({
     </main>
   </div>
 </div>
+<hr className='mt-6 mb-6' />
 <footer className="text-small">
   forumify documentation&nbsp;
   <a href="https://creativecommons.org/licenses/by/4.0/" target="_blank">CC BY 4.0</a>.

src/app/navigation.json

@@ -24,6 +24,11 @@
         "path": "cms",
         "label": "CMS"
       },
+      {
+        "type": "route",
+        "path": "automation",
+        "label": "Automation"
+      },
       {
         "type": "route",
         "path": "calendar",

src/app/user-manual/admin-panel/page.mdx

@@ -45,9 +45,9 @@ On the configuration page you can modify basic settings regarding your instance.
 - General: Basic information regarding your forum,
 - Users: Any settings related to user registration and forum profiles,
 - Spam Protection: reCAPTCHA settings.
-- Emails*: Configuration for your e-mail server.
+- Emails\*: Configuration for your e-mail server.
 
-**Email settings are not available on forumify cloud.*
+*\*Email settings are not available on forumify cloud.*
 
 ### <UserList /> Users
 
@@ -73,5 +73,5 @@ Here you can find:
 - <Link href="/user-manual/menu-builder">Menu Builder</Link>,
 - Plugins,
 - Reactions,
-- <link href="/user-manual/security">Roles</Link>,
+- <Link href="/user-manual/security">Roles</Link>,
 - Themes.

src/app/user-manual/automation/page.mdx

@@ -19,7 +19,6 @@ Each automation consists of 3 parts:
     If you are seeing any triggers, conditions or actions that are not in the documentation below, they are probably added by a plugin, and you should refer to their documentation.
 </Alert>
 
-
 ### Trigger
 
 The trigger decides when to execute the action. Triggers also provide the payload which is available in the condition and action.
@@ -68,6 +67,23 @@ Learn more: <a href="https://symfony.com/doc/current/reference/formats/expressio
 
 Sends a POST request to the given webhook URL.
 
+For example, to send data to Zapier:
+
+- **Webhook URL**: The webhook URL given by Zapier (Catch Raw Hook)
+- **Data**: The data sent to Zapier, for example with a Doctrine Topic trigger:
+
+```twig
+{{ {
+    topic: entity.title,
+    content: entity.firstComment.content
+}|json_encode|raw }}
+```
+
+<Alert severity="info">
+    The example creates the data object, then JSON encodes it and dumps the raw output. This method is recommended since it
+    takes care of escaping quotes and slashes which may break your JSON.
+</Alert>
+
 #### HTTP Request
 
 Call any external API using a HTTP request.

src/app/user-manual/page.mdx

@@ -5,6 +5,7 @@ import Link from 'next/link';
 - <Link href="/user-manual/admin-panel">Admin Panel</Link>
 - <Link href="/user-manual/forum">Forums</Link>
 - <Link href="/user-manual/cms">Content Management System</Link>
+- <Link href="/user-manual/automation">Automation</Link>
 - <Link href="/user-manual/calendar">Calendar</Link>
 - <Link href="/user-manual/menu-builder">Menu Builder</Link>
 - <Link href="/user-manual/automation">Automation</Link>

src/app/user-manual/security/page.mdx

@@ -51,8 +51,8 @@ There are 3 roles within forumify that can not be deleted or modified:
 - **Super Admin**: The Super Admin role bypasses any and all security checks.
 It's the most powerful role in your system and should be treated with extreme care.
 Only the website's owner should have this role. It is given to the user who installed the platform.
-- **User**: The User role is automatically assigned to any user that is logged in.
-- **Guest**: The Guest role is automatically assigned to any user that is *not* logged in.
+- **User**: The User role is automatically assigned to every user that is logged in.
+- **Guest**: The Guest role is automatically assigned to every user that is *not* logged in.
 
 So if you want to grant access to **all** users, all you have to do is assign the permission to both *User* and *Guest* roles.
 
@@ -61,7 +61,7 @@ So if you want to grant access to **all** users, all you have to do is assign th
 The most common security mechanism you will see in action is ACL. ACL allows you to enable an action for each role.
 
 ACLs are not managed in the Role's setting, but they are managed in the entity that defines them. 
-Usually when you see a <LockSimple /> button, you are editing the access control for that entity.
+Usually when you see a <LockSimple /> button, you are editing the Access Control List for that entity.
 Entities that are governed by ACLs define their own permissions.
 For example, a forum defines the permissions "view", "create topic", "create comment",...