Fix: Update Template

vr-varad · vr-varad · commit 40988f4447cc · 2025-07-16T03:59:32.000+05:30
Signed-off-by: vr-varad &lt;varadgupta21@gmail.com&gt;
diff --git a/Makefile b/Makefile
@@ -12,7 +12,7 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
-include .github/build/Makefile.show-help.mk
+#include .github/build/Makefile.show-help.mk
 
 ## Install docs.layer5.io dependencies on your local machine.
 ## See https://gohugo.io/categories/installation
diff --git a/content/learning-paths/your-org-uuid/example-learning-path/course-1/content/container-benefits.md b/content/learning-paths/your-org-uuid/example-learning-path/course-1/content/container-benefits.md
@@ -13,19 +13,15 @@ weight: 3
 ![image]({{< usestatic "image-1.png" >}})
 
 
-{{< chapterstyle >}}
-
-
-
-<h2 class="chapter-sub-heading">Container Benefits</h2>
+### **Container Benefits**
 
 1. **dev and ops separation of concerns** create application container images at build/release time rather than deployment time, thereby decoupling applications from infrastructure
 
-{{< image src="/images/learning-path/intro-kubernetes/containers/c1_l3_1.png" width="100%" align="center" alt="DevOps" >}}
+![image]({{< usestatic "image-1.png" >}})
 
 2. **continuous development, integration, and deployment** provides for reliable and frequent container image build and deployment with quick and efficient rollbacks – due to image immutability
 
-{{< image src="/images/learning-path/intro-kubernetes/containers/c1_l3_2.png" width="100%" align="center" alt="Mutable vs Immutable" >}}
+![image]({{< usestatic "image-1.png" >}})
 
 3. **environmental consistency across dev, test, and prod** runs the same on a laptop as it does on an on-premises server, virtualized server, and in the cloud
 
@@ -37,10 +33,6 @@ weight: 3
 
 7. **agile application creation and deployment** increased ease and efficiency of container image creation compared to VM image use
 
-8. <strong>application-centric management</strong> raises abstraction level:
-   <ul>
-     <li>from running applications on an OS using virtual hardware</li>
-     <li>to running applications on an OS using logical resources</li>
-   </ul>
-
-{{< /chapterstyle >}}
+8. **application-centric management** raises abstraction level:
+     - from running applications on an OS using virtual hardware
+     - to running applications on an OS using logical resources
diff --git a/content/learning-paths/your-org-uuid/example-learning-path/course-1/content/experience-we-want-to-change.md b/content/learning-paths/your-org-uuid/example-learning-path/course-1/content/experience-we-want-to-change.md
@@ -7,32 +7,30 @@ lectures: 4
 title: "Experiences we want to change!"
 weight: 1
 ---
-{{< chapterstyle >}}
 
-<h2 class="chapter-sub-heading">Why Containers?</h2>
+### **Why Containers?**
 
 Many people have a complex job building, testing, and running systems based on old concepts and technology in today's IT — the results you can see below (Experiences we want to change!). Modern ways to build, test, and run IT systems are not adopted as broadly as possible. Hence, a lot of pain is still out there that we could ease by changing IT processes and utilizing the new ways.
 
-{{< image src="/images/learning-path/intro-kubernetes/containers/c1_l1_1.png" width="100%" align="center" alt="Why Container?" >}}
+![image]({{< usestatic "image-1.png" >}})
 
-<h2 class="chapter-sub-heading">Experiences we want to change!</h2>
+### **Experiences we want to change!**
 
-<h3 class="chapter-sub-heading">BUILD - Life of a Developer</h3>
+#### **BUILD - Life of a Developer**
 
 Here you see a developer who brought her code into production, only to find out that it didn't run like on her laptop ...
 
-{{< image src="/images/learning-path/intro-kubernetes/containers/c1_l1_2.png" width="50%" align="center" alt="" >}}
+![image]({{< usestatic "image-1.png" >}})
 
