From 20b22e440d625f23990ccca2652bdb5efcc2f7ba Mon Sep 17 00:00:00 2001 From: Ryan Mocke Date: Fri, 14 Aug 2026 15:12:12 +0100 Subject: [PATCH 1/5] Add Maia introduction section to quickstart part 1. Adds a new "Build Faster with Maia" section to the Responsive Web App quickstart guide (Part 1), introducing Maia to beginners after they've completed the manual build steps. --- .../en/docs/quickstarts/responsive-web-app.md | 27 +++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/content/en/docs/quickstarts/responsive-web-app.md b/content/en/docs/quickstarts/responsive-web-app.md index 00ded5e36b0..bb69037e490 100644 --- a/content/en/docs/quickstarts/responsive-web-app.md +++ b/content/en/docs/quickstarts/responsive-web-app.md @@ -254,6 +254,33 @@ To deploy your app to a cloud environment, you can hit **publish** to deploy you To deploy your app to the Mendix Cloud (Paid), there are multiple options for hosting. Please refer to this guide on [our hosting options](/developerportal/deploy/mendix-cloud-deploy/) for more information on which plan is best for your project. {{% /alert %}} +## Build Faster with Maia + +Throughout this guide, you built your Employee app by hand — dragging entities onto the canvas, wiring up buttons, and writing microflow logic step by step. That's a great way to learn how Studio Pro works under the hood. But once you're comfortable with the basics, you don't have to do everything manually. **Maia**, Mendix's built-in AI assistant, can take over much of this repetitive modeling work for you. + +Unlike a typical chatbot that only answers questions, Maia is *agentic*: she can read your app's current domain model, pages, and logic, understand the context you're working in, and then directly create or modify app elements on your behalf. Ask her to add an entity, generate a page, or build out a microflow, and she'll produce real, editable Studio Pro artifacts — not just a suggestion or a code snippet for you to copy in. + +Maia isn't one single feature but a collection of capabilities woven into Studio Pro. The one you'll use most often is **[Maia Make](https://docs.mendix.com/refguide/mendix-ai-assistance/)**, a conversational interface where you describe what you want in plain language and Maia generates the domain model changes, pages, or microflows to match. Alongside Maia Make, you'll also find focused generators (for domain models, pages, workflows, and OQL queries), recommenders that suggest the next best widget or microflow activity as you build, and guidance tools like **[Maia Chat](https://docs.mendix.com/refguide/maia-chat/)** and **[Maia Explain](https://docs.mendix.com/refguide/mendix-ai-assistance/)** for when you want an explanation rather than a change to your app. As you grow more advanced, **[Maia Agent Skills](https://docs.mendix.com/refguide/maia-agent-skills/)** and Agent Instructions let you teach Maia your team's own conventions so her suggestions stay consistent with how your organization builds apps. + +### Try It Yourself: Extending the Employee App + +Let's put Maia to work on the app you just built. Right now, your Employee entity captures a job role as free text — let's use Maia to turn that into a proper Department entity, linked to Employee, along with an overview page. + +1. In Studio Pro, open **Maia Make** from the top bar. +1. In the chat box, describe what you want: + + > "Add a Department entity with a Name attribute. Create a one-to-many association from Department to Employee, so each employee belongs to one department. Then generate an overview page listing all departments with their employees, and add that page to the app's navigation." + +1. Maia will process the request and propose a set of changes — typically a new entity in your domain model, the association to Employee, a new page with a data grid, and a navigation entry linking to it. **Review** the proposed changes in the preview panel. +1. Click **Accept** to apply the changes to your app. You'll see the new **Department** entity appear in your App Explorer, already connected to Employee, along with a new item in your app's navigation menu. +1. **Open** the generated page and run your app locally (**F5**) to see the new Department overview — now reachable directly from the navigation menu — alongside your existing Employee Overview page. + +{{% alert type="info" %}} +You can keep iterating conversationally from here — for example, asking Maia to "add validation so a department name can't be empty" or "add a dropdown on the Employee page to select a department." Each request builds on the app state Maia already understands, so you don't need to re-explain your app every time. +{{% /alert %}} + +As you get more comfortable, try using **[Maia Explain](https://docs.mendix.com/refguide/maia-explain/)** on the microflow you built earlier (`Act_Employee_NewEdit`) to see how Maia summarizes logic you already created — a useful way to sanity-check your own work or onboard a teammate to the app quickly. + ## Finished! Congratulations on completing and deploying your very first Mendix App! Next, head over to the [Academy](https://academy.mendix.com/link/home) and get started with our **Crash Course** learning plan, or continue learning here in our docs pages by continuing onto part two. For videos on the latest news and updates, head to our [YouTube page](https://www.youtube.com/c/MendixCommunity). Or see what our awesome community is up to on our [Medium publication](https://medium.com/mendix). From 1799300c9f8241a03fa9fda9dd59d0a3372d312f Mon Sep 17 00:00:00 2001 From: ConnorLand <47385345+ConnorLand@users.noreply.github.com> Date: Mon, 17 Aug 2026 11:11:06 +0200 Subject: [PATCH 2/5] Update responsive-web-app.md --- content/en/docs/quickstarts/responsive-web-app.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/content/en/docs/quickstarts/responsive-web-app.md b/content/en/docs/quickstarts/responsive-web-app.md index bb69037e490..bccf2f47ec1 100644 --- a/content/en/docs/quickstarts/responsive-web-app.md +++ b/content/en/docs/quickstarts/responsive-web-app.md @@ -256,15 +256,15 @@ To deploy your app to the Mendix Cloud (Paid), there are multiple options for ho ## Build Faster with Maia -Throughout this guide, you built your Employee app by hand — dragging entities onto the canvas, wiring up buttons, and writing microflow logic step by step. That's a great way to learn how Studio Pro works under the hood. But once you're comfortable with the basics, you don't have to do everything manually. **Maia**, Mendix's built-in AI assistant, can take over much of this repetitive modeling work for you. +Throughout this guide, you built your **Employee** app by hand—dragging entities onto the canvas, wiring up buttons, and writing microflow logic step by step. That is a great way to learn how Studio Pro works under the hood. But once you are comfortable with the basics, you do not have to do everything manually. **Maia**, Mendix's built-in AI assistant, can take over much of this repetitive modeling work for you. -Unlike a typical chatbot that only answers questions, Maia is *agentic*: she can read your app's current domain model, pages, and logic, understand the context you're working in, and then directly create or modify app elements on your behalf. Ask her to add an entity, generate a page, or build out a microflow, and she'll produce real, editable Studio Pro artifacts — not just a suggestion or a code snippet for you to copy in. +Unlike a typical chatbot that only answers questions, Maia is agentic: it can read your app's current domain model, pages, and logic, understand the context you are working in, and then directly create or modify app elements on your behalf. Ask it to add an entity, generate a page, or build out a microflow, and it will produce real, editable Studio Pro artifacts—not just a suggestion or a code snippet for you to copy in. -Maia isn't one single feature but a collection of capabilities woven into Studio Pro. The one you'll use most often is **[Maia Make](https://docs.mendix.com/refguide/mendix-ai-assistance/)**, a conversational interface where you describe what you want in plain language and Maia generates the domain model changes, pages, or microflows to match. Alongside Maia Make, you'll also find focused generators (for domain models, pages, workflows, and OQL queries), recommenders that suggest the next best widget or microflow activity as you build, and guidance tools like **[Maia Chat](https://docs.mendix.com/refguide/maia-chat/)** and **[Maia Explain](https://docs.mendix.com/refguide/mendix-ai-assistance/)** for when you want an explanation rather than a change to your app. As you grow more advanced, **[Maia Agent Skills](https://docs.mendix.com/refguide/maia-agent-skills/)** and Agent Instructions let you teach Maia your team's own conventions so her suggestions stay consistent with how your organization builds apps. +Maia is not one single feature but a collection of capabilities woven into Studio Pro. The one you will use most often is [Maia Make](/refguide/mendix-ai-assistance/), a conversational interface where you describe what you want in plain language and Maia generates the domain model changes, pages, or microflows to match. Alongside Maia Make, you will also find focused generators (for domain models, pages, workflows, and OQL queries), recommenders that suggest the next best widget or microflow activity as you build, and guidance tools like [Maia Chat](/refguide/maia-chat/) and [Maia Explain](/refguide/mendix-ai-assistance/) for when you want an explanation rather than a change to your app. As you grow more advanced, [Maia Agent Skills](/refguide/maia-agent-skills/) and Agent Instructions let you teach Maia your team's own conventions so Maia's suggestions stay consistent with how your organization builds apps. ### Try It Yourself: Extending the Employee App -Let's put Maia to work on the app you just built. Right now, your Employee entity captures a job role as free text — let's use Maia to turn that into a proper Department entity, linked to Employee, along with an overview page. +Let's put Maia to work on the app you just built. Right now, your **Employee** entity captures a job role as free text. Next, let us use Maia to turn that into a proper **Department** entity, linked to **Employee** along with an overview page: 1. In Studio Pro, open **Maia Make** from the top bar. 1. In the chat box, describe what you want: @@ -276,10 +276,10 @@ Let's put Maia to work on the app you just built. Right now, your Employee entit 1. **Open** the generated page and run your app locally (**F5**) to see the new Department overview — now reachable directly from the navigation menu — alongside your existing Employee Overview page. {{% alert type="info" %}} -You can keep iterating conversationally from here — for example, asking Maia to "add validation so a department name can't be empty" or "add a dropdown on the Employee page to select a department." Each request builds on the app state Maia already understands, so you don't need to re-explain your app every time. +You can keep iterating conversationally from here—for example, asking Maia to "add validation so a department name can't be empty" or "add a dropdown on the Employee page to select a department." Each request builds on the app state Maia already understands, so you do not need to re-explain your app every time. {{% /alert %}} -As you get more comfortable, try using **[Maia Explain](https://docs.mendix.com/refguide/maia-explain/)** on the microflow you built earlier (`Act_Employee_NewEdit`) to see how Maia summarizes logic you already created — a useful way to sanity-check your own work or onboard a teammate to the app quickly. +As you get more comfortable, try using [Maia Explain](/refguide/maia-explain/) on the microflow you built earlier (`Act_Employee_NewEdit`) to see how Maia summarizes logic you already created—a useful way to sanity-check your own work or onboard a teammate to the app quickly. ## Finished! From ba8b980903b95b80b4e2fad36a1bac9643148f49 Mon Sep 17 00:00:00 2001 From: ConnorLand <47385345+ConnorLand@users.noreply.github.com> Date: Mon, 17 Aug 2026 11:20:11 +0200 Subject: [PATCH 3/5] format --- content/en/docs/quickstarts/responsive-web-app.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/en/docs/quickstarts/responsive-web-app.md b/content/en/docs/quickstarts/responsive-web-app.md index bccf2f47ec1..844980314f5 100644 --- a/content/en/docs/quickstarts/responsive-web-app.md +++ b/content/en/docs/quickstarts/responsive-web-app.md @@ -256,7 +256,7 @@ To deploy your app to the Mendix Cloud (Paid), there are multiple options for ho ## Build Faster with Maia -Throughout this guide, you built your **Employee** app by hand—dragging entities onto the canvas, wiring up buttons, and writing microflow logic step by step. That is a great way to learn how Studio Pro works under the hood. But once you are comfortable with the basics, you do not have to do everything manually. **Maia**, Mendix's built-in AI assistant, can take over much of this repetitive modeling work for you. +Throughout this guide, you built your **Employee** app by hand—dragging entities onto the canvas, wiring up buttons, and writing microflow logic step by step. That is a great way to learn how Studio Pro works under the hood. But once you are comfortable with the basics, you do not have to do everything manually. Maia, Mendix's built-in AI assistant, can take over much of this repetitive modeling work for you. Unlike a typical chatbot that only answers questions, Maia is agentic: it can read your app's current domain model, pages, and logic, understand the context you are working in, and then directly create or modify app elements on your behalf. Ask it to add an entity, generate a page, or build out a microflow, and it will produce real, editable Studio Pro artifacts—not just a suggestion or a code snippet for you to copy in. @@ -271,9 +271,9 @@ Let's put Maia to work on the app you just built. Right now, your **Employee** e > "Add a Department entity with a Name attribute. Create a one-to-many association from Department to Employee, so each employee belongs to one department. Then generate an overview page listing all departments with their employees, and add that page to the app's navigation." -1. Maia will process the request and propose a set of changes — typically a new entity in your domain model, the association to Employee, a new page with a data grid, and a navigation entry linking to it. **Review** the proposed changes in the preview panel. -1. Click **Accept** to apply the changes to your app. You'll see the new **Department** entity appear in your App Explorer, already connected to Employee, along with a new item in your app's navigation menu. -1. **Open** the generated page and run your app locally (**F5**) to see the new Department overview — now reachable directly from the navigation menu — alongside your existing Employee Overview page. +1. Maia will process the request and propose a set of changes—typically a new entity in your domain model, the association to Employee, a new page with a data grid, and a navigation entry linking to it. **Review** the proposed changes in the preview panel. +1. Click **Accept** to apply the changes to your app. You will see the new **Department** entity appear in your App Explorer, already connected to Employee, along with a new item in your app's navigation menu. +1. **Open** the generated page and run your app locally (F5 ) to see the new **Department** overview—now reachable directly from the navigation menu—alongside your existing **Employee Overview** page. {{% alert type="info" %}} You can keep iterating conversationally from here—for example, asking Maia to "add validation so a department name can't be empty" or "add a dropdown on the Employee page to select a department." Each request builds on the app state Maia already understands, so you do not need to re-explain your app every time. From 235b64c02f33fee690d30d926fa5c347c59130ea Mon Sep 17 00:00:00 2001 From: ConnorLand <47385345+ConnorLand@users.noreply.github.com> Date: Mon, 17 Aug 2026 11:22:58 +0200 Subject: [PATCH 4/5] remove contraction --- content/en/docs/quickstarts/responsive-web-app.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/quickstarts/responsive-web-app.md b/content/en/docs/quickstarts/responsive-web-app.md index 844980314f5..e69e1703b85 100644 --- a/content/en/docs/quickstarts/responsive-web-app.md +++ b/content/en/docs/quickstarts/responsive-web-app.md @@ -264,7 +264,7 @@ Maia is not one single feature but a collection of capabilities woven into Studi ### Try It Yourself: Extending the Employee App -Let's put Maia to work on the app you just built. Right now, your **Employee** entity captures a job role as free text. Next, let us use Maia to turn that into a proper **Department** entity, linked to **Employee** along with an overview page: +Put Maia to work on the app you just built. Right now, your **Employee** entity captures a job role as free text. Next, let us use Maia to turn that into a proper **Department** entity, linked to **Employee** along with an overview page: 1. In Studio Pro, open **Maia Make** from the top bar. 1. In the chat box, describe what you want: From 9dc250b7a35fa10e66248442cee879f09473f420 Mon Sep 17 00:00:00 2001 From: Quinn Tracy <142489060+quinntracy@users.noreply.github.com> Date: Mon, 17 Aug 2026 12:51:13 +0200 Subject: [PATCH 5/5] Small wording adjustments --- content/en/docs/quickstarts/responsive-web-app.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/quickstarts/responsive-web-app.md b/content/en/docs/quickstarts/responsive-web-app.md index e69e1703b85..6be56b5e7d5 100644 --- a/content/en/docs/quickstarts/responsive-web-app.md +++ b/content/en/docs/quickstarts/responsive-web-app.md @@ -260,7 +260,7 @@ Throughout this guide, you built your **Employee** app by hand—dragging entiti Unlike a typical chatbot that only answers questions, Maia is agentic: it can read your app's current domain model, pages, and logic, understand the context you are working in, and then directly create or modify app elements on your behalf. Ask it to add an entity, generate a page, or build out a microflow, and it will produce real, editable Studio Pro artifacts—not just a suggestion or a code snippet for you to copy in. -Maia is not one single feature but a collection of capabilities woven into Studio Pro. The one you will use most often is [Maia Make](/refguide/mendix-ai-assistance/), a conversational interface where you describe what you want in plain language and Maia generates the domain model changes, pages, or microflows to match. Alongside Maia Make, you will also find focused generators (for domain models, pages, workflows, and OQL queries), recommenders that suggest the next best widget or microflow activity as you build, and guidance tools like [Maia Chat](/refguide/maia-chat/) and [Maia Explain](/refguide/mendix-ai-assistance/) for when you want an explanation rather than a change to your app. As you grow more advanced, [Maia Agent Skills](/refguide/maia-agent-skills/) and Agent Instructions let you teach Maia your team's own conventions so Maia's suggestions stay consistent with how your organization builds apps. +Maia is not one single feature but a collection of capabilities woven into Studio Pro. [Maia Make](/refguide/mendix-ai-assistance/), is a conversational interface where you describe what you want in plain language and Maia generates the domain model changes, pages, or microflows to match. Within Maia Make are focused generators (for domain models, pages, workflows, and OQL queries), recommenders that suggest the next best widget or microflow activity as you build, and guidance tools like [Maia Chat](/refguide/maia-chat/) and [Maia Explain](/refguide/mendix-ai-assistance/) for when you want an explanation rather than a change to your app. As you grow more advanced, [Maia Agent Skills](/refguide/maia-agent-skills/) and Agent Instructions let you teach Maia your team's own conventions so Maia's suggestions stay consistent with how your organization builds apps. ### Try It Yourself: Extending the Employee App @@ -279,7 +279,7 @@ Put Maia to work on the app you just built. Right now, your **Employee** entity You can keep iterating conversationally from here—for example, asking Maia to "add validation so a department name can't be empty" or "add a dropdown on the Employee page to select a department." Each request builds on the app state Maia already understands, so you do not need to re-explain your app every time. {{% /alert %}} -As you get more comfortable, try using [Maia Explain](/refguide/maia-explain/) on the microflow you built earlier (`Act_Employee_NewEdit`) to see how Maia summarizes logic you already created—a useful way to sanity-check your own work or onboard a teammate to the app quickly. +As you get more comfortable, you can ask Maia to explain the microflow you built earlier (`Act_Employee_NewEdit`) to see how Maia summarizes logic you already created—a useful way to sanity-check your own work or onboard a teammate to the app quickly. ## Finished!