Merge remote-tracking branch 'origin/development' into pr/passalaqua/11058

Author: MarkvanMents

.claude/scripts/resolve-doc-url.sh

@@ -1,6 +1,6 @@
 #!/bin/bash
 # Resolve a documentation URL to its source markdown file
-# Usage: resolve-doc-url.sh "/path/to/page/"
+# Usage: resolve-doc-url.sh "/url/path/"
 
 if [ -z "$1" ]; then
     echo "Usage: resolve-doc-url.sh <url>"

.claude/skills/docs-alt-text/SKILL.md

@@ -0,0 +1,71 @@
+---
+name: docs-alt-text
+description: Generates W3C-compliant alt text for images in documentation pages. Analyzes each image's purpose and adds descriptive alt text for informative images or empty alt for decorative images, improving accessibility and SEO.
+user-invocable: true
+disable-model-invocation: false
+---
+
+> **Accessibility skill:** Generates alt text following W3C/WCAG 2.1 guidelines. Analyzes actual image content plus context to create concise, meaningful descriptions.
+
+## Workflow
+
+Follow this order for each image:
+
+1. **STEP 1 - View the image file** (REQUIRED)
+   - Extract image src path from figure shortcode
+   - Convert path: `src="/attachments/path/file.png"` → `static/attachments/path/file.png`
+   - Use Read tool to view the actual image
+   - Understand what the image shows BEFORE reading context
+
+2. **STEP 2 - Read surrounding context**
+   - Read the heading, preceding/following text, list item, or numbered step
+   - Understand the image's purpose within the documentation
+   - Consider if context + image together make the image informative or decorative
+
+3. **STEP 3 - Determine if informative or decorative**
+   - **Technical docs assumption:** Images are informative unless obviously decorative
+   - **Informative:** Images that convey information → write descriptive alt text
+   - **Decorative:** Images where the information is already given in adjacent text, or pure visual styling with no informational value → use `alt=""`
+
+4. **STEP 4 - Generate alt text**
+   - **If decorative, use `alt=""`.** Never omit the alt attribute entirely.
+   - **If informative, generate descriptive alt text:**
+      - Focus on the information the image communicates, not what it looks like
+      - Give the most concise description possible
+      - Maximum 30 words (flag complex images needing longer descriptions for body text)
+      - Don't include "screenshot of", "image of", or "picture of" (screen readers already announce it's an image)
+      - Use Mendix terminology
+      - Avoid redundancy with nearby text
+      - **Based on surrounding context:**
+         - In a procedure: emphasize the action/element relevant to the step (e.g., "Download button in Registration dialog")
+         - Showing UI elements: name the relevant elements (e.g., "Properties pane")
+         - Showing structure or relationships: describe what entities/components are connected (e.g., "Domain model with Customer and Order entities connected by one-to-many association")
+         - Showing logic or process flow: describe what the flow accomplishes (e.g., "Microflow that retrieves FileDocument list and updates encryption keys")
+
+5. **STEP 5 - Edit the figure shortcode**
+   - Use Edit tool to add/update only the `alt` attribute
+   - Preserve all other attributes: `class`, `width`, `max-width`, `link`
+   - Maintain exact indentation and spacing
+
+## Special Cases
+
+- **Images in numbered lists:** Common in procedures—describe the procedural step shown
+- **Before/after sequences:** Describe what changed or the state shown
+- **Existing alt text:** May update if it's empty, generic, or poor quality (e.g., `alt=""`, `alt="button"`, `alt="before"`)
+- **File format icons:** Use format name (e.g., "PDF", "ZIP", "Word document")
+- **Complex diagrams:** If needs >30 words, flag to user and suggest adding description to body text
+
+## What NOT to do
+
+- Don't modify `src` path or attributes other than `alt`
+- Don't change surrounding text or document structure
+- Don't process images outside the determined scope
+- Don't generate alt text based solely on filename—always view the image first
+
+## After Processing
+
+Report summary:
+- How many images processed
+- How many updated
+
+**Always suggest user review:** Recommend that the user review the images themselves to confirm alt text accuracy, as AI-generated descriptions may miss important nuances or context-specific details.

.claude/skills/docs-polish/SKILL.md

@@ -1,18 +1,18 @@
 ---
 name: docs-polish
-description: Proofreads a single documentation page and improves clarity, readability, and word choice without changing meaning or reorganizing structure. Simplifies complex sentences, applies style guide standards, and converts passive voice to active voice. Use when the user wants to polish, improve language and clarity, make more readable, check style guide compliance, or clean up documentation while preserving its structure.
+description: Applies style guide standards to a documentation page without changing meaning or reorganizing structure. This includes fixing grammar, improving clarity and readability, simplifying complex sentences, using active voice, and standardizing terminology and formatting. Use when the user wants to polish, check style guide compliance, improve language, or clean up documentation while preserving its structure.
 user-invocable: true
 disable-model-invocation: false
 ---
 