-<h3 class="chapter-sub-heading">TEST - Life of System Architects</h3>
+#### **TEST - Life of System Architects**
 
 Here you can see system architects who mistakenly made a load test on a production server ...
 
-{{< image src="/images/learning-path/intro-kubernetes/containers/c1_l1_3.png" width="50%" align="center" alt="" >}}
+![image]({{< usestatic "image-1.png" >}})
 
-<h3 class="chapter-sub-heading">RUN - Life of a System Administrator</h3>
+#### **RUN - Life of a System Administrator**
 
 Here you can see a system administrator who was woken at 3 am to restart a process ...
 
-{{< image src="/images/learning-path/intro-kubernetes/containers/c1_l1_4.png" width="50%" align="center" alt="" >}}
+![image]({{< usestatic "image-1.png" >}})
 
-{{< /chapterstyle >}}
diff --git a/content/learning-paths/your-org-uuid/example-learning-path/course-1/content/history_of_application_deployment.md b/content/learning-paths/your-org-uuid/example-learning-path/course-1/content/history_of_application_deployment.md
@@ -7,22 +7,19 @@ lectures: 4
 title: "History of Application Deployments"
 weight: 4
 ---
-{{< chapterstyle >}}
 
-<h2 class="chapter-sub-heading">History of Application Deployments</h2>
+### **History of Application Deployments**
 
-{{< image src="/images/learning-path/intro-kubernetes/containers/c1_l4_1.png" width="100%" align="center" alt="Application Deployments" >}}
+![image]({{< usestatic "image-1.png" >}})
 
-<h2 class="chapter-sub-heading">Traditional Deployment</h2>
+#### **Traditional Deployment**
 
 Early on, organizations ran applications on physical servers. There was no way to define resource boundaries for applications in a physical server, and this caused resource allocation issues. For example, if multiple applications run on a physical server, there can be instances where one application would take up most of the resources, and as a result, the other applications would underperform. A solution for this would be to run each application on a different physical server. But this did not scale as resources were underutilized, and it was expensive for organizations to maintain many physical servers.
 
-<h2 class="chapter-sub-heading">Virtualized Deployment</h2>
+#### **Virtualized Deployment**
 
 As a solution, virtualization was introduced. It allows you to run multiple Virtual Machines (VMs) on a single physical server's CPU. Virtualization allows applications to be isolated between VMs and provides a level of security as the information of one application cannot be freely accessed by another application. Virtualization allows better utilization of resources in a physical server and allows better scalability because an application can be added or updated easily, reduces hardware costs, and much more. With virtualization, you can present a set of physical resources as a cluster of disposable virtual machines. Each VM is a full machine running all the components, including its own operating system, on top of the virtualized hardware.
 
-<h2 class="chapter-sub-heading">Container Deployment</h2>
+#### **Container Deployment**
 
 Containers are similar to VMs, but they have relaxed isolation properties to share the Operating System (OS) among the applications. Therefore, containers are considered lightweight. Similar to a VM, a container has its own file system, share of CPU, memory, process space, and more. As they are decoupled from the underlying infrastructure, they are portable across clouds and OS distributions.
-
-{{< /chapterstyle >}}
diff --git a/content/learning-paths/your-org-uuid/example-learning-path/course-1/content/new-ideas-and-concepts.md b/content/learning-paths/your-org-uuid/example-learning-path/course-1/content/new-ideas-and-concepts.md
@@ -7,9 +7,8 @@ lectures: 4
 title: "New Ideas & Concepts"
 weight: 2
 ---
-{{< chapterstyle >}}
 
-<h2 class="chapter-sub-heading">New Ideas & Concepts</h2>
+### **New Ideas & Concepts**
 
 As often in IT, great "new" ideas and concepts are recycled or borrowed from others. So it happened that the shipping industry was a big inspiration for optimizing IT infrastructure operations more than two decades ago.
 
