From 4883eb3618a981abadc5d7c01bec0ce50798de53 Mon Sep 17 00:00:00 2001 From: Dana Breseman Date: Thu, 5 Nov 2026 13:28:08 +0100 Subject: [PATCH 01/17] Add skill --- .claude/skills/docs-new-page/SKILL.md | 27 +++++++++++++++++++++++++++ CLAUDE.md | 2 +- 2 files changed, 28 insertions(+), 1 deletion(-) create mode 100644 .claude/skills/docs-new-page/SKILL.md diff --git a/.claude/skills/docs-new-page/SKILL.md b/.claude/skills/docs-new-page/SKILL.md new file mode 100644 index 00000000000..3359b8d4a1f --- /dev/null +++ b/.claude/skills/docs-new-page/SKILL.md @@ -0,0 +1,27 @@ +--- +name: docs-new-page +description: Creates a new documentation page from the matching template in `templates/`. Use when the user asks to create, write, draft, or start a new documentation page or file. +user-invocable: true +--- + +Draft a new page by following these steps: + +1. Check whether the user has provided source material for the page's content. If material is missing, ask for it in a single prompt before continuing: + * Links, such as Jira tickets or Confluence pages + * Pasted content, such as specs, notes, a Slack thread, a transcript, a draft, a README, code or config snippets, or screenshots + * An existing page to use as a model + + If the user provides a link, read it only if you have a tool that can access it. If you can't access it, say so and ask the user to paste the content. +2. Explore `content/en/docs/` and decide where the page belongs (if it isn't clear, ask the user to confirm). Read the section's `_index.md` and nearby pages to match their conventions. +3. Search `content/en/docs/` for the page's main terms. Ignore the versioned folders for older Mendix versions (`refguide10`, `howto9`, and so on) unless the user says the page is for an older version. If a page already covers the entire topic, tell the user and ask whether to update that page instead. If a page covers part of it, link to that page instead of repeating the covered content, and ask the user whether the missing content belongs on the existing page or on the new one. Note any pages that need a link to the new page, and tell the user at the end. +4. Read the appropriate template from `templates/`. +5. Create the new file based on the template. File names must be simple, lowercase, and hyphen-separated. +6. Clean up the template: + * In the front matter, uncomment and complete `url` and `description`. Delete any unused commented fields. + * Replace or remove every `{…}` placeholder and instruction comment. + * Delete optional sections that don't apply. +7. Complete the introduction and the remaining sections. Content varies by content type. +8. Verify that any linked pages exist in the repo, using each target page's `url` front matter field. Link to the related pages found in step 3. +9. Run the `docs-copyedit` and `docs-alt-text` skills on the new page. + +Don't add product claims, technical behavior, or release facts that the user didn't provide. If more information is needed, ask the user to provide it. diff --git a/CLAUDE.md b/CLAUDE.md index 98f8f2db64a..18791391010 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -17,7 +17,7 @@ When instructions conflict, follow this order of precedence: ### Critical Constraints -* Edit existing files in place using the Edit tool. Do not create new files unless explicitly requested. +* Edit existing files in place using the Edit tool. Do not create new files unless explicitly requested. When a new file is requested, use the `docs-new-page` skill. * Preserve meaning and intent. Make the smallest set of edits that fully resolves the request. * Never add product claims, technical behavior, ticket numbers, or release facts unless explicitly requested and sourced from provided content. From d622bc8256390b9148542308a9afe4739cdc4ef4 Mon Sep 17 00:00:00 2001 From: Dana Breseman Date: Mon, 16 Nov 2026 13:20:40 +0100 Subject: [PATCH 02/17] Make template instruction generic --- CLAUDE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CLAUDE.md b/CLAUDE.md index 18791391010..a22c5b737c5 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -139,7 +139,7 @@ Less common shortcodes (`button`, `expandable-table`, `youtube`, `vidyard`, `swa If asked to create new content: -1. Read the appropriate template from `templates/`: `how-to-template.md`, `reference-template.md`, `marketplace-component-page-template.md`, or `release-notes-template.md`. +1. List `templates/` and read the template that matches the content type. 2. Use Write tool to create the new file based on the template. 3. Remove comment lines (`#`) from the template. 4. Follow the editorial workflow above. From 783a57783bb54bbb879c3eb5449ae159f033fde5 Mon Sep 17 00:00:00 2001 From: Dana Breseman Date: Mon, 16 Nov 2026 13:25:16 +0100 Subject: [PATCH 03/17] Fix Marketplace headings cascade --- .../docs/releasenotes/marketplace/general-marketplace/2026.md | 1 - .../releasenotes/marketplace/general-marketplace/_index.md | 3 ++- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/releasenotes/marketplace/general-marketplace/2026.md b/content/en/docs/releasenotes/marketplace/general-marketplace/2026.md index 4b4bc945ab0..dbca2a9bee5 100644 --- a/content/en/docs/releasenotes/marketplace/general-marketplace/2026.md +++ b/content/en/docs/releasenotes/marketplace/general-marketplace/2026.md @@ -4,7 +4,6 @@ linktitle: "2026" url: /releasenotes/marketplace/2026/ description: "2026 release notes for Marketplace" weight: 1 -numberless_headings: true --- ## October 2026 diff --git a/content/en/docs/releasenotes/marketplace/general-marketplace/_index.md b/content/en/docs/releasenotes/marketplace/general-marketplace/_index.md index 07aff3e724c..cff3034d372 100644 --- a/content/en/docs/releasenotes/marketplace/general-marketplace/_index.md +++ b/content/en/docs/releasenotes/marketplace/general-marketplace/_index.md @@ -4,7 +4,8 @@ linktitle: "General Marketplace" url: /releasenotes/marketplace/ description: "Release notes for updates to the Mendix Marketplace" weight: 35 -numberless_headings: true +cascade: + - numberless_headings: true aliases: - /releasenotes/app-store/index.html #This document is mapped to the landing page, update the link there if renaming or moving the doc file From 7158b0a25941e284854a3caef6f05fe0e417a13a Mon Sep 17 00:00:00 2001 From: Dana Breseman Date: Mon, 16 Nov 2026 13:48:16 +0100 Subject: [PATCH 04/17] Split release notes template for date vs version types --- templates/release-notes-date-template.md | 46 ++++++++++++ templates/release-notes-template.md | 43 ----------- templates/release-notes-version-template.md | 82 +++++++++++++++++++++ 3 files changed, 128 insertions(+), 43 deletions(-) create mode 100644 templates/release-notes-date-template.md delete mode 100644 templates/release-notes-template.md create mode 100644 templates/release-notes-version-template.md diff --git a/templates/release-notes-date-template.md b/templates/release-notes-date-template.md new file mode 100644 index 00000000000..8655ebfe3fd --- /dev/null +++ b/templates/release-notes-date-template.md @@ -0,0 +1,46 @@ +--- +title: "{YYYY} {Product} Release Notes" +linktitle: "{YYYY}" +#url: Match the URL pattern of sibling release notes. For example, /releasenotes/catalog/2026/ +#weight: Assign newer years a lower weight than older years +description: "Release notes for updates to {PRODUCT} in {YYYY}." +#If this page is mapped to a landing page, update the link there when renaming or moving it. +--- + +[//]: # "Use for products released by date. Text in {braces} is a placeholder; replace it. Headings without braces are literal. One file per year, newest first. For each later date, add a new date section above the previous one. For a new month, add a new month section above the previous one, with the same structure. Write only customer-facing changes. Use only the elements that apply, and match sibling release notes." + +## {Month YYYY} + +### {Month D, YYYY} + +#### New Features + +[//]: # "Use for a major new feature that customers can see and use." + +* We added {description}. + +#### Improvements + +[//]: # "Use for a functional fix or minor new feature that makes behavior more consistent or predictable." + +* We improved {description}. + +#### Fixes + +[//]: # "Use for a bug fix that customers reported or that changes product behavior. List notes with Zendesk tickets first, lowest ticket number at the top." + +* We fixed an issue where {description}. (Ticket {number}) + +#### Deprecations + +[//]: # "Use for functionality that is no longer available or will be removed in a future version." + +* We deprecated {description}. It will be removed on {Month D, YYYY}. Use {alternative} instead. +* We removed {description}. Use {alternative} instead. +* We dropped support for {description}, as it is no longer supported by the vendor. + +#### Limitations + +[//]: # "Use for a limitation that won't be fixed and has a workaround. Also document it on the product page." + +* {Describe the limitation.} diff --git a/templates/release-notes-template.md b/templates/release-notes-template.md deleted file mode 100644 index 490f896930c..00000000000 --- a/templates/release-notes-template.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -title: "Enter the title of the document - this should be unique to aid Google indexing" -numberless_headings: true #Prevent automatic heading numbering when this page renders -#url: Set the relative URL of the document; after the name of the main directory/product the document is in, use the document title; example for document titled my-new-page.md, in refguide directory: /refguide/my-new-page/ -#weight: Enter the position of the document compared to other 'child' documents at the same level; number by 10 (for first), 20, 30, etc. for easy ordering of other documents in the future if necessary; don't add brackets or quotation marks -#description: "The release notes for _____ version ____ with details on new features, bug fixes, and known issues." -#draft: Set to true if page should not appear in production -#ki: keep this line a comment and use to reference Jira issues for KIs in order to track fixes ---- - -## {Version or Release Date} - -**Release date:_____** - -### New Features - -[//]: # "Include links/references to the Mendix Community ideas when available." - -#### {Major new feature specifically named in heading} - -#### Other New Features (if necessary with above specific headings) - -### Improvements - -[//]: # "Include links/references to the Mendix Community ideas when available." - -#### Performance Improvements - -#### {Major improvement specifically named in heading} - -#### Other Improvements - -### Fixes - -### Deprecations - -### Limitations - -### Breaking Changes - -### Known Issues - -[//]: # "Document fixes in this release for known issues in older release notes. Update older release notes with links to fixes" diff --git a/templates/release-notes-version-template.md b/templates/release-notes-version-template.md new file mode 100644 index 00000000000..49af6b6e845 --- /dev/null +++ b/templates/release-notes-version-template.md @@ -0,0 +1,82 @@ +--- +title: "{Major.Minor Version Number, for example 10.18}" +#url: Match the URL pattern of sibling release notes. For example, /releasenotes/studio-pro/11.16/ +#weight: Match the order of sibling release notes +description: "The release notes for {PRODUCT} {VERSION} (including all patches) with details on new features, bug fixes, and known issues." +#If this page is mapped to a landing page, update the link there when renaming or moving it. +#KI: Reference Jira issues for known issues here. Example: # KI: "Short issue name": ABC-1234 +--- + +[//]: # "Use for products released by version. Text in {braces} is a placeholder; replace it. Headings without braces are literal. Write only customer-facing changes, newest patch first. For each later patch, add a new version section above the previous one, with the same structure. Use only the elements that apply, and match sibling release notes." + +[//]: # "Blog post used with Studio Pro only. Remove for other products." + +{{% alert color="info" %}}For highlights of this release, see the [{Release blog post title}]({URL}) blog post.{{% /alert %}} + +## {Major.Minor.Patch Version Number} {#{anchor, for example 10181}} + +**Release date: {Month D, YYYY}** + +[//]: # "Button used with Studio Pro only. Remove for other products." + +{{% button color="info" href="{Download URL}" text="Go to Marketplace" title="Download version {Major.Minor.Patch Version Number} from Marketplace" %}} + +### New Features + +[//]: # "Use for a major new feature that customers can see and use. Give a major feature its own heading, then group the rest under Other New Features. If no feature needs its own heading, use a flat list." + +#### {Major New Feature Name} + +{Name the feature and describe it, including the user benefit.} + +#### Other New Features + +* We added {description}. + +### Improvements + +[//]: # "Use for a functional fix or minor new feature that makes behavior more consistent or predictable. Group the rest under Other Improvements when you use subheadings, such as Performance. Otherwise use a flat list." + +#### Performance + +* We improved {description}. + +#### Other Improvements + +* We improved {description}. + +### Fixes + +[//]: # "Use for a bug fix that customers reported or that changes product behavior. List notes with Zendesk tickets first, lowest ticket number at the top." + +* We fixed an issue where {description}. (Ticket {number}) + +### Deprecations + +[//]: # "Use for functionality that is no longer available or will be removed in a future version." + +* We deprecated {description}. It will be removed in {version}. Use {alternative} instead. +* We removed {description}. Use {alternative} instead. +* We dropped support for {description}, as it is no longer supported by the vendor. + +### Breaking Changes + +[//]: # "Use for a technical change that can break existing apps or workflows." + +* We changed {description}. + +### Limitations + +[//]: # "Use for a limitation that won't be fixed in the same major version and has a workaround. Also document it on the product page." + +* {Describe the limitation.} + +### Known Issues + +[//]: # "Use for an issue that will be fixed in the same major version. Repeat each open issue in every later version and patch section until it's fixed. Add a ticket number if available." +[//]: # "When it's fixed, add a Fixed in link to the earlier notes and remove it from the new notes' open list. In the Fixes section, add an anchor to the fix note, such as , and link back to the known issue. List fixed issues first, then issues with workarounds, then the rest." + +* {Describe the issue.} (Ticket {number}) + * Workaround: {Describe the workaround.} +* {Describe the fixed issue.} + * Fixed in [{version}](/releasenotes/{product}/{version}/#ki-fix-{name}). From 9048fc9bcc0578ef15f6651faf81042fe64a527d Mon Sep 17 00:00:00 2001 From: Dana Breseman Date: Mon, 16 Nov 2026 13:48:27 +0100 Subject: [PATCH 05/17] Make Copilot templates reference generic --- .github/copilot-instructions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index 23c98cc48b5..6365b13c853 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -125,7 +125,7 @@ For comprehensive shortcode examples and edge cases, read `community-tools/contr If asked to create new content: -1. Read the appropriate template from `templates/`: `how-to-template.md`, `reference-template.md`, `marketplace-component-page-template.md`, or `release-notes-template.md` +1. Read the appropriate template from `templates/` 2. Create the new file based on the template 3. Remove comment lines (`#`) from the template 4. Follow the editorial workflow above From d3e722001a00ec9add4d33e285707f19960e3765 Mon Sep 17 00:00:00 2001 From: Dana Breseman Date: Mon, 16 Nov 2026 13:48:40 +0100 Subject: [PATCH 06/17] Fix numberless_headings cascade --- content/en/docs/releasenotes/catalog/2026.md | 1 - content/en/docs/releasenotes/catalog/_index.md | 3 ++- content/en/docs/releasenotes/community-tools/2026.md | 1 - content/en/docs/releasenotes/community-tools/_index.md | 3 ++- content/en/docs/releasenotes/control-center/2026.md | 1 - content/en/docs/releasenotes/control-center/_index.md | 5 +++-- content/en/docs/releasenotes/marketplace/_index.md | 3 ++- 7 files changed, 9 insertions(+), 8 deletions(-) diff --git a/content/en/docs/releasenotes/catalog/2026.md b/content/en/docs/releasenotes/catalog/2026.md index ebc2f55386e..0171f264de0 100644 --- a/content/en/docs/releasenotes/catalog/2026.md +++ b/content/en/docs/releasenotes/catalog/2026.md @@ -4,7 +4,6 @@ linktitle: "2026" url: /releasenotes/catalog/2026/ description: "Release notes for updates to the Mendix Catalog in 2026." weight: 10 -numberless_headings: true #This document is mapped to the landing page, update the link there if renaming or moving the doc file. --- diff --git a/content/en/docs/releasenotes/catalog/_index.md b/content/en/docs/releasenotes/catalog/_index.md index 562fb2550e2..78fdd3eafad 100644 --- a/content/en/docs/releasenotes/catalog/_index.md +++ b/content/en/docs/releasenotes/catalog/_index.md @@ -4,7 +4,8 @@ linktitle: "Catalog" url: /releasenotes/catalog/ description: "Release notes for updates to the Mendix Catalog" weight: 36 -numberless_headings: true +cascade: + - numberless_headings: true aliases: - /releasenotes/data-hub/ #This document is mapped to the landing page, update the link there if renaming or moving the doc file. diff --git a/content/en/docs/releasenotes/community-tools/2026.md b/content/en/docs/releasenotes/community-tools/2026.md index bfb90bd42e0..0b54e25383e 100644 --- a/content/en/docs/releasenotes/community-tools/2026.md +++ b/content/en/docs/releasenotes/community-tools/2026.md @@ -4,7 +4,6 @@ linktitle: "2026" url: /releasenotes/community-tools/2026/ description: "2026 Release notes for the community tools in the Mendix Platform." weight: 1 -numberless_headings: true --- ## October 2026 diff --git a/content/en/docs/releasenotes/community-tools/_index.md b/content/en/docs/releasenotes/community-tools/_index.md index f6a96b3770a..630a88d53f4 100644 --- a/content/en/docs/releasenotes/community-tools/_index.md +++ b/content/en/docs/releasenotes/community-tools/_index.md @@ -4,7 +4,8 @@ linktitle: "Community" url: /releasenotes/community-tools/ description: "Release notes for the community tools in the Mendix Platform." weight: 37 -numberless_headings: true +cascade: + - numberless_headings: true #This document is mapped to the landing page, update the link there if renaming or moving the doc file. --- diff --git a/content/en/docs/releasenotes/control-center/2026.md b/content/en/docs/releasenotes/control-center/2026.md index c0274098e39..3d424bf2579 100644 --- a/content/en/docs/releasenotes/control-center/2026.md +++ b/content/en/docs/releasenotes/control-center/2026.md @@ -4,7 +4,6 @@ linktitle: "2026" url: /releasenotes/control-center/2026/ description: "2026 Release notes for Control Center" weight: 1 -numberless_headings: true --- ## November 2026 diff --git a/content/en/docs/releasenotes/control-center/_index.md b/content/en/docs/releasenotes/control-center/_index.md index 8b1f9c2cc2b..9eb8660c49c 100644 --- a/content/en/docs/releasenotes/control-center/_index.md +++ b/content/en/docs/releasenotes/control-center/_index.md @@ -4,8 +4,9 @@ linktitle: "Control Center" url: /releasenotes/control-center/ description: "Release notes for Control Center" weight: 30 -numberless_headings: true -#This document is mapped to the landing page, update the link there if renaming or moving the doc file. +cascade: + - numberless_headings: true +#This document is mapped to the landing page. Update the link there if renaming or moving the doc file. --- These release notes cover changes to the app management functionality and other features of the [Mendix Control Center](/control-center/). diff --git a/content/en/docs/releasenotes/marketplace/_index.md b/content/en/docs/releasenotes/marketplace/_index.md index 10967e1e4c2..76a795d9839 100644 --- a/content/en/docs/releasenotes/marketplace/_index.md +++ b/content/en/docs/releasenotes/marketplace/_index.md @@ -4,7 +4,8 @@ linktitle: "Marketplace" url: /releasenotes/marketplace-category/ description: "Release notes for updates to the Mendix Marketplace, ATD, and ATS" weight: 35 -numberless_headings: true +cascade: + - numberless_headings: true aliases: - /releasenotes/app-store/index.html #This document is mapped to the landing page, update the link there if renaming or moving the doc file. From 6e8ab751802c4295e7ba86d0f9fc09139a20b44a Mon Sep 17 00:00:00 2001 From: Dana Breseman Date: Mon, 16 Nov 2026 15:06:00 +0100 Subject: [PATCH 07/17] Uncomment URL in template --- templates/release-notes-date-template.md | 2 +- templates/release-notes-version-template.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/templates/release-notes-date-template.md b/templates/release-notes-date-template.md index 8655ebfe3fd..0a053858639 100644 --- a/templates/release-notes-date-template.md +++ b/templates/release-notes-date-template.md @@ -1,7 +1,7 @@ --- title: "{YYYY} {Product} Release Notes" linktitle: "{YYYY}" -#url: Match the URL pattern of sibling release notes. For example, /releasenotes/catalog/2026/ +url: /releasenotes/{product}/{year}/ # Match the URL pattern of sibling release notes, for example /releasenotes/catalog/2026/ #weight: Assign newer years a lower weight than older years description: "Release notes for updates to {PRODUCT} in {YYYY}." #If this page is mapped to a landing page, update the link there when renaming or moving it. diff --git a/templates/release-notes-version-template.md b/templates/release-notes-version-template.md index 49af6b6e845..9a68c8ba3a7 100644 --- a/templates/release-notes-version-template.md +++ b/templates/release-notes-version-template.md @@ -1,6 +1,6 @@ --- title: "{Major.Minor Version Number, for example 10.18}" -#url: Match the URL pattern of sibling release notes. For example, /releasenotes/studio-pro/11.16/ +url: /releasenotes/{product}/{version}/ # Match the URL pattern of sibling release notes, for example /releasenotes/studio-pro/11.16/ #weight: Match the order of sibling release notes description: "The release notes for {PRODUCT} {VERSION} (including all patches) with details on new features, bug fixes, and known issues." #If this page is mapped to a landing page, update the link there when renaming or moving it. From cf1e143d98b769242b5dbaa65f3312536b217752 Mon Sep 17 00:00:00 2001 From: Dana Breseman Date: Mon, 16 Nov 2026 16:37:29 +0100 Subject: [PATCH 08/17] Update how-to template --- templates/how-to-template.md | 47 +++++++++++++++++++++--------------- 1 file changed, 27 insertions(+), 20 deletions(-) diff --git a/templates/how-to-template.md b/templates/how-to-template.md index b255e642192..f226ce5356d 100644 --- a/templates/how-to-template.md +++ b/templates/how-to-template.md @@ -1,47 +1,54 @@ --- -title: "Enter the title of the document - this should be unique to aid Google indexing" -#url: Set the relative URL of the document; after the name of the main directory/product the document is in, use the document title; example for document titled my-new-page.md, in refguide directory: /refguide/my-new-page/ -#linktitle: Enter a short title to be used in the left side menu; increases readability and navigation through the menu -#weight: Enter the position of the document compared to other 'child' documents at the same level; number by 10 (for first), 20, 30, etc. for easy ordering of other documents in the future if necessary; don't add brackets or quotation marks -#description: "Set a description with a maximum of 140 characters; this should describe what the goal of the document is, and it can be different from the document introduction; this is optional, and it can be removed" -#draft: Set to true if page should not appear in production +title: "{How-to Title}" # Start with a bare infinitive and name what the reader accomplishes (for example, Set Up Anonymous User Security) +url: /{section}/{page-name}/ # Match the URL pattern of sibling pages (for example, /howto/security/set-up-anonymous-user-security/) +#linktitle: Optional. If the title is longer than 40 characters, add a short title for the left navigation +#weight: Optional. Lower numbers appear first among sibling pages. +description: "Describes how to {task}." --- +[//]: # "Use for step-by-step guides that help readers reach a goal. Text in {braces} is a placeholder; replace it. Headings without braces are literal. Use only the elements that apply, and match sibling pages." + ## Introduction -{Describe what this how-to will cover and what the user will learn.} +{Describe what problem this how-to solves and why it matters to the user.} + +[//]: # "Optional: Keep the following list when the how-to covers two or more distinct tasks or outcomes. Omit it when the introduction already states the single goal. Make each item a concrete task outcome (such as create, build, or configure)." -This how-to teaches you how to do the following: +This how-to shows you how to do the following: -* Create... -* Build... -* Configure... +* {Outcome 1} +* {Outcome 2} ## Prerequisites -{If there are no prerequisites, leave this section out} +[//]: # "Optional: Keep this section when the steps depend on something the reader needs first, such as a software version, an existing app or module, access rights, a required configuration, or another how-to or documentation page. List only what the steps require. Omit the section if there are none. Don't list baseline knowledge." -Before starting this how-to, make sure you have completed the following prerequisites: +Before starting this how-to, make sure you have the following: * {Prerequisite 1} * {Prerequisite 2} -## {Title of Section Using Present Participle Verb/Gerund} +## {Section Title} + +[//]: # "Start the heading with a gerund that names the task (for example, Setting Up Security). Make one section for each distinct stage of the task, with its own steps. Add or remove sections as the task requires." +[//]: # "Optional: Add an image under a step where the reader needs to recognize a screen, dialog box, or result. Don't add one for every step." To {do this task}, follow these steps: 1. {Step 1} + + {{< figure src="/attachments/{path}/{image-name}.png" alt="{Describe the image.}" >}} + 2. {Step 2} -{{< figure src="/attachments/rest-of-image-path/image-name-and-extension" >}} +### {Subsection Title} -### {Title of Sub-Section} +[//]: # "Optional: Use a subsection for a sub-task with its own steps, an alternative approach, an example the reader can skip, or a common problem and its solution." -{Use sub-sections for more detail.} +{Describe the sub-task, alternative approach, example, or problem and solution.} ## Read More -* {Link 1} -* {Link2} – {an explanation when necessary especially if this is a third-party link} +[//]: # "Optional: List supplementary links only. Don't repeat cross-references used earlier in the page." -{Make sure this section contains a bulleted list only with explanations where necessary. Do not just repeat cross-references you used throughout the document, but list useful supplementary links here.} +* [{Link title}]({URL}) – {Explanation, if needed, especially for third-party links.} From 562ba0cb72c51b6b0ce61bd984a7656bdc7c57a2 Mon Sep 17 00:00:00 2001 From: Dana Breseman Date: Mon, 16 Nov 2026 16:38:22 +0100 Subject: [PATCH 09/17] Add image and frontmatter directions --- .claude/skills/docs-new-page/SKILL.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.claude/skills/docs-new-page/SKILL.md b/.claude/skills/docs-new-page/SKILL.md index 3359b8d4a1f..ec799b3414e 100644 --- a/.claude/skills/docs-new-page/SKILL.md +++ b/.claude/skills/docs-new-page/SKILL.md @@ -17,10 +17,10 @@ Draft a new page by following these steps: 4. Read the appropriate template from `templates/`. 5. Create the new file based on the template. File names must be simple, lowercase, and hyphen-separated. 6. Clean up the template: - * In the front matter, uncomment and complete `url` and `description`. Delete any unused commented fields. + * In the front matter, complete `title`, `url`, and `description`, plus any other fields the page needs. Uncomment those fields, and delete the commented fields you don't use. * Replace or remove every `{…}` placeholder and instruction comment. * Delete optional sections that don't apply. -7. Complete the introduction and the remaining sections. Content varies by content type. +7. Complete the introduction and the remaining sections. Content varies by content type. Add images only if the user provides them. Where an image is needed and none is available, leave out the `figure` shortcode and list the location in your final summary. 8. Verify that any linked pages exist in the repo, using each target page's `url` front matter field. Link to the related pages found in step 3. 9. Run the `docs-copyedit` and `docs-alt-text` skills on the new page. From bc1853efff3c034f1ee455cd21ff67d185d47d1e Mon Sep 17 00:00:00 2001 From: Dana Breseman Date: Tue, 17 Nov 2026 14:51:21 +0100 Subject: [PATCH 10/17] Update Marketplace Components template --- .../marketplace-component-page-template.md | 64 ++++++++++++++----- 1 file changed, 48 insertions(+), 16 deletions(-) diff --git a/templates/marketplace-component-page-template.md b/templates/marketplace-component-page-template.md index f8d195c9c0e..8afd12388d8 100644 --- a/templates/marketplace-component-page-template.md +++ b/templates/marketplace-component-page-template.md @@ -1,48 +1,80 @@ --- -title: "Enter the title of the document - this should be unique to aid Google indexing" -#url: Set the relative URL of the document; after the name of the main directory/product the document is in, use the document title; example for document titled my-new-page.md, in refguide directory: /refguide/my-new-page/ -#linktitle: Enter a short title to be used in the left side menu; increases readability and navigation through the menu -#weight: Enter the position of the document compared to other 'child' documents at the same level; number by 10 (for first), 20, 30, etc. for easy ordering of other documents in the future if necessary; don't add brackets or quotation marks -#description: "Set a description with a maximum of 140 characters; this should describe what the goal of the document is, and it can be different from the document introduction; this is optional, and it can be removed" -#draft: Set to true if page should not appear in production +title: "{Component Name}" # Use the component name as it appears in Marketplace +url: /{section}/{page-name}/ # Match the URL pattern of sibling pages (for example, /appstore/modules/mendix-feedback/) +#linktitle: Optional. If the title is longer than 40 characters, add a short title for the left navigation +#weight: Optional. Lower numbers appear first among sibling pages. +description: "Describes the {Component Name} {module, widget, or connector}, which lets you {do what it does}." --- +[//]: # "Use for pages that document a platform-supported Marketplace component, such as a module, widget, or connector. Text in {braces} is a placeholder; replace it. Headings without braces are literal. Use only the sections that apply, and match sibling pages." + ## Introduction -{Provide a basic description of what this platform-supported Mendix Marketplace component does.} +{Describe what the component does. Start with the component name, linked to its Marketplace page.} ### Typical Use Cases +[//]: # "Optional: Keep this subsection when readers need examples of when to use the component." + +{Describe the main scenarios the component is used for.} + ### Features +[//]: # "Optional: Keep this subsection when readers need a quick overview of what the component can do." + +{Component Name} has the following features: + +* {Describe a feature.} + ### Limitations +[//]: # "Optional: Keep this subsection when readers need to know about restrictions." + +{Component Name} has the following limitations: + +* {Describe the limitation.} + ### Prerequisites +[//]: # "Optional: Keep this subsection when using the component depends on something the reader needs first, such as a Studio Pro version, an account or access rights with a provider, or a resource that must exist first. List required Marketplace modules under Dependencies instead. Omit the subsection if there are none. Don't list baseline knowledge." + +Before using {Component Name}, make sure you have the following: + +* {Prerequisite 1} +* {Prerequisite 2} + ### Dependencies -{List important dependencies, especially when they are other Marketplace components.} +[//]: # "Optional: Keep this subsection to list the Marketplace modules the component requires. If a module is required only for certain versions of the component or Studio Pro, say which." -### Demo App +{Component Name} requires the following Marketplace modules: -{Provide a link to a maintained demo app where the component is used if available.} +* [{Module Name}]({URL}) ## Installation -{Describe the basic installation of the component if necessary.} +[//]: # "Add any steps the component needs after import, such as setting an After startup microflow or adding a module role. Include version or upgrade warnings, and if the component comes with an app template or starter app that the reader may be using, say so and tell readers they can skip installing it." + +Follow the instructions in [Using Marketplace Content](/appstore/use-content/), and add any required modules listed under [Dependencies](#dependencies). ## Configuration -{Describe the properties to be configured.} +[//]: # "Use a subsection for each area to configure, such as a widget property tab or a connector setting. Widgets often call this section Properties Pane." -## Usage +{Describe the properties and settings to configure.} -{Optional: Provide more info for general use cases here if desired. You should provide this info in a reference guide page or how-to for more specific or advanced use cases.} +[//]: # "Less common optional sections: Usage (for general use after configuration; put step-by-step walkthroughs in a how-to), Technical Reference (for entities, activities, and other items the component provides), Styling, and Demo App (or Showcase App). Add them, and any sections specific to this component, after Configuration, and match sibling pages." ## Troubleshooting -{Optional: Provide basic troubleshooting info for configuration here if necessary. You should provide this info in a reference guide page or how-to for more specific use cases.} +[//]: # "Optional: Use a subsection for each common problem and its solution. + +### {Problem} + +{Describe the cause and the solution.} ## Read More -{Add links to related documents and blog posts. Contextualize necessary third-party links in the above sections, as they should not be put here.} +[//]: # "Optional: List supplementary links only. Don't repeat cross-references used earlier in the page." + +* [{Link title}]({URL}) – {Explanation, if needed} From 8ba1e57e56c453db5729f789d8c075cb1b951f33 Mon Sep 17 00:00:00 2001 From: Dana Breseman Date: Tue, 17 Nov 2026 14:51:42 +0100 Subject: [PATCH 11/17] "say which" -> "specify the version" --- templates/marketplace-component-page-template.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/templates/marketplace-component-page-template.md b/templates/marketplace-component-page-template.md index 8afd12388d8..f4631e89f6c 100644 --- a/templates/marketplace-component-page-template.md +++ b/templates/marketplace-component-page-template.md @@ -45,7 +45,7 @@ Before using {Component Name}, make sure you have the following: ### Dependencies -[//]: # "Optional: Keep this subsection to list the Marketplace modules the component requires. If a module is required only for certain versions of the component or Studio Pro, say which." +[//]: # "Optional: Keep this subsection to list the Marketplace modules the component requires. If a module is required only for certain versions of the component or Studio Pro, specify the version." {Component Name} requires the following Marketplace modules: From 95224f27067f67f839612406dc804224b1cefc2c Mon Sep 17 00:00:00 2001 From: Dana Breseman Date: Tue, 17 Nov 2026 15:14:07 +0100 Subject: [PATCH 12/17] Add a quote --- templates/marketplace-component-page-template.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/templates/marketplace-component-page-template.md b/templates/marketplace-component-page-template.md index f4631e89f6c..3afc63c03e3 100644 --- a/templates/marketplace-component-page-template.md +++ b/templates/marketplace-component-page-template.md @@ -67,7 +67,7 @@ Follow the instructions in [Using Marketplace Content](/appstore/use-content/), ## Troubleshooting -[//]: # "Optional: Use a subsection for each common problem and its solution. +[//]: # "Optional: Use a subsection for each common problem and its solution." ### {Problem} From 553ae4a2f3906ea4b0acafd4974525a02e7da8ab Mon Sep 17 00:00:00 2001 From: Dana Breseman Date: Tue, 17 Nov 2026 17:44:45 +0100 Subject: [PATCH 13/17] Add subsection guidance --- .github/copilot-instructions.md | 3 ++- CLAUDE.md | 3 ++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index 6365b13c853..e1bb07318b4 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -60,6 +60,7 @@ Search the tree to understand where your topic belongs before creating a new fil * **Terminology** – Capitalize product names (Mendix Portal, Studio Pro, Team Server); use “microflow”, “nanoflow”, etc. consistently. Never use e.g. or i.e. * **Text formatting** – Reserve bold for UI labels, button names, menu items, or other interface text, or for introductions in list items. Don't use italics except to refer to titles and sections. Use wording or alert shortcodes for emphasis; don't use text formatting for emphasis. Use code font only to wrap literal code, filenames, paths, or command-line input. Use `` for keyboard shortcuts. * **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 numbers. +* **Subsections** – A subsection is the content under a heading one level below its section, such as an H3 under an H2. Add one only for two or more parts that each need a paragraph or more. For a set of options or components that contain figures or tables, use one subsection per member instead of a list or table. Keep procedure steps in a numbered list, even with figures. A linked part can be shorter or stand alone if it has an anchor ID. * **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** – Use four spaces to indent content—for example, to create a sub-list or nest an image or code block in a list. Alerts 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). @@ -125,7 +126,7 @@ For comprehensive shortcode examples and edge cases, read `community-tools/contr If asked to create new content: -1. Read the appropriate template from `templates/` +1. Read `templates/README.md` to choose the appropriate template, then read that template from `templates/` 2. Create the new file based on the template 3. Remove comment lines (`#`) from the template 4. Follow the editorial workflow above diff --git a/CLAUDE.md b/CLAUDE.md index 920e0c4b7d9..9f5eaf345f3 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -62,6 +62,7 @@ Before creating a new file, use Glob to explore the directory structure and unde * **Terminology** – Capitalize product names (Mendix Portal, Studio Pro, Team Server); use "microflow", "nanoflow", etc. consistently. Never use e.g. or i.e. * **Text formatting** – Reserve bold for UI labels, button names, menu items, or other interface text, or for introductions in list items. Don't use italics except to refer to titles and sections. Use wording or alert shortcodes for emphasis; don't use text formatting for emphasis. Use code font only to wrap literal code, filenames, paths, or command-line input. Use `` for keyboard shortcuts. * **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. +* **Subsections** – A subsection is the content under a heading one level below its section, such as an H3 under an H2. Add one only for two or more parts that each need a paragraph or more. For a set of options or components that contain figures or tables, use one subsection per member instead of a list or table. Keep procedure steps in a numbered list, even with figures. A linked part can be shorter or stand alone if it has an anchor ID. * **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** – 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). @@ -140,7 +141,7 @@ Less common shortcodes (`button`, `expandable-table`, `youtube`, `vidyard`, `swa If asked to create new content: -1. List `templates/` and read the template that matches the content type. +1. Read `templates/README.md` to choose the template that matches the content type, then read that template. 2. Use Write tool to create the new file based on the template. 3. Remove the guidance comments from the template: `#` comments and inline comments in the front matter, and `[//]: #` comments in the body. Complete `title`, `url`, and `description`. 4. Follow the editorial workflow above. From 3b58273333c48f9a6f23c5828dc5a403dd6db3f3 Mon Sep 17 00:00:00 2001 From: Dana Breseman Date: Tue, 17 Nov 2026 17:45:06 +0100 Subject: [PATCH 14/17] Add section-index-template --- templates/section-index-template.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 templates/section-index-template.md diff --git a/templates/section-index-template.md b/templates/section-index-template.md new file mode 100644 index 00000000000..f21e977d6f0 --- /dev/null +++ b/templates/section-index-template.md @@ -0,0 +1,20 @@ +--- +title: "{Section Title}" +url: /{section}/{page-name}/ # Match the URL pattern of sibling pages (for example, /control-center/people/) +#linktitle: Optional. If the title is longer than 40 characters, add a short title for the left navigation +#weight: Optional. Lower numbers appear first among sibling pages. +description: "Describes the {section or topic}." # Also appears in the parent page's list of child pages +no_list: false # Keep this line so the layout adds a list of the child pages below the page content. Without it, no list appears. +description_list: true # Shows bulleted links, each with the child's description. Use it for most section indices. +#simple_list: true Optional. Set to true to show links only. Use it when the child titles explain themselves, such as release notes by year or version, or a set of similar reference pages. It overrides description_list. +--- + +[//]: # "Use for _index.md files that introduce a section and link to its child pages. Save the file as _index.md in the section folder. Text in {braces} is a placeholder; replace it. Headings without braces are literal. Use only the elements that apply, and match sibling pages." + +## Introduction + +{Describe what this section covers and what users can do with its pages.} + +## Documents in This Category + +[//]: # "Optional: Keep this heading when the layout adds a list of child pages (when no_list is set to false). Make it the last heading and put nothing under it, because the list appears directly below the page content." From 775a0bd54f755a83eb1587513bad3a2c656b8495 Mon Sep 17 00:00:00 2001 From: Dana Breseman Date: Tue, 17 Nov 2026 17:45:16 +0100 Subject: [PATCH 15/17] Add fallback template --- templates/general-page-template.md | 34 ++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 templates/general-page-template.md diff --git a/templates/general-page-template.md b/templates/general-page-template.md new file mode 100644 index 00000000000..492cb74c84e --- /dev/null +++ b/templates/general-page-template.md @@ -0,0 +1,34 @@ +--- +title: "{Page Title}" +url: /{section}/{page-name}/ # Match the URL pattern of sibling pages (for example, /refguide/session-management/) +#linktitle: Optional. If the title is longer than 40 characters, add a short title for the left navigation +#weight: Optional. Lower numbers appear first among sibling pages. +description: "Describes {the topic}." # Start with Describes, for example, "Describes the {topic}" or "Describes how {topic works}" +--- + +[//]: # "Use only when no other template fits. Text in {braces} is a placeholder; replace it. Headings without braces are literal. Use only the elements that apply, and match sibling pages." +[//]: # "Read sibling pages in the same folder for terminology, level of detail, and any heading that most of them share. Choose the other headings to fit your topic." + +## Introduction + +{Describe what the topic is and why it matters to the user.} + +## {Section Title} + +[//]: # "Add the sections the topic needs. Structure varies by topic, so use a heading from sibling pages only when most of them share it." + +{Explain this part of the topic.} + +[//]: # "Optional: Add an image or code block only when it does something the text can't. Use an image when the reader needs to recognize a screen or see how parts relate, and a code block for literal code or settings the reader copies. Most paragraphs need neither." + +### {Subsection Title} + +[//]: # "Optional: Use subsections only where the topic has parts that each need a paragraph or more, such as a detail, an alternative, an example the reader can skip, or a common problem and its solution. For other cases, see the Subsections rule in CLAUDE.md." + +{Describe the detail, alternative, example, or problem and solution.} + +## Read More + +[//]: # "Optional: List supplementary links only. Don't repeat cross-references used earlier in the page." + +* [{Link title}]({URL}) – {Explanation, if needed, especially for third-party links.} From 91e5069e594fbf8c4c12c33e2b8893b6a3a8cb33 Mon Sep 17 00:00:00 2001 From: Dana Breseman Date: Tue, 17 Nov 2026 17:45:30 +0100 Subject: [PATCH 16/17] Add readme for template selection --- templates/README.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 templates/README.md diff --git a/templates/README.md b/templates/README.md new file mode 100644 index 00000000000..bd10f432e84 --- /dev/null +++ b/templates/README.md @@ -0,0 +1,12 @@ +# Choosing a Template + +Go through the questions in order and use the first template that fits. Each template's opening comment says more about when to use it. + +1. Is the page an `_index.md` file that introduces a section and lists its child pages? Use `section-index-template.md`. +2. Is the page release notes? + * Released by version: use `release-notes-version-template.md`. + * Released by date: use `release-notes-date-template.md`. +3. Does the page guide readers through steps to reach a goal? Use `how-to-template.md`. +4. Does the page document a platform-supported Marketplace component, such as a module, widget, or connector? Use `marketplace-component-page-template.md`. For AWS connectors, use `marketplace-aws-connector-page-template.md`. +5. Does the page document the properties of a Studio Pro element? Use `reference-template.md`. +6. Does none of the above fit? Use `general-page-template.md`. Read sibling pages in the same folder for terminology and level of detail, and choose the other headings to fit the topic. From 22c1c9bd678e5a3df6064440241e31c136843895 Mon Sep 17 00:00:00 2001 From: Dana Breseman Date: Tue, 17 Nov 2026 18:14:21 +0100 Subject: [PATCH 17/17] Apply feedback --- .claude/skills/docs-new-page/SKILL.md | 31 ++++++++++++--------------- 1 file changed, 14 insertions(+), 17 deletions(-) diff --git a/.claude/skills/docs-new-page/SKILL.md b/.claude/skills/docs-new-page/SKILL.md index ec799b3414e..18eb4c29e3a 100644 --- a/.claude/skills/docs-new-page/SKILL.md +++ b/.claude/skills/docs-new-page/SKILL.md @@ -1,27 +1,24 @@ --- name: docs-new-page -description: Creates a new documentation page from the matching template in `templates/`. Use when the user asks to create, write, draft, or start a new documentation page or file. +description: Drafts new documentation content, as one or more new pages from the matching templates in `templates/`, as additions to existing pages, or both. Use when the user asks to create, write, draft, add to, or start new documentation pages, files, or content. user-invocable: true --- -Draft a new page by following these steps: +Draft new content by following these steps: -1. Check whether the user has provided source material for the page's content. If material is missing, ask for it in a single prompt before continuing: +1. Check whether the user has provided source material for the content. If material is missing, ask for it in a single prompt before continuing: * Links, such as Jira tickets or Confluence pages * Pasted content, such as specs, notes, a Slack thread, a transcript, a draft, a README, code or config snippets, or screenshots - * An existing page to use as a model If the user provides a link, read it only if you have a tool that can access it. If you can't access it, say so and ask the user to paste the content. -2. Explore `content/en/docs/` and decide where the page belongs (if it isn't clear, ask the user to confirm). Read the section's `_index.md` and nearby pages to match their conventions. -3. Search `content/en/docs/` for the page's main terms. Ignore the versioned folders for older Mendix versions (`refguide10`, `howto9`, and so on) unless the user says the page is for an older version. If a page already covers the entire topic, tell the user and ask whether to update that page instead. If a page covers part of it, link to that page instead of repeating the covered content, and ask the user whether the missing content belongs on the existing page or on the new one. Note any pages that need a link to the new page, and tell the user at the end. -4. Read the appropriate template from `templates/`. -5. Create the new file based on the template. File names must be simple, lowercase, and hyphen-separated. -6. Clean up the template: - * In the front matter, complete `title`, `url`, and `description`, plus any other fields the page needs. Uncomment those fields, and delete the commented fields you don't use. - * Replace or remove every `{…}` placeholder and instruction comment. - * Delete optional sections that don't apply. -7. Complete the introduction and the remaining sections. Content varies by content type. Add images only if the user provides them. Where an image is needed and none is available, leave out the `figure` shortcode and list the location in your final summary. -8. Verify that any linked pages exist in the repo, using each target page's `url` front matter field. Link to the related pages found in step 3. -9. Run the `docs-copyedit` and `docs-alt-text` skills on the new page. - -Don't add product claims, technical behavior, or release facts that the user didn't provide. If more information is needed, ask the user to provide it. +2. Explore `content/en/docs/` and decide whether the content needs new pages, additions to existing pages, or both, and where each belongs (if it isn't clear, add it to the plan as an open question). Read the section's `_index.md` and nearby pages to match their conventions. +3. Search `content/en/docs/` for the content's main terms. Ignore the versioned folders for older Mendix versions (`refguide10`, `howto9`, and so on) unless the user says the page is for an older version. If a page already covers the entire topic, add to the plan the question of whether to update that page instead. If a page covers part of it, link to that page instead of repeating the covered content, and add to the plan the question of whether the missing content belongs on that page or on a new one. +4. For each new page, read `templates/README.md` to choose the appropriate template, then read that template from `templates/`. If only `general-page-template.md` fits a page, say so in the plan and ask whether to base its structure on sibling pages. For additions to an existing page, follow that page's structure. +5. Present a plan to the user for confirmation or adjustments. List each new page with its template, location, file name, and sections. List each existing page you will change with what you will add and where. Include the source material you will use. Put the open questions from steps 2 to 4 in the plan, and ask them together in one prompt. If the user hasn't said, also ask whether a release note is needed. Don't fill in missing or ambiguous information. Ask for it. +6. Create each new file based on its template. Add the planned content to existing pages in place. +7. Clean up each new page's template as described in the Content Creation Workflow in CLAUDE.md, and uncomment any optional front matter fields the page needs. Compare the optional sections with the nearby pages from step 2, and delete the ones that most of those pages don't have. If nearby pages have a section that the source material doesn't cover, don't fill it in. Ask the user for the information in a single question, and delete the section if they have none. +8. Complete the introduction and the remaining sections of each new page. Add images only if the user provides them. Where an image is needed and none is available, leave out the `figure` shortcode and list the location in your final summary. +9. Compare the files you created or changed with the input the user provided, and give the user a summary of what you did. Flag any input you left out and why. Search sibling pages and flag anything in other files that the new pages make outdated (such as labels or dates) and any conflicts with the new pages. Note any pages that need a link to the new pages. Prioritize technical accuracy. If it isn't clear which source to trust, ask the user. +10. Verify that any linked pages exist in the repo. Link to the related pages found in step 3, and link the new pages to each other where relevant. +11. Run the `docs-copyedit` and `docs-alt-text` skills on each new page and on the content you added to existing pages. +12. Run the `docs-pr-review` skill. \ No newline at end of file