app menu

Author: katarzyna-koltun-mx

content/en/docs/refguide/modeling/menus/app-menu/create-deployment-package-dialog.md

@@ -23,6 +23,32 @@ This is the uncompressed size of the deployment package (*.mda* file). You can f
 Unfortunately, from the error shown on the log during deployment, it is not always clear if the package size is a problem. But if you have issues deploying your app, the package size is one possible cause.
 {{% /alert %}}
 
+## Portable Package
+
+Here, you can decide whether you will create a portable deployment package.
+
+A portable deployment package bundles your application code with all its necessary dependencies into a single, self-contained artifact. For more information about portable packages, see [Portable App Distribution](/developerportal/deploy/portable-app-distribution-deploy/).
+
+{{< figure src="/attachments/refguide/modeling/menus/app-menu/create-deployment-package-dialog/create-portable-package.png" alt="Create Deployment Package dialog with the portable option selected" width="500" >}}
+
+{{% alert color="info" %}}
+Unlike regular packages, portable packages are created as .zip files, in order to make their deployment more convenient for cloud environments. For more information about the structure and contents of the .zip file, see [Reference Guide for Portable Apps Distribution](/developerportal/deploy/portable-apps-distribution/reference/).
+{{% /alert %}}
+
+## Options for Portable Packages
+
+If you are creating a portable package, enter the information outlined below.
+
+## Export Secrets
+
+If you toggle the **Export secrets** option to **Yes**, the created package will include passwords and private constants. Enable or disable this option as required for your application
+
+## File Name
+
+The **Disk location** section displays the location where the deployment package will be saved. This is shown in the **File name** field. This is not editable.
+
+All packages are placed in a **releases** directory inside your app directory. This directory is automatically ignored so that these packages are not committed to the repository. You can always recreate a deployment package (using the Studio Pro version you originally used), so there is no need to put them on the Team Server.
+
 ## Versioned
 
 Here, you can decide whether you will create a versioned deployment package.