Merge branch 'mendix:development' into development

Author: atul-lahade-mx

content/en/docs/developerportal/digital-execution/implement-mendix/_index.md

@@ -1,11 +1,13 @@
 ---
 title: "Implementing Mendix in Your Organization"
 linktitle: "Implementing Mendix in Your Organization"
-url: /lead-mendix-implementation-in-your-organization/
+url: /developerportal/digital-execution/lead-mendix-implementation-in-your-organization/
 weight: 45
 description: "Unlock the full potential of the Mendix platform and accelerate the app development journey in your organization."
 no_list: false 
 description_list: true
+aliases:
+    - /lead-mendix-implementation-in-your-organization/
 ---
 
 ## Introduction

content/en/docs/developerportal/digital-execution/implement-mendix/first-project.md

@@ -1,9 +1,11 @@
 ---
 title: "Getting Started With Your First Project"
 linktitle: "Getting Started With Your First Project"
-url: /first-project/
+url: /developerportal/digital-execution/first-project/
 weight: 95
 description: "Find out how to get started with your first Mendix project."
+aliases:
+    - /first-project/
 ---
 
 ## Introduction

content/en/docs/developerportal/digital-execution/implement-mendix/getting-started.md

@@ -1,9 +1,11 @@
 ---
 title: "Creating a Getting Started Plan"
 linktitle: "Creating a Getting Started Plan"
-url: /getting-started-plan/
+url: /developerportal/digital-execution/getting-started-plan/
 weight: 65
 description: "Learn why and how to create an effective getting started plan."
+aliases:
+    - /getting-started-plan/
 ---
 
 ## Introduction

content/en/docs/developerportal/digital-execution/implement-mendix/governance.md

@@ -1,9 +1,11 @@
 ---
 title: "Setting Up Governance and Control in Mendix"
 linktitle: "Setting Up Governance and Control in Mendix"
-url: /governance-control/
+url: /developerportal/digital-execution/governance-control/
 weight: 85
 description: "Find out how to incorporate governance in your process."
+aliases:
+    - /governance-control/
 ---
 
 ## Introduction

content/en/docs/developerportal/digital-execution/implement-mendix/launch-app.md

@@ -1,9 +1,11 @@
 ---
 title: "Launching Your First App"
 linktitle: "Launching Your First App"
-url: /launch-first-app/
+url: /developerportal/digital-execution/launch-first-app/
 weight: 105
 description: "Find out how to test, deploy, and promote your first app."
+aliases:
+    - /launch-first-app/
 ---
 
 ## Introduction

content/en/docs/developerportal/digital-execution/implement-mendix/mendix-ecosystem.md

@@ -1,9 +1,11 @@
 ---
 title: "Delving Into the Mendix Ecosystem"
 linktitle: "Delving Into the Mendix Ecosystem"
-url: /mendix-ecosystem/
+url: /developerportal/digital-execution/mendix-ecosystem/
 weight: 55
 description: "Find out about the 3 S's and the 5 P's of digital execution."
+aliases:
+    - /mendix-ecosystem/
 ---
 
 ## Introduction
@@ -106,17 +108,17 @@ The following leadership roles are essential to the success of any new platform
 
 * Center of Excellence (COE) lead – larger organizations appoint a Mendix COE to help define and enforce good governance, development, and enablement practices that can evolve with the business and technological changes over time. The COE lead ensures the Mendix COE is properly staffed to support, oversee, and enable development teams, and ensures the products are of high-quality, and follow best practices for high re-usability, maintainability, and return on investment. This person generally has sufficient senior-level technical and managerial skills to oversee the COE’s Enterprise and Solution Architects, DevOps technical leads, trainers, mentors, and other experienced staff.
 
