Merge remote-tracking branch 'upstream/development' into development

Author: github-actions[bot]

.github/workflows/check-claude-settings.yml

@@ -0,0 +1,45 @@
+name: Check Claude Configuration
+
+on:
+  pull_request:
+    paths:
+      - '.claude/**'
+      - 'CLAUDE.md'
+
+jobs:
+  check-claude-config:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check for Claude configuration changes
+        uses: actions/github-script@v7
+        with:
+          script: |
+            const comment = `⚠️ **Claude Configuration Warning**
+
+            You've modified Claude Code configuration files. These files contain the shared configuration for all contributors. Please revert this change if unintended. **ONLY modify these files if you need to change shared configurations that apply to everyone and have discussed this change with the TW team.**
+
+            To override the Claude settings locally, use \`.claude/settings.local.json\` instead.
+
+            **For example, if you're changing AWS_PROFILE:**
+            The default profile name is \`my-sandbox\`. If your AWS profile has a different name, override it locally instead of changing the shared file.
+
+            Create or edit \`.claude/settings.local.json\` in the repo root and include the following lines:
+
+            \`\`\`json
+            {
+              "env": {
+                "AWS_PROFILE": "your-sandbox-name"
+              }
+            }
+            \`\`\`
+
+            This local file is gitignored and overrides the repo default.`;
+
+            github.rest.issues.createComment({
+              issue_number: context.issue.number,
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              body: comment
+            });
+
+            core.setFailed('Claude configuration was modified - see comment for guidance');

CLAUDE.md

@@ -200,3 +200,7 @@ If you are unsure whether a command is safe to run, **do not run it**. Instead,
 - Run tests after making changes: see project-specific test commands
 - Do not add dependencies without asking
 - Do not refactor code beyond what was requested
+
+### Claude Code Settings Management
+
+For personal configuration changes (AWS_PROFILE, etc.), always suggest `.claude/settings.local.json` instead of modifying `.claude/settings.json`. The local file is gitignored and overrides shared settings.

CONTRIBUTING.md

