added note to deployment guides

Author: shahednasser

www/apps/docs/content/deployments/index.mdx

@@ -7,7 +7,22 @@ import { getCategoryItems } from '@site/src/utils/get-first-category-item';
 
 # Deployment Overview
 
-In this document, you’ll learn about the different ways you can deploy your Medusa project.
+In this document, you’ll learn about the different ways you can deploy your Medusa v1 project.
+
+<Note title="Deploy with Medusa Cloud">
+
+This guide is intended for Medusa v1 users. If you're a Medusa v2 user, consider using [Medusa Cloud](https://docs.medusajs.com/cloud). By using Medusa Cloud, you can avoid the complexities and challenges of self-hosting, while benefiting from automated deployment, scaling, and maintenance.
+
+With Medusa Cloud, you also maintain full customization control as you deploy your own modules and customizations directly from GitHub:
+
+1. Push to deploy.
+2. Multiple testing environments.
+3. Preview environments for new PRs.
+4. Test on production-like data.
+
+Refer to the [Cloud vs. Self-Hosting comparison guide](https://docs.medusajs.com/cloud/comparison) for more details.
+
+</Note>
 
 ## Overview
 

www/apps/docs/content/deployments/server/deploying-on-digital-ocean.md

@@ -5,7 +5,22 @@ addHowToData: true
 
 # Deploy Your Medusa Backend to DigitalOcean Apps
 
-In this document, you'll learn how to deploy your Medusa backend to a DigitalOcean App.
+In this document, you'll learn how to deploy your Medusa v1 backend to a DigitalOcean App.
+
+:::info[Deploy with Medusa Cloud]
+
+This guide is intended for Medusa v1 users. If you're a Medusa v2 user, consider using [Medusa Cloud](https://docs.medusajs.com/cloud). By using Medusa Cloud, you can avoid the complexities and challenges of self-hosting, while benefiting from automated deployment, scaling, and maintenance.
+
+With Medusa Cloud, you also maintain full customization control as you deploy your own modules and customizations directly from GitHub:
+
+1. Push to deploy.
+2. Multiple testing environments.
+3. Preview environments for new PRs.
+4. Test on production-like data.
+
+Refer to the [Cloud vs. Self-Hosting comparison guide](https://docs.medusajs.com/cloud/comparison) for more details.
+
+:::
 
 DigitalOcean is a reliable hosting provider that provides different ways to host websites and servers. One way to host a backend is using their DigitalOcean App Platform.
 

www/apps/docs/content/deployments/server/deploying-on-heroku.mdx

@@ -5,13 +5,22 @@ addHowToData: true
 
 # Deploy Your Medusa Backend on Heroku
 
-In this document, you'll learn how to deploy your Medusa backend on Heroku. Heroku is a PaaS (Platform as a Service) that allows you to easily deploy your applications in the cloud.
+In this document, you'll learn how to deploy your Medusa v1 backend on Heroku. Heroku is a PaaS (Platform as a Service) that allows you to easily deploy your applications in the cloud.
 
-Alternatively, you can use this button to deploy the Medusa backend to Heroku directly:
+<Note title="Deploy with Medusa Cloud">
 
-<a href="https://heroku.com/deploy?template=https://github.com/medusajs/medusa-starter-default/tree/feat/deploy-heroku" className="img-url">
-  <img src="https://www.herokucdn.com/deploy/button.svg" alt="Deploy to Heroku" className="no-zoom-img" />
-</a>
+This guide is intended for Medusa v1 users. If you're a Medusa v2 user, consider using [Medusa Cloud](https://docs.medusajs.com/cloud). By using Medusa Cloud, you can avoid the complexities and challenges of self-hosting, while benefiting from automated deployment, scaling, and maintenance.
+
+With Medusa Cloud, you also maintain full customization control as you deploy your own modules and customizations directly from GitHub:
+
+1. Push to deploy.
+2. Multiple testing environments.
+3. Preview environments for new PRs.
+4. Test on production-like data.
+
+Refer to the [Cloud vs. Self-Hosting comparison guide](https://docs.medusajs.com/cloud/comparison) for more details.
+
+</Note>
 
 ## Prerequisites
 

www/apps/docs/content/deployments/server/deploying-on-microtica.md

@@ -5,7 +5,22 @@ addHowToData: true
 
 # Deploy Your Medusa Backend on Microtica
 
-In this document, you'll learn how to deploy your Medusa backend on your AWS account with Microtica.
+In this document, you'll learn how to deploy your Medusa v1 backend on your AWS account with Microtica.
+
+:::info[Deploy with Medusa Cloud]
+
+This guide is intended for Medusa v1 users. If you're a Medusa v2 user, consider using [Medusa Cloud](https://docs.medusajs.com/cloud). By using Medusa Cloud, you can avoid the complexities and challenges of self-hosting, while benefiting from automated deployment, scaling, and maintenance.
+
+With Medusa Cloud, you also maintain full customization control as you deploy your own modules and customizations directly from GitHub:
+
+1. Push to deploy.
+2. Multiple testing environments.
+3. Preview environments for new PRs.
+4. Test on production-like data.
+
+Refer to the [Cloud vs. Self-Hosting comparison guide](https://docs.medusajs.com/cloud/comparison) for more details.
+
+:::
 
 :::note
 

www/apps/docs/content/deployments/server/deploying-on-railway.mdx

@@ -9,18 +9,26 @@ import MimeErrorTroubleshooting from "../../troubleshooting/mime-error.md"
 
 # Deploy Your Medusa Backend to Railway
 
-In this document, you’ll learn how to deploy your Medusa backend to Railway.
+In this document, you’ll learn how to deploy your Medusa v1 backend to Railway.
 
-## What is Railway
+<Note title="Deploy with Medusa Cloud">
 
-[Railway](https://railway.app/) is a hosting provider that you can use to deploy web applications and databases without having to worry about managing the full infrastructure.
+This guide is intended for Medusa v1 users. If you're a Medusa v2 user, consider using [Medusa Cloud](https://docs.medusajs.com/cloud). By using Medusa Cloud, you can avoid the complexities and challenges of self-hosting, while benefiting from automated deployment, scaling, and maintenance.
+
+With Medusa Cloud, you also maintain full customization control as you deploy your own modules and customizations directly from GitHub:
 
-Railway provides a free trial (no credit card required) that allows you to deploy your Medusa backend along with PostgreSQL and Redis databases. This is useful mainly for development and demo purposes.
+1. Push to deploy.
+2. Multiple testing environments.
+3. Preview environments for new PRs.
+4. Test on production-like data.
 
-<a 
-  href="https://railway.app/template/zC7eOq?referralCode=TW4Qi0" className="img-url no-zoom-img mb-2 inline-block">
-  <img src="https://railway.app/button.svg" alt="Deploy with Railway" className="no-zoom-img"/>
-</a>
+Refer to the [Cloud vs. Self-Hosting comparison guide](https://docs.medusajs.com/cloud/comparison) for more details.
+
+</Note>
+
+## What is Railway
+
+[Railway](https://railway.app/) is a hosting provider that you can use to deploy web applications and databases without having to worry about managing the full infrastructure.
 
 <Note type="check">
 

www/apps/docs/content/deployments/server/general-guide.md

@@ -5,7 +5,22 @@ addHowToData: true
 
 # General Deployment Guide for Medusa Backend
 
-In this guide, you’ll learn the general steps you need to take when deploying your Medusa backend. This is useful when the [platform-specific deployment guides](./index.mdx) do not include your selected hosting provider.
+In this guide, you’ll learn the general steps you need to take when deploying your Medusa v1 backend. This is useful when the [platform-specific deployment guides](./index.mdx) do not include your selected hosting provider.
+
+:::info[Deploy with Medusa Cloud]
+
+This guide is intended for Medusa v1 users. If you're a Medusa v2 user, consider using [Medusa Cloud](https://docs.medusajs.com/cloud). By using Medusa Cloud, you can avoid the complexities and challenges of self-hosting, while benefiting from automated deployment, scaling, and maintenance.
+
+With Medusa Cloud, you also maintain full customization control as you deploy your own modules and customizations directly from GitHub:
+
+1. Push to deploy.
+2. Multiple testing environments.
+3. Preview environments for new PRs.
+4. Test on production-like data.
+
+Refer to the [Cloud vs. Self-Hosting comparison guide](https://docs.medusajs.com/cloud/comparison) for more details.
+
+:::
 
 ## Prerequisites
 

www/apps/docs/content/deployments/server/index.mdx

@@ -9,4 +9,19 @@ import DocCardList from '@theme/DocCardList';
 
 Find in this page guides to deploy your Medusa backend on different platforms.
 
+<Note title="Deploy with Medusa Cloud">
+
+The following guides are intended for Medusa v1 users. If you're a Medusa v2 user, consider using [Medusa Cloud](https://docs.medusajs.com/cloud). By using Medusa Cloud, you can avoid the complexities and challenges of self-hosting, while benefiting from automated deployment, scaling, and maintenance.
+
+With Medusa Cloud, you also maintain full customization control as you deploy your own modules and customizations directly from GitHub:
+
+1. Push to deploy.
+2. Multiple testing environments.
+3. Preview environments for new PRs.
+4. Test on production-like data.
+
+Refer to the [Cloud vs. Self-Hosting comparison guide](https://docs.medusajs.com/cloud/comparison) for more details.
+
+</Note>
+
 <DocCardList />

www/apps/docs/src/theme/Admonition/Layout/index.tsx

@@ -47,7 +47,7 @@ function AdmonitionContent({
       )}
     >
       {title && (
-        <span className="txt-compact-medium-plus block mb-0.125">
+        <span className="text-compact-medium-plus block mb-docs_0.125 text-medusa-fg-base">
           {transformAdmonitionTitle(title)}
         </span>
       )}