Deprecate Document Templates

content/en/docs/refguide/installation/upgrading-from-10-to-11.md

@@ -27,7 +27,7 @@ Regardless of which major version you are upgrading from, we recommend you upgra
 
 1. Back up your app.
 1. Upgrade to the latest patch of Studio Pro.
-1. Upgrade widgets, modules, Marketplace components, templates, and connectors.
+1. Upgrade widgets, modules, Marketplace components, and connectors.
 1. Fix deprecations and test your app.
 1. Upgrade app to Mendix 11.
 
@@ -55,7 +55,10 @@ In general, you should not remove and re-import modules unless this is recommend
 
 After the upgrade of your marketplace content, take the next steps:
 
-1. Fix any deprecation warnings you see in development in Studio Pro, as well as in the Mendix Runtime using your console and browser console.
+1. Fix any deprecation warnings you see in development in Studio Pro, as well as in the Mendix Runtime using your console and browser console. These deprecations could include, but are not limited to, the following:
+    * [Document Templates](/refguide/document-templates/): deprecated in 10.24 
+    * [Dojo-based Mendix Client](/refguide/mendix-client/): deprecated in 11.0
+    * Deprecated Java Version: depending on your Java version you may see errors — to resolve those errors, see [Java Version Migration](/refguide/java-version-migration/)
 1. Review the major changes in the sections below.
 1. Run your app, test all functionality, and ensure it works without error.
 1. Back up or commit your Mendix 10 app so you can return to it if necessary.

content/en/docs/refguide/modeling/app-explorer/modules/_index.md

@@ -56,7 +56,7 @@ There are the following type of modules:
 | --- | --- |
 | [Constants](/refguide/constants/) | Constants are used to define a constant value (for example, to store a URL for a web service). |
 | [Datasets](/refguide/data-sets/) | A dataset can be used for reporting and is defined using either an OQL query or a custom Java action. |
-| [Document Templates](/refguide/document-templates/) | Document templates are used to model a template needed as input for a document export action that can generate all kinds of documents based on application data. They are composed much in the same way as forms. |
+| [Document Templates](/refguide/document-templates/) | **Deprecated in 11.0.0** Document Templates were used to design templates for exporting documents based on application data. |
 | [Java Actions](/refguide/java-actions/) | With Java actions, you can extend the functionality of your application in situations where it would be hard to implement the functionality in microflows. You can call a Java action from a microflow. |
 | [Regular Expressions](/refguide/regular-expressions/) | A regular expression is used by [validation rules](/refguide/validation-rules/) on an entity to describe a set of criteria that a string can match. |
 | [Rules](/refguide/rules/) | A rule defines a set of criteria. With a certain input, the rule will result in a Boolean or enumeration, depending on the criteria met. It can be called from a decision to determine the direction the microflow should go once a decision is reached. |

content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/_index.md

