Move contact page to Reference

docs/components/best-practices/development/service-integration-patterns.md

@@ -120,7 +120,7 @@ You can leverage [message buffering](/components/concepts/messages.md#message-bu
 
 Retries are not built-in, so if you need to model a loop to retry the initial service call if no response is received. And (at least in the current Zeebe version), there is no possibility to trigger error events for a receive task, which means you need to model error messages as response payload or separate message types — both are discussed later in this post.
 
-A final note for high-performance environments: These powerful messaging capabilities do not come for free and require some overhead within the engine. For pure request/response calls that return within milliseconds, none of the features are truly required. If you are looking to build a high-performance scenario, using service tasks instead of message correlation for request/response calls, you can tune your overall performance or throughput. However, as with everything performance related, the devil is in the detail, so [reach out to us](/contact) to discuss such a scenario in more depth.
+A final note for high-performance environments: These powerful messaging capabilities do not come for free and require some overhead within the engine. For pure request/response calls that return within milliseconds, none of the features are truly required. If you are looking to build a high-performance scenario, using service tasks instead of message correlation for request/response calls, you can tune your overall performance or throughput. However, as with everything performance related, the devil is in the detail, so [reach out to us](/reference/contact.md) to discuss such a scenario in more depth.
 
 **Summary And recommendations**
 

docs/components/concepts/data-retention.md

@@ -15,7 +15,7 @@ The following time-to-live settings are configured in SaaS for each application.
 - **Tasklist**: 30 days
 - **Zeebe**: 7 days
 
-If there are specific requirements for your use-case, [reach out to us](/contact/) to discuss your data retention needs under an Enterprise plan.
+If there are specific requirements for your use-case, [reach out to us](/reference/contact.md) to discuss your data retention needs under an Enterprise plan.
 For more information on development clusters in the Starter or Professional plans, refer to our [fair usage limits of those plans](https://camunda.com/legal/fair-usage-limits-for-starter-plan/).
 
 ## Additional information

docs/components/concepts/what-is-camunda-8.md

@@ -105,7 +105,7 @@ The platform and tools are usable in your environment right away, with full publ
 
 ## Next steps
 
-- To request information about Camunda 8 performance and benchmarking, refer to our [Contact](/contact/) page.
+- To request information about Camunda 8 performance and benchmarking, refer to our [Contact](/reference/contact.md) page.
 - [Introduction to Camunda 8](/guides/introduction-to-camunda-8.md)
 - [Create a Camunda 8 account](/guides/create-account.md)
 - [Migrate from Camunda 7 to Camunda 8](/guides/migrating-from-camunda-7/index.md)

docs/components/console/manage-plan/migrate-from-prof-to-starter.md

@@ -11,7 +11,7 @@ Here are a few important remarks to consider before completing the migration ste
 - Since the two plans have different types of clusters included and fees for those, we recommend comparing the [Professional plan](https://camunda.com/blog/2023/05/camunda-professional-edition-accelerate-projects/) with the [Starter plan](https://camunda.com/blog/2023/09/camunda-starter/) to [understand your monthly costs](https://camunda.com/pricing/starter-plan-price-calculator/) before the migration.
 - General users and development/production cluster reservations in the Professional plan are migrated “as is” to the Starter plan, which may result in overage costs (e.g. production clusters in Professional will be transferred to production clusters in the Starter plan). If you are not using your production cluster in the Professional plan, we recommend you delete it beforehand and create a new development cluster in the Starter plan afterward.
 - Once you have edited the plan below, the changes will take effect on the first day of your next subscription period.
-- If you have any questions, do not hesitate to [contact us](https://camunda.com/contact/).
+- If you have any questions, do not hesitate to [contact us](/reference/contact.md).
 
 :::
 

docs/components/early-access/alpha/alpha-features.md

@@ -32,7 +32,7 @@ To learn more about using alpha features, see [enabling alpha features](/compone
 :::note
 
 - Alpha features can also be included in a minor version (stable) release.
-- Although there is no maintenance service, customers can still provide feedback through designated support channels, depending on their SLAs. These channels include filing issues in the respective [GitHub repositories](https://github.com/camunda) and submitting questions and suggestions by [contacting us](/contact).
+- Although there is no maintenance service, customers can still provide feedback through designated support channels, depending on their SLAs. These channels include filing issues in the respective [GitHub repositories](https://github.com/camunda) and submitting questions and suggestions by [contacting us](/reference/contact.md).
 
 :::
 

docs/components/early-access/alpha/sap/btp-integration.md

@@ -11,5 +11,5 @@ The Camunda SAP Business Technology Platform (BTP) integration is an artifact ru
 - A generic endpoint to start BPMN processes with.
 
 :::note Important!
-The SAP BTP integration is an alpha feature available upon request. Visit [https://camunda.com/contact](https://camunda.com/contact) to contact us.
+The SAP BTP integration is an alpha feature available upon request. Visit [our contact page](/reference/contact.md) to contact us.
 :::

docs/components/early-access/alpha/sap/odata-connector.md

@@ -11,7 +11,7 @@ This Connector is designed to run in [hybrid mode](/guides/use-connectors-in-hyb
 This Connector works with Camunda 8 SaaS, and utilizes SAP BTP's [Destination](https://learning.sap.com/learning-journeys/administrating-sap-business-technology-platform/using-destinations) and [Connectivity](https://help.sap.com/docs/connectivity/sap-btp-connectivity-cf/what-is-sap-btp-connectivity) concepts to query a SAP system via both OData v2 and v4.
 
 :::note Important!
-This Connector is an alpha feature and available upon request. Visit [https://camunda.com/contact](https://camunda.com/contact) to contact us.
+This Connector is an alpha feature and available upon request. Visit [our contact page](/reference/contact.md) to contact us.
 :::
 
 ## Overview

docs/components/early-access/alpha/sap/rfc-connector.md

@@ -9,7 +9,7 @@ The SAP RFC [Connector](/components/connectors/introduction.md) is a [protocol a
 It connects to Camunda 8 SaaS, and utilizes SAP BTP's [Destination](https://learning.sap.com/learning-journeys/administrating-sap-business-technology-platform/using-destinations) and [Connectivity](https://help.sap.com/docs/connectivity/sap-btp-connectivity-cf/what-is-sap-btp-connectivity) concepts to query a SAP system via the RFC protocol to interact with remote-enabled Function Modules and BAPIs.
 
 :::note Important!
-This Connector is an alpha feature available upon request. Visit [https://camunda.com/contact](https://camunda.com/contact) to contact us.
+This Connector is an alpha feature available upon request. Visit [our contact page](/reference/contact.md) to contact us.
 :::
 
 ## Overview

docs/components/zeebe/zeebe-overview.md

@@ -20,12 +20,6 @@ With Zeebe you can:
 
 For documentation on deploying Zeebe as part of Camunda 8 Self-Managed, refer to the [deployment guide](../../self-managed/zeebe-deployment/zeebe-installation.md).
 
-## Enterprise support for Zeebe
-
-Paid support for Zeebe is available via either Camunda 8 Starter or Camunda 8 Enterprise plans. Customers can choose either plan based on their process automation requirements. Camunda 8 Enterprise customers also have the option of on-premises or private cloud deployment.
-
-Additionally, regardless of how you are working with Zeebe and Camunda 8, you can always find support through the [community](/contact/).
-
 ## Next steps
 
 - Get familiar with [technical concepts](technical-concepts/technical-concepts-overview.md).

docs/guides/migrating-from-camunda-7/index.md

@@ -53,4 +53,4 @@ As described earlier in this guide, migration is an ongoing topic and this guide
 - Discuss workload migrations (operations)
 - Eventual consistency
 
-[Reach out to us](/contact/) to discuss your specific migration use case.
+[Reach out to us](/reference/contact.md) to discuss your specific migration use case.

src/pages/contact.md → docs/reference/contact.md

@@ -1,4 +1,5 @@
 ---
+id: contact
 title: Contact
 description: Contact Camunda, submit feedback, find support using the Camunda community forum, note bug reports and feature requests, and review security notices.
 keywords:
@@ -16,15 +17,13 @@ keywords:
   ]
 ---
 
-# Contact
-
 There are a few different channels you can reach us based on your needs:
 
 - We encourage everyone to participate in our **community** via the [Camunda community forum](https://forum.camunda.io/), where you can exchange ideas with other Camunda users, as well as Camunda employees. For all other Camunda community programs and resources, visit our [Camunda Developer Hub](https://camunda.com/developers).
 
 - We welcome your **bug** reports and **feature requests** through our community channels mentioned above.
 
-- For **security-related issues**, review our [security notices](../docs/reference/notices) for the most up-to-date information on known issues and steps to report a vulnerability so we can solve the problem as quickly as possible. Do not use GitHub for security-related issues.
+- For **security-related issues**, review our [security notices](/reference/notices.md) for the most up-to-date information on known issues and steps to report a vulnerability so we can solve the problem as quickly as possible. Do not use GitHub for security-related issues.
 
 - **Feedback and support** can be submitted or requested via JIRA by following our [Enterprise support process](https://camunda.com/services/enterprise-support-guide/). All users can also find feedback and support options in the Help Center or [Camunda community forum](https://forum.camunda.io/).
 

docs/reference/regions.md

@@ -9,7 +9,7 @@ When you create a cluster in Camunda 8 SaaS, you must specify a region for that
 Currently, we make these regions available for customers on the Trial, Starter, and Enterprise Plans. Enterprise customers can discuss custom regions with their Customer Success Manager.
 
 :::note
-Our Console and Web Modeler components are currently hosted in the EU. [Contact us](https://camunda.com/contact/) if you have additional questions.
+Our Console and Web Modeler components are currently hosted in the EU. [Contact us](/reference/contact.md) if you have additional questions.
 :::
 
 Below, find a list of regions currently supported in Camunda 8 SaaS.
@@ -28,5 +28,5 @@ Below, find a list of regions currently supported in Camunda 8 SaaS.
 You can find the locations behind the region codes [on the Google page](https://cloud.google.com/about/locations).
 
 :::note
-Running on a Trial or Starter plan and want to try a different region, or interested in other regions or cloud providers? [Contact us](https://camunda.com/contact/) as we are able to make additional regions available on request.
+Running on a Trial or Starter plan and want to try a different region, or interested in other regions or cloud providers? [Contact us](/reference/contact.md) as we are able to make additional regions available on request.
 :::

docs/reference/release-notes/860.md

@@ -324,7 +324,7 @@ You can now synchronize process applications with GitHub using a native integrat
 - After an admin approves and configures the basic integration, you can select a path to synchronize with in a GitHub repository.
 - You can pull changes from GitHub to integrate contributions from Desktop Modeler users, make changes, and begin the process to make a pull request so every change is properly reviewed and approved.
 
-Do you use another tool such as GitLab or Bitbucket? [Contact us](/contact/) to make your request. Until then, you can use our Connectors system and the CI/CD blueprint on the Marketplace.
+Do you use another tool such as GitLab or Bitbucket? [Contact us](/reference/contact.md) to make your request. Until then, you can use our Connectors system and the CI/CD blueprint on the Marketplace.
 
 ### Persist data across sessions
 

docs/reference/status.md

@@ -21,4 +21,4 @@ To receive service status updates:
 
 ## Support
 
-Support can be requested by subscription or enterprise customers via [JIRA](https://jira.camunda.com/projects/SUPPORT/). Otherwise, [contact us](/contact). For more information about Enterprise support and additional support resources, see [Enterprise Support](https://camunda.com/services/support/).
+Support can be requested by subscription or enterprise customers via [JIRA](https://jira.camunda.com/projects/SUPPORT/). Otherwise, [contact us](/reference/contact.md). For more information about Enterprise support and additional support resources, see [Enterprise Support](https://camunda.com/services/support/).

docs/reference/supported-environments.md

@@ -8,7 +8,7 @@ The supported environments page lists browsers, operating systems, clients, depl
 
 **If the particular technology is not listed, we cannot resolve issues caused by the usage of that unlisted technology.**
 
-You may [raise a feature request](/contact) that will be evaluated by our product teams to provide official support from Camunda, or you can make a [help request](/contact) to work with Consulting services.
+You may [raise a feature request](/reference/contact.md) that will be evaluated by our product teams to provide official support from Camunda, or you can make a [help request](/reference/contact.md) to work with Consulting services.
 
 Recommendations are denoted with [recommended], however, other listed options are supported as well.
 

docs/self-managed/modeler/web-modeler/installation.md

@@ -4,4 +4,4 @@ title: Installation
 description: "Details on installation of Web Modeler Self-Managed."
 ---
 
-Refer to the [installation guide](/self-managed/setup/overview.md) for details on how to install Web Modeler, and the [contact page](/contact) for guidance on obtaining Camunda 8 credentials.
+Refer to the [installation guide](/self-managed/setup/overview.md) for details on how to install Web Modeler, and the [contact page](/reference/contact.md) for guidance on obtaining Camunda 8 credentials.

docs/self-managed/react-components/components.md

@@ -16,6 +16,6 @@ Camunda 8 Self-Managed users may also use [Desktop Modeler](../../components/mod
 
 :::note
 
-To obtain or retrieve your Camunda 8 credentials for Enterprise licenses, visit the [contact page](/contact).
+To obtain or retrieve your Camunda 8 credentials for Enterprise licenses, visit the [contact page](/reference/contact.md).
 
 :::

docusaurus.config.js

@@ -269,7 +269,7 @@ module.exports = {
             },
             {
               label: "Contact",
-              to: "contact",
+              to: "docs/reference/contact",
             },
           ],
         },

sidebars.js

@@ -905,6 +905,7 @@ module.exports = {
         "reference/release-notes/850",
       ],
     },
+    "reference/contact",
     "reference/supported-environments",
     "reference/dependencies",
     "reference/camunda-help-center",

static/.htaccess

@@ -14,6 +14,9 @@ RewriteRule ^optimize/3.14.0/(.*)$ /optimize/$1 [R=302,L]
 # ----------------------
 # None here yet, but please place them here when you have them.
 
+# Move contact page
+RewriteRule ^contact/?$ /docs/reference/contact/ [R=301,L]
+
 # Remove Connector update guides entirely
 RewriteRule ^docs/components/connectors/custom-built-connectors/update-guide/(.*)$ /docs/components/connectors/custom-built-connectors/connector-sdk/ [R=301,L]
 

versioned_docs/version-8.2/components/best-practices/development/service-integration-patterns.md

@@ -120,7 +120,7 @@ You can leverage [message buffering](/docs/components/concepts/messages#message-
 
 Retries are not built-in, so if you need to model a loop to retry the initial service call if no response is received. And (at least in the current Zeebe version), there is no possibility to trigger error events for a receive task, which means you need to model error messages as response payload or separate message types — both are discussed later in this post.
 
-A final note for high-performance environments: These powerful messaging capabilities do not come for free and require some overhead within the engine. For pure request/response calls that return within milliseconds, none of the features are truly required. If you are looking to build a high-performance scenario, using service tasks instead of message correlation for request/response calls, you can tune your overall performance or throughput. However, as with everything performance related, the devil is in the detail, so [reach out to us](/contact) to discuss such a scenario in more depth.
+A final note for high-performance environments: These powerful messaging capabilities do not come for free and require some overhead within the engine. For pure request/response calls that return within milliseconds, none of the features are truly required. If you are looking to build a high-performance scenario, using service tasks instead of message correlation for request/response calls, you can tune your overall performance or throughput. However, as with everything performance related, the devil is in the detail, so [reach out to us](/reference/contact.md) to discuss such a scenario in more depth.
 
 **Summary And recommendations**
 

versioned_docs/version-8.2/components/concepts/data-retention.md

@@ -15,7 +15,7 @@ The following time-to-live settings are configured in SaaS for each application.
 - **Tasklist**: 30 days
 - **Zeebe**: 7 days
 
-If there are specific requirements for your use-case, [reach out to us](/contact/) to discuss your data retention needs under an Enterprise plan.
+If there are specific requirements for your use-case, [reach out to us](/reference/contact.md) to discuss your data retention needs under an Enterprise plan.
 
 ## Further information
 

versioned_docs/version-8.2/components/concepts/what-is-camunda-8.md

@@ -105,7 +105,7 @@ The platform and tools are usable in your environment right away, with full publ
 
 ## Next steps
 
-- To request information about Camunda 8 performance and benchmarking, see our [Contact](/contact/) page.
+- To request information about Camunda 8 performance and benchmarking, see our [Contact](/reference/contact.md) page.
 - [Introduction to Camunda 8](/guides/introduction-to-camunda-8.md)
 - [Create a Camunda 8 account](/guides/create-account.md)
 - [Migrate from Camunda 7 to Camunda 8](/guides/migrating-from-camunda-7/index.md)

versioned_docs/version-8.2/components/zeebe/zeebe-overview.md

@@ -20,12 +20,6 @@ With Zeebe you can:
 
 For documentation on deploying Zeebe as part of Camunda 8 Self-Managed, refer to the [deployment guide](../../self-managed/zeebe-deployment/zeebe-installation.md).
 
-## Enterprise support for Zeebe
-
-Paid support for Zeebe is available via either Camunda 8 Starter or Camunda 8 Enterprise. Customers can choose either plan based on their process automation requirements. Camunda 8 Enterprise customers also have the option of on-premises or private cloud deployment.
-
-Additionally, regardless of how you are working with Zeebe and Camunda 8, you can always find support through the [community](/contact/).
-
 ## Next steps
 
 - Get familiar with [technical concepts](technical-concepts/technical-concepts-overview.md).

versioned_docs/version-8.2/guides/migrating-from-camunda-7/index.md

@@ -53,4 +53,4 @@ As described earlier in this guide, migration is an ongoing topic and this guide
 - Discuss workload migrations (operations)
 - Eventual consistency
 
-[Reach out to us](/contact/) to discuss your specific migration use case.
+[Reach out to us](/reference/contact.md) to discuss your specific migration use case.

versioned_docs/version-8.2/reference/alpha-features.md

@@ -32,7 +32,7 @@ To learn more about using alpha features, see [enabling alpha features](/compone
 :::note
 
 - Alpha features can also be included in a minor version (stable) release.
-- Although there is no maintenance service, customers can still provide feedback through designated support channels, depending on their SLAs. These channels include filing issues in the respective [GitHub repositories](https://github.com/camunda) and submitting questions and suggestions by [contacting us](/contact).
+- Although there is no maintenance service, customers can still provide feedback through designated support channels, depending on their SLAs. These channels include filing issues in the respective [GitHub repositories](https://github.com/camunda) and submitting questions and suggestions by [contacting us](/reference/contact.md).
 
 :::