Add borders to graphics

labs/shipped-cicd/1.md

@@ -9,37 +9,40 @@ Continuous Deployment (CD) is a practice that closely related to CI. CD deploys
 ## Configure Your Project
 
 
-1. Log in to <a href="https://ciscoshipped.io">https://ciscoshipped.io</a>.    
+1. Log in to <a href="https://ciscoshipped.io">Shipped UI</a>.    
 
-2.  Select a project from **Your Projects** drop-down list. Or create new project.
+2.  Select a project from **Your Projects** drop-down list, or create a new one.
 
-![](posts/files/shipped-cicd/assets/project-select.png)
+    ![](posts/files/shipped-cicd/assets/project-select.png)
 
 
-3. Add a new Service (Golang for Eg.), you can select from existing buildpacks.
+3. Add a new service (Golang for example).
 
-![](posts/files/shipped-cicd/assets/2.PNG)
+    ![](posts/files/shipped-cicd/assets/2.PNG)
 
-4. Provide a Service name for this newly created service.
+4. Enter a name for this service.
 
-![](posts/files/shipped-cicd/assets/3.PNG)
+    ![](posts/files/shipped-cicd/assets/3.PNG)
 
-5. Click Save Project, this will Create a new git repo with the same service name you have mentioned above, and also make neccesory changes to this repo to be integrated with shipped.
+5. Click **Save Project**.  
+    A new git repo is created with the service name you created.
 
-![](posts/files/shipped-cicd/assets/4.PNG)
+    ![](posts/files/shipped-cicd/assets/4.PNG)
 
-6. Verify First build- Once you save project, Shipped makes some changes to your repo to be integrated with shipped.this process also trigger some builds for such commits.
-
-![](posts/files/shipped-cicd/assets/5.PNG)
+6. Verify the build.   
+    Shipped makes some changes to your repo to be integrated with Shipped. This process also triggers some builds for such commits.
 
+    ![](posts/files/shipped-cicd/assets/5.PNG)
 
-7.  Click the **Deploy** tab and create new environment.
+7.  Click the **Deploy** tab then click **New Environment**.
+
+    ![](posts/files/shipped-cicd/assets/Environment-add.png)    
 
-![](posts/files/shipped-cicd/assets/Environment-add.png)    
+8.  Enter a name for the environment, click **Save**. 
 
-8.  Deploy your application.
+8.  Click **Deploy Build**.
 
-![](posts/files/shipped-cicd/assets/12.PNG)    
+    ![](posts/files/shipped-cicd/assets/12.PNG)    
 
 
 

labs/shipped-cicd/2.md

@@ -1,24 +1,25 @@
-# Shipped - CICD
 
-## Making new changes to Git repo and Redeploy
+## Make Changes to Git Repo and Redeploy
 
-1 Verify Git Project- Now you should be able to see fully integrated git repo with all neccesory changes done by shipped.
+1. Verify your project, which is fully integrated with all additional files.
 
-![](posts/files/shipped-cicd/assets/6.PNG)
+    ![](posts/files/shipped-cicd/assets/6.PNG)
 
-2 Make Some Changes in your git Project to see if shipped triggers a new build for your commit.
 
-![](posts/files/shipped-cicd/assets/7.PNG)
+1. Make some changes in your git project to verify that Shipped triggers a new build.
 
-3 Commit changes- once you commit your change associated webhook will tell shipped to trigger a build for your commits. Each Commit will trigger a seperate build.
+    ![](posts/files/shipped-cicd/assets/7.PNG)
 
-![](posts/files/shipped-cicd/assets/8.PNG)
+1. Commit changes.  
+    When you commit changes, an associated webhook tells Shipped to trigger a build. Each commit triggers a seperate build.
 
-4 Verify Build progress for latest commit
+     ![](posts/files/shipped-cicd/assets/8.PNG)
 
-![](posts/files/shipped-cicd/assets/9.PNG)
+1. Verify the build progress for the latest commit.
 
-5 Deploy latest build.
+    ![](posts/files/shipped-cicd/assets/9.PNG)
 
-![](posts/files/shipped-cicd/assets/10.PNG)
+1. Deploy latest build.
+
+    ![](posts/files/shipped-cicd/assets/10.PNG)
 

labs/shipped-cicd/3.md

@@ -1,24 +1,48 @@
-# Shipped - CICD
 
-## Environment Configurations
+## Configure Environment Settings
 
-1. Click on **Deploy** tab. and click on Settings
+1. Click the **Deploy** tab.  
 
-![](posts/files/shipped-cicd/assets/13.PNG)
+    ![](posts/files/shipped-cicd/assets/Environment-settings.png)
 
-2. Change containers to 3 and click on save button.
+4.  Select your environment, then click **Settings**.
 
-![](posts/files/shipped-cicd/assets/14.PNG)
+1. Click **Environment Settings** to display the settings. 
 
-3. Once done with Enviroment specific setting, We need to redeploy build.
+    ![](posts/files/shipped-cicd/assets/Environment-settings-CI.png)
 
-Deploying a build to an environment means that your project will be deployed to the environment you select. It replaces any previous deployment of the build to that environment. 
+## Enable Auto Deploy
 
-![](posts/files/shipped-cicd/assets/12.PNG)
+1. Click the **Auto Deploy**, then click **Back to Environments**. 
+
+1. Click **Deploy Build**. 
 
-4 When the project deployment is completed, we can see URL in green color link like "CISCO EU" for    the build, and progress bar also disappears.
 
-![](posts/files/shipped-cicd/assets/16.PNG)
+## Add a New Deploy Target
+
+
+1. Click **Settings** on the environment page. 
+
+    ![](posts/files/shipped-cicd/assets/Environment-target.png)
+
+1. Click **+ New Target**, then click **+ Add New Target**. 
+
+    ![](posts/files/shipped-cicd/assets/Environment-target-marathon.png)
+
+1. Click **Add Deploy Target**, and select **Marathon**. 
+
+    ![](posts/files/shipped-cicd/assets/Deployed-target.png)
+
+1. Enter information in the following fields:
+ - **Name** - The name of your target. 
+ - **URL** - The URL of your target and must be in this format, for example, https://mycorp-control-01.mycorp.shipped.cisco.com:8080
+ - **URL Template** - The template must be in this format, for example,    
+    http://%smycorp.shipped.cisco.com
+
+        ![](posts/files/shipped-cicd/assets/Environment-add-deploy-target.png)
+
+1. Optionally, click the check box next to **Enable HTTP Authentication**, then enter the user name and password. 
+
+1. Click **Save**.
+
 
-<br/>
-Wow, You have successfully built and deployed your project with custom environment settings.