@@ -98,7 +98,11 @@ These activities can only be used in microflows.
 | ---| --- | --- |
 | {{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/activities/log-message.png" alt="log message" link="/refguide/log-message/" max-width=60% class="no-border" >}} | [Log message](/refguide/log-message/) | Allows you to create messages that appear in the log of your Mendix application. |
 
-## Document Generation Activities
+## Document Generation Activities (Deprecated)
+
+{{% alert color="warning" %}}
+Document generation using Document Templates was deprecated in 11.0.0. See [Document Templates](/refguide/document-templates/) for alternatives.
+{{% /alert %}}
 
 | Graphic | Name | Description |
 | --- | --- | --- |

content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/activities/generate-document.md

@@ -6,13 +6,13 @@ description: "Describes generating documents from a microflow. "
 #If moving or renaming this doc file, implement a temporary redirect and let the respective team know they should update the URL in the product. See Mapping to Products for more details.
 ---
 
-{{% alert color="info" %}}
-This activity can only be used in microflows.
+{{% alert color="warning" %}}
+**Document generation** using Document Templates was deprecated in 11.0.0 Please see the documentation of [Document Templates](/refguide/document-templates/) for alternatives.
 {{% /alert %}}
 
 ## Introduction
 
-The **Generate document** activity is used to write a document to a file, based on a [document template](/refguide/document-templates/). 
+The **Generate document** microflow activity is used to write a document to a file, based on a [document template](/refguide/document-templates/). 
 
 For more information on which types of documents can be created, see [Document Type](#document-type).
 

content/en/docs/refguide/modeling/images.md

@@ -8,7 +8,7 @@ description: "Introduces the image functionality in Studio Pro."
 
 ## Introduction
 
-Images can be used to brighten up your application. [Navigation items](/refguide/navigation-tree/) and the various kinds of [buttons](/refguide/button-widgets/) have small images (icons) to left of their captions. Images can also be used in the dynamic image widgets in [pages](/refguide/pages/) and [document templates](/refguide/document-templates/). Also, [enumeration values](/refguide/enumerations/#enum-value-properties) can have images that can then be shown in data grid columns.
+Images can be used to brighten up your application. [Navigation items](/refguide/navigation-tree/) and the various kinds of [buttons](/refguide/button-widgets/) have small images (icons) to left of their captions. Images can also be used in the dynamic image widgets in [pages](/refguide/pages/). Also, [enumeration values](/refguide/enumerations/#enum-value-properties) can have images that can then be shown in data grid columns.
 
 The **System** module contains some images that are used by the standard components. If you place a data view on a page, the **Save** and **Cancel** buttons will have images from the **System** module on them. You can always use different images if you like. The same holds for images on the control bar buttons of the data grid.
 

content/en/docs/refguide/modeling/resources/document-templates.md

@@ -0,0 +1,58 @@
+---
+title: "Document Templates"
+url: /refguide/document-templates/
+weight: 90
+aliases:
+    - /refguide/Document+Templates.html
+    - /refguide/Document+Templates
+    - /refguide/creating-your-own-documents/
+    - /refguide/data-view-document-template/
+    - /refguide/document-template/
+    - /refguide/dynamic-image-document-template/
+    - /refguide/dynamic-label-document-template/
+    - /refguide/footer-document-template/
+    - /refguide/header-document-template/
+    - /refguide/line-break-document-template/
+    - /refguide/page-break-document-template/
+    - /refguide/static-image-document-template/
+    - /refguide/static-label-document-template/
+    - /refguide/style/
+    - /refguide/template-grid-document-template/
+    - /refguide/title-document-template/
+    - /refguide/data-grid-document-template/
+    - /refguide/columns-document-template/
+    - /refguide/table-document-template/
+    - /refguide/row-document-template/
+    - /refguide/cell-document-template/
+#If moving or renaming this doc file, implement a temporary redirect and let the respective team know they should update the URL in the product. See Mapping to Products for more details.
+---
+
+{{% alert color="warning" %}}
+The use of **Document Templates** and the **Generate Document** microflow action is deprecated and will be removed in a future version of Mendix.
+{{% /alert %}}
+
+## Introduction
+
+Document Templates, previously used to design templates for exporting documents based on application data in Mendix, along with the **Generate Document** microflow action, are now deprecated and will be removed in a future Mendix release. This guide outlines the recommended alternatives for document generation.
+
+To view the documentation of Document Templates, please refer to the [Mendix 10 documentation](/refguide10/document-templates/) instead.
+
+## Alternatives
+
+Document Templates in Mendix allowed the generation of various document types. This section explains the appropriate replacement options for each previously supported document type.
+
+### PDF
+
+To generate PDF documents, use the [PDF Document Generation](/appstore/modules/document-generation/) capability, which allows you to define PDFs based on standard Mendix pages. This approach offers significantly greater flexibility and control over the layout and design of your PDF documents compared to the deprecated Document Templates.
+
+### HTML
+
+To generate HTML documents, create the HTML manually and use the token replacement capabilities of the [Mx Model Reflection](/appstore/modules/model-reflection/#token-configuration) module to insert application data. Open source tools such as [MJML](https://mjml.io/) can assist in designing visually appealing HTML, especially for email templates.
+
+### Microsoft Word
+
+Generating Microsoft Word documents is no longer supported by Mendix. However, there are several alternative solutions available — both free and paid — maintained by Mendix partners and the community that support Word document generation. These can be found in the [Mendix Marketplace](https://marketplace.mendix.com/link/search/word).
+
+### Other Formats
+
+Other formats, including Rich Text Format (.rtf) and OpenDocument Text (.odt), are no longer supported by Mendix and do not have official alternatives. We understand this may impact certain use cases, and we recommend exploring whether supported formats like PDF or HTML can meet your current needs.