-* Product owner – they have in-depth knowledge of the business, the product, and its users, as well as insight into the value that it will create. If possible, make sure that your first product owner comes from your own organization, and is familiar with the problem you are setting out to solve with your first app. The product owner does not hold a leadership role, but they are crucial for the success of your first app. They are also part of the agile scrum team, so will come up again in the [Identify Your First Mendix Project Team](/start-program/#identify-first-mendix-team) section.
+* Product owner – they have in-depth knowledge of the business, the product, and its users, as well as insight into the value that it will create. If possible, make sure that your first product owner comes from your own organization, and is familiar with the problem you are setting out to solve with your first app. The product owner does not hold a leadership role, but they are crucial for the success of your first app. They are also part of the agile scrum team, so will come up again in the [Identify Your First Mendix Project Team](/developerportal/digital-execution/start-program/#identify-first-mendix-team) section.
 
 * Architect – they help establish a target architecture, infrastructure, and governance. 
 
 * App development manager – they need to spearhead the initiative, and drive the program and the cross-functional teams who will deliver on those projects. 
 
-At first, it is likely that not all these people will come from your own organization—the [Review Options for Development Resources](/getting-started-plan/#review-options-for-development-resources) section offers information about this.
+At first, it is likely that not all these people will come from your own organization—the [Review Options for Development Resources](/developerportal/digital-execution/getting-started-plan/#review-options-for-development-resources) section offers information about this.
 
 It is important to keep your team small as you build your Mendix COE, which is your central repository of development expertise, reusable components, and governance guidance that business teams can access as they build their specialized solutions. With a small team, you can deliver new app quickly, avoiding much of the miscommunication and delays that often come with larger development teams. Smaller teams encourage productivity and creativity. Amazon CEO Jeff Bezos’ “two pizza rule” states that you should never have a meeting where two pizzas couldn’t feed the entire group. The smaller the team, the more room for brainstorming and peer review. 
 
-Mendix recommends that you start thinking about who you need to kick off building your first app, and that you start talking to them about it. More information about who you need is available in the [Identifying Your First Mendix Project Team](/start-program/#identify-first-mendix-team) section.
+Mendix recommends that you start thinking about who you need to kick off building your first app, and that you start talking to them about it. More information about who you need is available in the [Identifying Your First Mendix Project Team](/developerportal/digital-execution/start-program/#identify-first-mendix-team) section.
 
 ##### Process
 

content/en/docs/developerportal/digital-execution/implement-mendix/questions-feedback.md

@@ -1,9 +1,11 @@
 ---
 title: "Questions and Feedback"
 linktitle: "Questions and Feedback"
-url: /questions-feedback/
+url: /developerportal/digital-execution/questions-feedback/
 weight: 115
 description: "Find resources related to digital execution practice and organizational considerations."
+aliases:
+    - /questions-feedback/
 ---
 
 ## Introduction

content/en/docs/developerportal/digital-execution/implement-mendix/resources.md

@@ -1,9 +1,11 @@
 ---
 title: "Resources"
 linktitle: "Resources"
-url: /resources/
+url: /developerportal/digital-execution/resources/
 weight: 125
 description: "Find resources related to the Mendix platform."
+aliases:
+    - /resources/
 ---
 
 ## Introduction

content/en/docs/developerportal/digital-execution/implement-mendix/start-program.md

@@ -1,9 +1,11 @@
 ---
 title: "Starting Your Mendix Program"
 linktitle: "Starting Your Mendix Program"
-url: /start-program/
+url: /developerportal/digital-execution/start-program/
 weight: 75
 description: "Find out how to kick off your Mendix program."
+aliases:
+    - /start-program/
 ---
 
 ## Introduction

content/en/docs/refguide/modeling/resources/_index.md

@@ -18,7 +18,7 @@ To add a resource document, do the following:
 
 1. In the [App Explorer](/refguide/app-explorer/), right-click the module or a folder you want to add a resource to and select **Add other**:
 
-    {{< figure src="/attachments/refguide/modeling/resources/app-explorer-resources.png" class="no-border" >}}
+    {{< figure src="/attachments/refguide/modeling/resources/add-resources.png" class="no-border" >}}
 
 2. In the **Resources** category, select the document you would like to add to your app.
 
@@ -28,18 +28,19 @@ The **Resources** category contain various document types that can be used in di
 
 | Element            | Is used in                      | Description                                                  |
 | ------------------ | -------------------------------------- | ------------------------------------------------------------ |
+| [Dataset](/refguide/data-sets/) | Pages                                  | Datasets define the data shown in reports widgets.        |
 | [Java action](/refguide/java-actions/) | Microflows                             | Java actions can extend the functionality of your application. They can be called from microflows. |
 | [JavaScript action](/refguide/javascript-actions/) | Nanoflow                               | JavaScript actions can extend the functionality of your application. They can be called from nanoflows. |
+| [Task queue](/refguide/task-queue/) |  Microflows and Java actions                                 | A Task queue allows you to run microflows or Java actions asynchronously while controlling the number of tasks that are active.   |
 | [Rule](/refguide/rules/)      | Microflows                             | Rules contain the application logic that should result in an enumeration or a Boolean. They are used in decisions in microflows. |
 | [Enumeration](/refguide/enumerations/) | Domain model                           | Enumerations are used to define attributes of an enumeration type. |
-| [Dataset](/refguide/data-sets/) | Pages                                  | Datasets define the data shown in reports widgets.        |
 | [Constant](/refguide/constants/) | Microflow expressions and Consumed web services | Constants are used to define configuration values.           |
 | [Regular expression](/refguide/regular-expressions/) | Domain model                           | Regular expressions are used in validation rules to define criteria that a string should match to pass the validation. They cannot be used in other places which require regular expressions (for example, the *isMatch()* function). |
 | [Scheduled event](/refguide/scheduled-events/) | Microflows                     | Scheduled events let the runtime execute a microflow at a specific moment in time. |
-| [Document template](/refguide/document-templates/) | Microflows                             | Document template is used to format the document in a client and to download or print it. |
+| [Document template](/refguide/document-templates/)(deprecated) | Microflows                             | Document template is used to format the document in a client and to download or print it. |
 
 ## Read More
 
 * [Microflows](/refguide/microflows/)
-* [Domain Model]
+* [Data in the Domain Model](/refguide/domain-model/)
 * [Pages](/refguide/pages/)