-> **Skill progression:** This does everything `/docs-proofread` does plus clarity improvements and style guide enforcement. If only grammar and spelling fixes are needed, use `/docs-proofread`. For deeper reorganization, suggest `/docs-enhance`.
+> **Skill progression:** This does everything `/docs-proofread` does plus style guide enforcement including clarity improvements. If only grammar and spelling fixes are needed, use `/docs-proofread`. For deeper reorganization, suggest `/docs-enhance`. If missing alt text is found, suggest `/docs-alt-text`.
 
 Improve clarity and readability without changing meaning, structure, or paragraph order:
 
 **docs-polish should**:
 * Read Mendix style guides first (in parallel): `grammar-formatting.md`, `terminology.md`, and `product-naming-guide.md` from `/content/en/docs/community-tools/contribute-to-mendix-docs/style-guide/`
 * Fix all spelling, grammar, and punctuation errors
-* Add missing alt text to images (use simple, factual descriptions)
+* Check all figure shortcodes for missing alt text. If the alt text parameter is missing, insert `alt=""` as a placeholder.
 * Ensure required front matter fields are present (title, url, description) and make descriptions concise and action-oriented
 * Fix broken Markdown syntax
 * Fix capitalization and terminology inconsistencies
@@ -24,10 +24,15 @@ Improve clarity and readability without changing meaning, structure, or paragrap
 * Apply Mendix style guide standards (overrides the Microsoft Writing Style Guide)
 * Apply Microsoft Writing Style Guide standards, unless they conflict with the Mendix style guide standards
 
