mendix · ester-nl · Apr 25, 2025 · Apr 25, 2025 · Apr 25, 2025 · Apr 25, 2025
diff --git a/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-10/_index.md b/content/en/docs/apidocs-mxsdk/apidocs/studio-pro-10/_index.md
@@ -0,0 +1,11 @@
+---
+title: "APIs for Studio Pro 10"
+url: /apidocs-mxsdk/apidocs/apis-for-studio-pro-10/
+no_list: false
+description_list: true
+description: "Provides the documentation of APIs for Studio Pro 10, including Extensibility API and Mendix Runtime API."
+weight: 5
+linktitle: "Studio Pro 10"
+---
+
+Mendix offers the following APIs for Studio Pro 10:
diff --git a/...cs/studio-pro/extensibility-api/_index.md → ...studio-pro-10/extensibility-api/_index.md b/...cs/studio-pro/extensibility-api/_index.md → ...studio-pro-10/extensibility-api/_index.md
diff --git a/...io-pro/extensibility-api/csharp/_index.md → ...pro-10/extensibility-api/csharp/_index.md b/...io-pro/extensibility-api/csharp/_index.md → ...pro-10/extensibility-api/csharp/_index.md
diff --git a/...csharp/extensibility-api-howtos/_index.md → ...csharp/extensibility-api-howtos/_index.md b/...csharp/extensibility-api-howtos/_index.md → ...csharp/extensibility-api-howtos/_index.md
diff --git a/...harp/extensibility-api-howtos/add-menu.md → ...harp/extensibility-api-howtos/add-menu.md b/...harp/extensibility-api-howtos/add-menu.md → ...harp/extensibility-api-howtos/add-menu.md
diff --git a/...pi-howtos/build-todo-example-extension.md → ...pi-howtos/build-todo-example-extension.md b/...pi-howtos/build-todo-example-extension.md → ...pi-howtos/build-todo-example-extension.md
diff --git a/...ibility-api-howtos/create-context-menu.md → ...ibility-api-howtos/create-context-menu.md b/...ibility-api-howtos/create-context-menu.md → ...ibility-api-howtos/create-context-menu.md
diff --git a/...bility-api-howtos/create-dockable-pane.md → ...bility-api-howtos/create-dockable-pane.md b/...bility-api-howtos/create-dockable-pane.md → ...bility-api-howtos/create-dockable-pane.md
diff --git a/...ility-api-howtos/create-menu-extension.md → ...ility-api-howtos/create-menu-extension.md b/...ility-api-howtos/create-menu-extension.md → ...ility-api-howtos/create-menu-extension.md
diff --git a/...ty-api-howtos/create-microflow-service.md → ...ty-api-howtos/create-microflow-service.md b/...ty-api-howtos/create-microflow-service.md → ...ty-api-howtos/create-microflow-service.md
diff --git a/...-howtos/create-microflows-calculations.md → ...-howtos/create-microflows-calculations.md b/...-howtos/create-microflows-calculations.md → ...-howtos/create-microflows-calculations.md
diff --git a/...ility-api-howtos/create-modal-web-view.md → ...ility-api-howtos/create-modal-web-view.md b/...ility-api-howtos/create-modal-web-view.md → ...ility-api-howtos/create-modal-web-view.md
diff --git a/...ibility-api-howtos/export-an-extension.md → ...ibility-api-howtos/export-an-extension.md b/...ibility-api-howtos/export-an-extension.md → ...ibility-api-howtos/export-an-extension.md
diff --git a/...ity-api-howtos/interact-with-model-api.md → ...ity-api-howtos/interact-with-model-api.md b/...ity-api-howtos/interact-with-model-api.md → ...ity-api-howtos/interact-with-model-api.md
diff --git a/...nsibility-api-howtos/untyped-model-api.md → ...nsibility-api-howtos/untyped-model-api.md b/...nsibility-api-howtos/untyped-model-api.md → ...nsibility-api-howtos/untyped-model-api.md
diff --git a/...tensibility-api-reference-guide/_index.md → ...tensibility-api-reference-guide/_index.md b/...tensibility-api-reference-guide/_index.md → ...tensibility-api-reference-guide/_index.md
diff --git a/...y-api-reference-guide/extension-points.md → ...y-api-reference-guide/extension-points.md b/...y-api-reference-guide/extension-points.md → ...y-api-reference-guide/extension-points.md
diff --git a/...nsibility-api-reference-guide/services.md → ...nsibility-api-reference-guide/services.md b/...nsibility-api-reference-guide/services.md → ...nsibility-api-reference-guide/services.md
diff --git a/...nsibility-api-reference-guide/web-view.md → ...nsibility-api-reference-guide/web-view.md b/...nsibility-api-reference-guide/web-view.md → ...nsibility-api-reference-guide/web-view.md
diff --git a/...o/extensibility-api/csharp/get-started.md → ...0/extensibility-api/csharp/get-started.md b/...o/extensibility-api/csharp/get-started.md → ...0/extensibility-api/csharp/get-started.md
diff --git a/...nsibility-api/packaging-your-extension.md → ...nsibility-api/packaging-your-extension.md b/...nsibility-api/packaging-your-extension.md → ...nsibility-api/packaging-your-extension.md
@@ -1,29 +1,29 @@
----
-title: "Packaging Your Extension"
-url: /apidocs-mxsdk/apidocs/extensibility-api/packaging-your-extension
-weight: 30
----
-
-# Packaging your extension
-
-Once you have finished development on your extension, you might want to package it into an add-on module so that others can start using it. Once you have created the add-on module, it can then be published to the Mendix Marketplace for your extension users to download into their Studio Pro app.
-
-To package your extension, you will still need the `--enable-extension-development` command line option turned on. Create a new module in your Studio Pro app containing your dev extension, give it an appropriate name. Open the module's settings form and set it to be an Add-on module. In the `Extension name` dropdown, select the extension you want to package into it.
-
-![Extension Add-on Module](/attachments/apidocs-mxsdk/apidocs/extensibility-api/extensionAddOnModule.png)
-
-After you've created your add-on module with its extension, you can now export it, by right-clicking the module in the App Explorer and choosing `Export add-on module package`, as shown below.
-
-![Export Module](/attachments/apidocs-mxsdk/apidocs/extensibility-api/exportAddOnModule.png)
-
-You can now save the add-on module to a location of your choice.
-
-# Importing the extension add-on module
-
-Once the add-on module is available to a Studio Pro user, they are now able to add it in their application. They can so so by right-clicking the app in the App Explorer and choosing `Import module package`, as shown below.
-
-![Import Module](/attachments/apidocs-mxsdk/apidocs/extensibility-api/importAddOnModule.png)
-
-Once an add-on module containing an extension is imported in the app, Studio Pro will show a warning to the user, asking to trust the extension contained in it. If the user does not choose to trust, the module will still be imported but the extension inside it won't be loaded.
-
+---
+title: "Packaging Your Extension"
+url: /apidocs-mxsdk/apidocs/extensibility-api/packaging-your-extension
+weight: 30
+---
+
+# Packaging your extension
+
+Once you have finished development on your extension, you might want to package it into an add-on module so that others can start using it. Once you have created the add-on module, it can then be published to the Mendix Marketplace for your extension users to download into their Studio Pro app.
+
+To package your extension, you will still need the `--enable-extension-development` command line option turned on. Create a new module in your Studio Pro app containing your dev extension, give it an appropriate name. Open the module's settings form and set it to be an Add-on module. In the `Extension name` dropdown, select the extension you want to package into it.
+
+![Extension Add-on Module](/attachments/apidocs-mxsdk/apidocs/extensibility-api/extensionAddOnModule.png)
+
+After you've created your add-on module with its extension, you can now export it, by right-clicking the module in the App Explorer and choosing `Export add-on module package`, as shown below.
+
+![Export Module](/attachments/apidocs-mxsdk/apidocs/extensibility-api/exportAddOnModule.png)
+
+You can now save the add-on module to a location of your choice.
+
+# Importing the extension add-on module
+
+Once the add-on module is available to a Studio Pro user, they are now able to add it in their application. They can so so by right-clicking the app in the App Explorer and choosing `Import module package`, as shown below.
+
+![Import Module](/attachments/apidocs-mxsdk/apidocs/extensibility-api/importAddOnModule.png)
+
+Once an add-on module containing an extension is imported in the app, Studio Pro will show a warning to the user, asking to trust the extension contained in it. If the user does not choose to trust, the module will still be imported but the extension inside it won't be loaded.
+
 ![Trust Extension](/attachments/apidocs-mxsdk/apidocs/extensibility-api/trustExtension.png)
diff --git a/...tudio-pro/extensibility-api/web/_index.md → ...io-pro-10/extensibility-api/web/_index.md b/...tudio-pro/extensibility-api/web/_index.md → ...io-pro-10/extensibility-api/web/_index.md
diff --git a/...-pro/extensibility-api/web/get-started.md → ...o-10/extensibility-api/web/get-started.md b/...-pro/extensibility-api/web/get-started.md → ...o-10/extensibility-api/web/get-started.md
diff --git a/...y-api/web/web-extensions-howtos/_index.md → ...y-api/web/web-extensions-howtos/_index.md b/...y-api/web/web-extensions-howtos/_index.md → ...y-api/web/web-extensions-howtos/_index.md