@@ -19,20 +18,16 @@ Replication of success is always desirable and sparked a new way of operating IT
 
 Container Technology in the shipping industry Instead of thinking up a separate way of shipping for each product, placing the goods in steel containers designed for pickup by the crane on the dock and fit into the ship is a more efficient way to do transport at scale.
 
-{{< image src="/images/learning-path/intro-kubernetes/containers/c1_l2_1.png" width="100%" align="center" alt="A Container Ship" >}}
+![image]({{< usestatic "image-1.png" >}})
 
 In streamlining the processes and the loading of the goods in standardized containers, the goods can be moved as one unit in a space-saving and cost-effective manner.
 
 Container Technology in the IT industry Computer container technology in the IT industry addresses similar challenges to steel containers in the shipping industry:
 
-<ul>
-  <li>increase compatibility</li>
-  <li>reduce dependencies</li>
-  <li>develop, deploy and operate easier</li>
-</ul>
+- increase compatibility
+- reduce dependencies
+- develop, deploy and operate easier
 
-{{< image src="/images/learning-path/intro-kubernetes/containers/c1_l2_2.png" width="50%" align="center" alt="Docker" >}}
+![image]({{< usestatic "image-1.png" >}})
 
 In streamlining the processes and the apps' packaging in containers, deploying and running apps as one unit become a more performant and resource-effective process.
-
-{{< /chapterstyle >}}
diff --git a/content/learning-paths/your-org-uuid/example-learning-path/course-2/content/packaging-pricing.md b/content/learning-paths/your-org-uuid/example-learning-path/course-2/content/packaging-pricing.md
@@ -7,10 +7,7 @@ lectures: 2
 title: "Packaging & Pricing"
 weight: 2
 ---
-{{< chapterstyle >}}
 
-<h2 class="chapter-sub-heading">Packaging & Pricing</h2>
+### **Packaging & Pricing**
 
-{{< image src="/images/learning-path/intro-kubernetes/exoscale-sks/c6_l2_1.png" width="100%" align="center" alt="Exoscale SKS - Packaging & Pricing" >}}
-
-{{< /chapterstyle >}}
+![image]({{< usestatic "image-1.png" >}})
diff --git a/content/learning-paths/your-org-uuid/example-learning-path/course-2/content/scalable-kubernetes-services.md b/content/learning-paths/your-org-uuid/example-learning-path/course-2/content/scalable-kubernetes-services.md
@@ -7,15 +7,14 @@ lectures: 2
 title: "Scalable Kubernetes Service"
 weight: 1
 ---
-{{< chapterstyle >}}
 
-<h2 class="chapter-sub-heading">Scalable, On-demand Kubernetes Cluster</h2>
+### **Scalable, On-demand Kubernetes Cluster**
 
 Start with a privacy-minded public cloud to host from single applications to complex architectures. Deploy a production-ready cluster in 90 seconds and manage it with a simple web portal, CLI, API or your choice of tools (Terraform).
 
-{{< image src="/images/learning-path/intro-kubernetes/exoscale-sks/c6_l1_1.png" width="30%" align="center" alt="" >}}
+![image]({{< usestatic "image-1.png" >}})
 
-<h2 class="chapter-sub-heading" >SKS Features</h2>
+### **SKS Features**
 
 **Access to all compute instance types**
 
@@ -41,6 +40,13 @@ With a free STARTER version and an affordable PRO plan, SKS provides straightfor
 
 Deploy your cluster where you need to, in the region that suits your latency, privacy or redundancy strategy.
 
-{{< image src="/images/learning-path/intro-kubernetes/exoscale-sks/c6_l2_1.png" width="100%" align="center" alt="" >}}
+![image]({{< usestatic "image-1.png" >}})
 
-{{< /chapterstyle >}}
+
+{{< card 
+title="Video: Example">}}
+<video width="100%" height="100%" controls>
+    <source src="https://exmaple.mp4" type="video/mp4">
+    Your browser does not support the video tag.
+</video>
+{{< /card >}}
diff --git a/static/your-org-uuid/image-1.png b/static/your-org-uuid/image-1.png
