add placeholder migration article

Author: jesp209i

umbraco-cloud/set-up/project-settings/umbraco-cicd/Migrate.md

@@ -0,0 +1,19 @@
+# Migrate from V1 to V2
+
+todo todo todo
+
+## What has changed?
+We wanted to improve on the original flow based on all the feedback received from users of the feature.
+Here are some of the highlights:
+- New endpoints
+- Target environment must be supplied on get-diff and deploy steps
+- More options when deploying
+- Rewritten scripts to target new endpoints
+
+## Move directly from V1 to V2 scripts
+This assumes you have only changes the parameters mentioned in the original guide
+
+# azdevops
+
+
+# github

umbraco-cloud/set-up/project-settings/umbraco-cicd/UmbracoCloudApi.md

@@ -11,7 +11,7 @@ These are the most important differences between the V1 and V2 endpoints:
 - More options are available when deploying.
 - Simplified api call flow: Uploading an artifact is decoupled from the actual deployment.
 
-[Do you want to migrate from V1 to V2 endpoints?](#todo)
+[Do you want to migrate from V1 to V2 endpoints?](./Migrate.md)
 
 ## Getting started
 

umbraco-cloud/set-up/project-settings/umbraco-cicd/samplecicdpipeline/V1-azure-devops.md

@@ -1,5 +1,4 @@
 ---
-hidden: true
 description: >-
   This section provides a step-by-step guide to setting up a CI/CD pipeline in
   Azure DevOps using the provided sample Bash or Powershell scripts.

umbraco-cloud/set-up/project-settings/umbraco-cicd/samplecicdpipeline/V1-github-actions.md

@@ -1,5 +1,4 @@
 ---
-hidden: true
 description: >-
   This section provides a step-by-step guide to setting up a CI/CD pipeline in
   GitHub Actions using the provided sample Bash or Powershell scripts.