@@ -1,4 +1,5 @@
-For guidelines on contributing to the Mendix documentation, please see these two documents:
+For guidelines on contributing to the Mendix documentation, see these documents:
 
 * [How to Contribute to Mendix Docs](https://docs.mendix.com/community-tools/contribute-to-mendix-docs/)
 * [Documentation Writing Guidelines](https://docs.mendix.com/community-tools/documentation-guidelines/)
+* [Using AI Tools for Documentation](https://docs.mendix.com/community-tools/contribute-to-mendix-docs/using-ai-tools/)

content/en/docs/community-tools/contribute-to-mendix-docs/using-ai-tools.md

@@ -0,0 +1,64 @@
+---
+title: "Using AI Tools for Documentation"
+url: /community-tools/contribute-to-mendix-docs/using-ai-tools/
+weight: 30
+description: "Guidelines for using AI tools when contributing to Mendix documentation."
+---
+
+## Introduction
+
+Contributors may use AI tools such as large language models and writing assistants to draft or improve documentation. However, these tools must be treated as writing aids, like spell-checkers or linters, and not as authoritative sources.
+
+## Contributor Responsibility
+
+If you use AI tools, before contributing, you must:
+
+* Review and verify the accuracy of all AI-assisted content.
+* Ensure the content does not infringe on third-party copyrights.
+* Remove hallucinated content or unsupported claims.
+* Confirm that the AI tool's terms do not impose restrictions inconsistent with Mendix's contributors license agreement.
+
+AI output must be treated as unverified draft material.
+
+## Maintainer Discretion
+
+Maintainers may request clarification, edits, or removal of AI-assisted content if concerns arise regarding accuracy, licensing, or quality.
+
+## Using AI Assistants
+
+This repository is configured for use with [Claude Code](https://code.claude.com/docs/en/vs-code), an AI-powered coding assistant. There is also GitHub Copilot customization for contributors who use it.
+
+### Claude Code Configuration
+
+The default AWS profile name is `my-sandbox`. If your AWS sandbox profile has a different name, create `.claude/settings.local.json` in the repo root and include the following lines:
+
+```json
+{
+  "env": {
+    "AWS_PROFILE": "your-sandbox-name"
+  }
+}
+```
+
+This file is gitignored and will override the shared settings.
+
+{{% alert color="warning" %}}
+Do not modify `.claude/settings.json` or other files in the `.claude/` directory for personal configuration. These files contain shared configuration for all contributors.
+{{% /alert %}}
+
+### Custom Skills
+
+This repository includes custom Claude Code skills optimized for documentation work:
+
+* `/proofread` - Checks spelling, grammar, punctuation, and basic Markdown formatting
+* `/polish` - Improves clarity, readability, and word choice without changing meaning
+* `/enhance` - Performs comprehensive editing including reorganization, restructuring, and stronger phrasing
+* `/review` - Analyzes documentation and generates suggestions for improvements
+* `/add` - Adds new content to an existing page while preserving original structure
+
+These skills are available to all contributors using Claude Code with this repository.
+
+## Read More
+
+* [Contributing to Mendix Docs](/community-tools/contribute-to-mendix-docs/)
+* [Documentation Writing Guidelines](/community-tools/documentation-guidelines/)

content/en/docs/control-center/security/software-composition/components.md

@@ -48,12 +48,12 @@ The component list contains the following information:
 * **Support type** — The support type of the Marketplace component. This can be **Mendix**, **Partner**, or **Community**.    
   For more information, refer to [Content Support Categories](/appstore/marketplace-content-support/#category).
 * **Version** — The version of the component that is being used.
-* **Findings** — This shows the number of findings of each type, color-coded according to severity level.
+* **Findings** — The number of findings of each type, color-coded according to severity level.
 * **License** — For components derived from the Mendix Marketplace, this is the end-user license for the component.
 * **Marketplace** – Whether the component is **Public** or **Private**. A public component is available to the whole Mendix community in the Marketplace, while a private component is available only via your [Company Content](/appstore/home-page/#company-content) page.
 * **Apps using component** – The number of apps where the component is used.
-* **Latest version** — The latest version of the component.
-* **Publisher** — The name of the organization that published the component.
+* **Latest version** — For components derived from the Mendix Marketplace, this is the latest version of the component.
+* **Publisher** — For components derived from the Mendix Marketplace, this is the name of the organization that published the component.
 * **View details** — Clicking this opens the [Component Details](#component-details) page.
 * Column customization ({{% icon name="view" %}}) – You can customize the columns of the list by clicking the {{% icon name="view" %}} icon and selecting or deselecting options.
 

content/en/docs/control-center/security/software-composition/overview.md

@@ -133,10 +133,10 @@ The component usage list contains the following information:
 * **Support type** – The support type of the Marketplace component. This can be **Mendix**, **Partner**, or **Community**.    
   For more information, refer to [Content Support Categories](/appstore/marketplace-content-support/#category).
 * **License** – For components derived from the Mendix Marketplace, this is the end-user license for the component.
-* **Latest version** – The latest version of the component.
+* **Latest version** – For components derived from the Mendix Marketplace, this is the latest version of the component.
 * **Marketplace** – Whether the component is **Public** or **Private**. A public component is available to the whole Mendix community in the Marketplace, while a private component is available only via your [Company Content](/appstore/home-page/#company-content) page.
 * **Latest Runtime Compatible Version** — The most recent runtime version to which the component is compatible.
-* **Publisher** – The name of the organization that published the component.
+* **Publisher** – For components derived from the Mendix Marketplace, this is the name of the organization that published the component.
 * Column customization ({{% icon name="view" %}}) – You can customize the columns of the list by clicking the {{% icon name="view" %}} icon and selecting or deselecting options.
 
 To export the information corresponding to selected items in the list to an Excel file, select the checkboxes of the items in the list, then click **Selection Export** that appears at the bottom of the page.

content/en/docs/deployment/general/software-composition.md

@@ -153,11 +153,11 @@ The component list contains the following information:
 * **Support type** — The support type of the Marketplace component. This can be **Mendix**, **Partner**, or **Community**.    
   For more information, refer to [Content Support Categories](/appstore/marketplace-content-support/#category).
 * **Version** — The version of the component that is being used.
-* **Findings** — This shows the number of findings of each type, color-coded according to severity level.
+* **Findings** — The number of findings of each type, color-coded according to severity level.
 * **License** — For components derived from the Mendix Marketplace, this is the end-user license for the component.
 * **Marketplace** – Whether the component is **Public** or **Private**. A public component is available to the whole Mendix community in the Marketplace, while a private component is available only via your [Company Content](/appstore/home-page/#company-content) page.
-* **Latest version** — The latest version of the component.
-* **Publisher** — The name of the organization that published the component.
+* **Latest version** — For components derived from the Mendix Marketplace, this is the latest version of the component.
+* **Publisher** — For components derived from the Mendix Marketplace, this is the name of the organization that published the component.
 * **View details** — Clicking this opens the [Component App Details](#component-usage) page.
 * Column customization ({{% icon name="view" %}}) – You can customize the columns of the list by clicking the {{% icon name="view" %}} icon and selecting or deselecting options.
 

content/en/docs/developerportal/_index.md

@@ -29,10 +29,6 @@ The following sections describe the process for each option.
 
 ### Creating an App with Maia
 
-{{% alert color="warning" %}}
-This feature is in Public Beta. For more information, refer to [Release Status](/releasenotes/release-status/).
-{{% /alert %}}
-
 Follow the steps in [Maia Plan](/developerportal/maia-plan/) to enlist Maia's help in planning and creating an app.
 
 ### Creating an App from a Starter App Template

content/en/docs/developerportal/maia-plan.md

@@ -3,36 +3,35 @@ title: "Maia Plan"
 url: /developerportal/maia-plan/
 description: "Describes the process of planning and building an app using Maia."
 weight: 3
-beta: true
 ---
 
-{{% alert color="warning" %}}
-This feature is in Public Beta. For more information, refer to [Release Status](/releasenotes/release-status/).
-{{% /alert %}}
-
 ## Introduction
 
-You can use Maia Plan to plan and generate an app. This page details the steps involved in providing project context, reviewing and refining the generated project scope, and approving the solution proposal to initiate app development.
+You can use Maia Plan to plan and generate an app. This page describes how to provide project context, review and refine the generated project scope, and approve the solution proposal to initiate app development.
 
-{{< figure src="/attachments/developerportal/maia/maia-create-app-beta.png" alt="Plan and build with Maia" >}}
+{{< figure src="/attachments/developerportal/maia/maia-create-app.png" alt="Plan and build with Maia" max-width=50% >}}
 
 ## Creating an App with Maia Plan
 
-Follow these steps to have Maia Plan create an app for you:
+Go through the steps in the following sections to have Maia Plan create an app for you.
+
+### Adding Project Details
 
 1. In **Apps**, click **Create App** in the upper right corner.
 
 2. Select **Plan & Build with Maia**. 
 
-3. In the **Project Context** text box, enter as much detail as possible about your future app. These are some details that you could add to help Maia generate an app for you:
+3. In the **Project Context** text box, enter as much detail as possible about your future app. Include the following information to help Maia generate an accurate app plan:
 
     * Describe your goals.
     * Describe your targeted users.
     * List out success criteria.
     * Add requirements.
     * Attach documents, sketches, images.
 
-4. Click **Generate Plan**. The **Project Scope** window is displayed, and Maia starts populating it with the proposed project scope.     
+### Generating the Project Scope
+
+1. Once you have added all the preliminary details, click **Generate Plan**. The **Project Scope** window is displayed, and Maia starts populating it with the proposed project scope.     
    The app plan becomes available on the **Apps** page as soon as you click **Generate Plan** at the beginning of the workflow. As such, you can go back to the plan at any time after you leave it, and you can already add team members to the app.
 
     Once the **Project Scope** window is populated, you can see the following information generated by Maia:
@@ -61,22 +60,49 @@ Follow these steps to have Maia Plan create an app for you:
 
     You can use the pane on the right to chat with Maia about your requirements for the new app.
 
-5. Once you review the project scope and make any changes you deem necessary, click **Approve Project Scope** in the top right of the page. The status of the project scope changes from **Draft** to **Approved**.
+2. Once you review the project scope and make any changes you deem necessary, click **Approve Project Scope** in the top right of the page. The status of the project scope changes from **Draft** to **Approved**.
+
+### Generating the Solution Proposal
 
-6. Click **Generate Solution** in the top right of the page. The **Solution Proposal** window is displayed, and Maia starts populating it with the proposed project scope.     
-    While the solution proposal is being generated, as well as after it's displayed, the **Project Scope** is locked. If you want to make changes to it, you can click the lock icon to unlock it.    
-    Once the **Solution Proposal** window is populated, you can see the following information generated by Maia:
+If you agree with the project scope, click **Generate Solution** in the top right of the page. The **Solution Proposal** window is displayed, and Maia starts populating it with the proposed project scope.     
+While the solution proposal is being generated, as well as after it's displayed, the **Project Scope** is locked. If you want to make changes to it, you can click the lock icon to unlock it.    
+Once the **Solution Proposal** window is populated, you can see the following information generated by Maia:
 
-    * Cards corresponding to each epic which contributes to building the app.    
-        You can remove epics by hovering over them, then clicking the trash can icon.    
-        Click the card itself to:
+* Cards corresponding to each epic which contributes to building the app.    
+    You can remove epics by hovering over them, then clicking the trash can icon.    
+    Click the card itself to:
 
-        * See the entire list of stories for an epic in the right side panel.
-        * Edit the description or details of the epic.
+    * See the entire list of stories for an epic in the right side panel.
+    * Edit the description or details of the epic.
 
-      You can perform the following actions on each story:
+    You can perform the following actions on each story:
+
+    * To see the full details of a story or to edit it, click the three-dot menu, then select **Edit**.    
+    * To remove a story, click the three-dot menu, then select **Delete**.
+
+<!--
+#### Recommended Marketplace Components {#recommender}
+
+{{% alert color="warning" %}} This feature is in Public Beta. For more information, refer to Release Status. {{% /alert %}}
+
+If Mendix identifies Marketplace components that can be used to implement a specific story, they are displayed in the following places:
+
+* At the epic level, as a number. Example: *1 Resource*.
+* At the user story level, in the side panel. From here, you can perform the following actions:
+
+    * If you want more details about the component, click it to access its page in the Marketplace.
+    * If you do not want a component to be used, delete it by clicking the trash can icon.
+
+If your company has company-approved components, Maia only returns company-approved components from the Public and the Private Marketplace.    
+If your company does not have company-approved components, Maia returns the following types of components:
+
+* platform-supported components
+* all Private Marketplace components
+-->
+    
+### Opening the App
 
-        * To see the full details of a story or to edit it, click the three-dot menu, then select **Edit**.    
-        * To remove a story, click the three-dot menu, then select **Delete**.
+Once you are happy with Maia's suggested project plan, click **Open in Studio Pro** in the top right of the page. This opens Studio Pro, where you can continue working on the new app. <!-- Note that, at the moment, Studio Pro does not take into account [recommended components](#recommender). -->    
+For details, refer to [Maia Make](/refguide/maia-make/) in the Studio Pro documentation.    
 
-7. Once you are happy with Maia's suggested project plan, click **Open in Studio Pro** in the top right of the page. This opens Studio Pro, where you can continue working on the new app. For details, refer to [Maia Make](/refguide/maia-make/) in the Studio Pro documentation.
+You can also click **Open in Planning** to open the **Planning** window of the new app, which includes  all the project's stories. <!-- Note that, if you click **Open in Planning** before Maia is done [finding recommendations](#recommender), recommended components are not displayed in the **Planning** window. -->