+**After completing edits**:
+* Report what was changed in a concise summary
+* If any images were found with missing or empty alt text, state "I found [N] image(s) with missing alt text. Consider running `/docs-alt-text` to generate alt text."
+
 **docs-polish should NOT**:
 * Move paragraphs or restructure sections (that's `/docs-enhance`)
 * Change technical meaning or accuracy
 * Significantly increase document length
+* Generate alt text for images
 * Change command syntax, code identifiers, variable names, placeholders, or any other text that appears in code formatting (inline backticks or code blocks). Code-formatted text represents literal technical content that must remain unchanged. If you notice an issue with code-formatted text, flag it in the chat but don't edit it directly.
 
 Every edit should serve a clear purpose in making the text easier to read, scan, and understand.

CLAUDE.md

@@ -81,7 +81,7 @@ Before creating a new file, use Glob to explore the directory structure and unde
 * **Headings** – H1 is generated from the front‑matter title. Subsequent headings increment by one level at a time. Don't use bold or italics as a replacement for headings. Use title case. Never start headings with numerals.
 * **Lists and tables** – Bullet lists use asterisks; ordered lists use numbers followed by a period. If there are more than three data points per item, use a table instead. Use the same syntax and structure for all list items in a given list. Use complete sentences to introduce lists and tables, not partial sentences completed with the list items.
 * **Indentation** – Four spaces for sub-lists and nested content. Alerts in lists are an exception:  don't indent alert lines but do omit preceding blank line.
-* **Links** – Use absolute paths starting with a leading slash (`/deployment/`). Use descriptive link text such as the page title, not "click here". To link to a heading, add an anchor ID (`{#anchor-id}`) next to the heading and use that ID in the URL (for example, `[Section title](/path/to/page#anchor-id)` to link to a heading in another page or `[Section title](#anchor-id)` to link to a heading in the same page).
+* **Links** – Link using the target page's `url` front matter field, not its file system path (e.g., `/deployment/` from front matter, not `content/en/docs/deployment/_index.md`). Use descriptive link text such as the page title, not "click here". To link to a heading, add an anchor ID (`{#anchor-id}`) next to the heading and use that ID in the URL (for example, `[Prerequisites](/deployment/mendix-cloud/#prerequisites)` to link to a heading in another page or `[Prerequisites](#prerequisites)` to link to a heading in the same page).
 * **Images** – Always include `alt` text (or `alt=""` if decorative). Use W3C guidelines. Reference images with the `figure` shortcode.
 * **Code** – Use fenced code blocks with language specifier. Do not modify text that appears in code formatting (inline backticks or code blocks), even to fix apparent inconsistencies or apply naming conventions. 
 
@@ -105,18 +105,18 @@ Call tools in parallel for independent operations (reading multiple files, multi
 
 ### Tool Selection
 
+* **Helper Scripts**
+    * For URL resolution, use `bash .claude/scripts/resolve-doc-url.sh` instead of spawning agents. This resolves documentation URLs (e.g., `/community-tools/contribute-to-mendix-docs/`) to their source Markdown files and ensures Grep uses efficient flags consistently.
 * **Read** – Use to view specific files you know the path to
 * **Edit** – Use to modify existing files with targeted changes
 * **Glob** – Use to find files by pattern (e.g., `*.md`, `**/*config*`)
 * **Grep** – Use to search file contents for specific text or patterns
 * **Write** – Use only for creating new files (prefer Edit for existing files)
-* **Helper Scripts** – Use `.claude/scripts/resolve-doc-url.sh` to resolve documentation URLs (e.g., `/path/to/page/`) to their source markdown files. This is faster and more token-efficient than using Grep to search front matter.
 
 ### Cross-Reference Verification
 
 When following or verifying documentation links:
-* Use `.claude/scripts/resolve-doc-url.sh "/path/to/page/"` to quickly find the source file for a URL
-* This is more efficient than Grep for URL-to-file lookups
+* Use `bash .claude/scripts/resolve-doc-url.sh "/url/path/"` to quickly find the source file for a URL
 
 When modifying URLs or anchor IDs:
 1. Use Grep to search for the old URL/anchor across all documentation files

branch-cleanup-timestamp.txt

@@ -1 +1 @@
-Last scan for stale merged branches: 2026-04-02 00:41:32 CEST (UTC+02:00)
+Last scan for stale merged branches: 2026-05-02 00:53:35 CEST (UTC+02:00)

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/packaging-your-extension.md

@@ -1,35 +1,36 @@
 ---
 title: "Packaging Your Extension"
-url: /apidocs-mxsdk/apidocs/extensibility-api-11/packaging-your-extension
+url: /apidocs-mxsdk/apidocs/extensibility-api-11/packaging-your-extension/
 weight: 30
+description: "Explains how to package extensions into add-on modules and publish them to the Mendix Marketplace."
 ---
 
 # Packaging Your Extension
 
-After completing development on your extension, you can package it into an add-on module so  others can use it. Once packaged, the module can be published to the Mendix Marketplace, allowing other users to download it into their Studio Pro apps.
+After you complete development on your extension, you can package it into an add-on module so others can use it. You can then publish the module to the Mendix Marketplace so other users can download it into their apps.
 
-To package your extension, follow the steps below:
+To package your extension, follow these steps:
 
-1. Make sure you have enabled the [Extension Development](/refguide/preferences-dialog/#extension-development) setting in your app's Preferences. Alternatively, you can start Studio Pro with the `--enable-extension-development` command-line option.
-2. In your Studio Pro app, create a new module and include your development extension.
-3. Give the module a name. 
-4. Open the module's settings and in the **Export** tab, choose **Add-on module**. 
-5. In the **Extension name** drop-down, select the extension you want to package into it.
+1. Verify that you have enabled the [Extension Development](/refguide/preferences-dialog/#extension-development) setting in your app's **Preferences**. Alternatively, start Studio Pro with the `--enable-extension-development` command-line option.
+2. In your app, create a new module and include your development extension.
+3. Name the module.
+4. Open the module's settings and on the **Export** tab, select **Add-on module**.
+5. In the **Extension name** list, select the extension you want to package.
 
-![Extension Add-on Module](/attachments/apidocs-mxsdk/apidocs/extensibility-api/extensionAddOnModule.png)
+{{< figure src="/attachments/apidocs-mxsdk/apidocs/extensibility-api/extensionAddOnModule.png" alt="Extension settings showing Add-on module selected with Extension name dropdown" width="400" >}}
 
-After you have created your add-on module with its extension, you can export it by right-clicking the module in the **App Explorer** and selecting **Export add-on module package**.
+After you create your add-on module with its extension, export it by right-clicking the module in the **App Explorer** and selecting **Export add-on module package**.
 
-![Export Module](/attachments/apidocs-mxsdk/apidocs/extensibility-api/exportAddOnModule.png)
+{{< figure src="/attachments/apidocs-mxsdk/apidocs/extensibility-api/exportAddOnModule.png" width="400" >}}
 
 You can now save the add-on module to a location of your choice.
 
 # Importing the Extension Add-on Module
 
-When the add-on module is available to a Studio Pro user, they are now able to add it in their application. This is done by right-clicking the app in the **App Explorer** and selecting **Import module package**.
+When the add-on module is available to a Studio Pro user, they can add to their app. This is done by right-clicking the app in the **App Explorer** and selecting **Import module package**.
 
-![Import Module](/attachments/apidocs-mxsdk/apidocs/extensibility-api/importAddOnModule.png)
+{{< figure src="/attachments/apidocs-mxsdk/apidocs/extensibility-api/importAddOnModule.png" width="400" >}}
 
-When 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 will not be loaded.
+When an add-on module containing an extension is imported in the app, Studio Pro displays a warning to the user, asking to trust the extension contained in it. If the user does not choose to trust the extension, the module is still imported but the extension inside it will not be loaded.
 
-![Trust Extension](/attachments/apidocs-mxsdk/apidocs/extensibility-api/trustExtension.png)
+{{< figure src="/attachments/apidocs-mxsdk/apidocs/extensibility-api/trustExtension.png" width="400" >}}

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/extensibility-api/web/_index.md

@@ -35,7 +35,7 @@ For detailed information on how to get started with extensions, see [Get Started
 
 ## How-tos
 
-Below is a list of how-tos for you to begin with:
+The following how-tos help you get started:
 
 * [How Menus Work](/apidocs-mxsdk/apidocs/web-extensibility-api-11/menu/)
 * [How to Create a Dockable Pane](/apidocs-mxsdk/apidocs/web-extensibility-api-11/dockable-pane-api/)