GITBOOK-171: Demos added on Version/Release Management and Modules page

adnanqaops · gitbook-bot · commit 9d76939f8d0a · 2024-07-30T12:26:50.000Z
diff --git a/docs/build-applications/create-a-new-app/modules.md b/docs/build-applications/create-a-new-app/modules.md
@@ -134,6 +134,10 @@ When an app uses a module, you can configure how the current app reacts to the m
 
 The following example conducts event tests in the **Event Test** section.
 
+### Demo
+
+{% embed url="https://demos.lowcoder.cloud/demo/WtS5m4F_GPcJsUpRLfwRI" %}
+
 ## Permissions
 
 End users are automatically granted permission to view modules in apps or other modules they have viewing permissions with. If you are an editor and wish to use a module in external apps, you should at least have the viewer's role of that module.&#x20;
diff --git a/docs/build-applications/create-a-new-app/version-and-release-management.md b/docs/build-applications/create-a-new-app/version-and-release-management.md
@@ -25,6 +25,10 @@ You can restore your current draft to a history version.
 
 <figure><img src="../../.gitbook/assets/App Editor  App Editing History.png" alt=""><figcaption></figcaption></figure>
 
+### Demo :&#x20;
+
+{% embed url="https://demos.lowcoder.cloud/demo/clye1mf9v0rpsthf7eufsfmrm" %}
+
 ## Release management
 
 Apps are usually upgraded on a regular basis to include new features, improve business processes, and correct failures. However, the development of a new version of an app takes time and you need to ensure that user experience is not affected during this progress.
