Merge pull request #6557 from layer5io/leecalcote/service-mesh/be-gone

Refactor README and blog content for clarity and consistency:

Author: leecalcote

README.md

@@ -59,17 +59,6 @@
 <br />
 
 
-<p style="clear:both;">
-<h2><a href="https://layer5.io/landscape">Service Mesh Landscape</a></h2>
-<a href="https://layer5.io/landscape"><img src=".github/assets/images/buttons/landscape.webp"  
-style="float:left;margin:10px;" width="125px"
-alt="Service Mesh Landscape Ecosystem" align="left"/></a>
-The <a href="https://layer5.io/landscape">Service Mesh Landscape</a> is a comprehensive collection of prominent service mesh projects and offerings laid out in contrast to one another.
-<br /><br /><br />
-</p>
-<br />
-
-
 <p style="clear:both;">
 <h2><a href="https://layer5.io/projects/cloud-native-performance">Cloud Native Performance</a></h2>
 <a href="https://layer5.io/projects/cloud-native-performance">
@@ -91,7 +80,7 @@ The <a href="https://layer5.io/projects/cloud-native-performance">Cloud Native P
 style="float:left;margin:10px;" width="125px"
 alt="Image Hub" align="left" /></a>
 <a href="https://layer5.io/projects/image-hub">Image Hub</a> is a demo application which runs on <a href="https://docs.meshery.io/service-meshes/adapters/consul">Consul</a> and facilitates exploring WebAssembly modules used as Envoy Filters.
-Image Hub supports Envoy-based data planes. It is compatible with and can be deployed on Istio and Consul service meshes.
+Image Hub supports Envoy-based data planes. It is compatible with and can be deployed on Istio and Consul.
 <br /><br /><br />
 </p>
 <br />
@@ -121,18 +110,6 @@ alt="Learn Layer5" align="left" />
 </p>
 <br />
 
-
-<!-- <p style="clear:both;">
-<h2><a href="https://layer5.io/smi">Service Mesh Interface Conformance </a></h2>
-<a href="https://layer5.io/smi"><img src=".github/assets/images/smi-conformance/checklist.svg"
-style="float:left;margin:10px;" width="125px"
-alt="Service Mesh Interface Conformance" align="left" /></a>
-<a href="https://layer5.io/smi">SMI Conformance</a> includes all service mesh projects participating in the Service Mesh Interface specification. It is an easy-to-use, service mesh and SMI-specific tool to give service mesh projects and users a suite of repeatable conformance tests.
-<br /><br /><br />
-</p>
-<br />
- -->
-
 <p style="clear:both;">
 <h2><a href="https://layer5.io/projects/nighthawk">Nighthawk</a></h2>
 <a href="https://getnighthawk.dev/">

content-learn/mastering-kubernetes-for-engineers/ambassador-edge-stack-api-gateway-with-meshery/index.mdx

@@ -1,7 +1,7 @@
 ---
 docType: "Course"
 title: "Course"
-description: "This course will guide you through the process of deploying and visualizing Edge Stack components with Meshery. You will learn how to install and configure the Ambassador API Gateway and explore its integration with Meshery. Additionally, you will gain hands-on experience with two popular service meshes, Istio and Linkerd. By the end of this course, you will have a solid understanding of Edge Stack deployment and be able to leverage Meshery for managing your API gateway and service mesh configurations."
+description: "This course will guide you through the process of deploying and visualizing Edge Stack components with Meshery. You will learn how to install and configure the Ambassador API Gateway and explore its integration with Meshery. Additionally, you will gain hands-on experience with Istio and Linkerd. By the end of this course, you will have a solid understanding of Edge Stack deployment and be able to leverage Meshery for managing your API gateway and infrastructure configurations."
 videos: 0
 lectures: 4
 courseTitle: "Ambassador Edge Stack API Gateway with Meshery"

src/collections/blog/2019/2019-12-04-layer5-landscape-spectrums-revisited/index.mdx

@@ -47,7 +47,7 @@ Within [Issue #211](https://github.com/layer5io/layer5/issues/211), Layer5 lead
 
 #### 2\. A modular design
 
-The designs I am implementing are meant to be used to present opinionated information. As I am not nearly knowledgeable to form opinionated comparisons between service meshes and related technologies, I have instead made my goal to make it as easy as possible for other Layer5 contributors to utilize the graphics ("\[comparative\] spectrums") that I am designing. Doing so would require encapsulating (templating) the spectrums I design (new and old), within their own HTML files, and providing a means to easily invoke (and customize) instances of those templates into the Landscape page.
+The designs I am implementing are meant to be used to present opinionated information. As I am not nearly knowledgeable to form opinionated comparisons between DevOps tools and related technologies, I have instead made my goal to make it as easy as possible for other Layer5 contributors to utilize the graphics ("\[comparative\] spectrums") that I am designing. Doing so would require encapsulating (templating) the spectrums I design (new and old), within their own HTML files, and providing a means to easily invoke (and customize) instances of those templates into the Landscape page.
 
 #### 3\. Documentation
 

src/collections/blog/2020/2020-07-03-my-meshy-journey/index.mdx

@@ -21,24 +21,25 @@ import IshitaProfile from "./ishita-kumar-profile.webp";
 As a graduate student at the Indiana University Bloomington, studying for my Masters in Computer Science, little did I consider that my thesis project would lead me on this amazing journey to becoming an open source contributor.
 
 My adventure with Layer5 has been a highly informative and invigorating experience, from coming aboard as a Meshery user to becoming an open source contributor. My initial interest in Layer5 was sparked when, for a project in my Masters course, I was required to build a microservice architecture and develop a service layer on top of it.
-A basic Google search led me to a plethora of resources, which in turn led me to understand how different service meshes could be compared. Comparison and selection of a service mesh was my first step to deploying one on my VM cluster. Amidst the varied resources available to me, stumbling onto Layer5 and Meshery was a happy boon.
+A basic Google search led me to a plethora of resources, which in turn led me to understand how different DevOps technologies could be compared. Comparison and selection of a cluster was my first step to deploying one on my VM cluster. Amidst the varied resources available to me, stumbling onto Layer5 and Meshery was a happy boon.
 
 ## Why Meshery?
 
 From the beginning, Meshery proved to be an intuitive and easy-to-use application. Among other benefits, it could be implemented into my project with ease which was also a major contributing factor behind my choice of taking advantage of its features for my project thesis.
-There are tons of resources online that compare different service meshes for your deployment however meshery was the only project that actually offered a practical way of comparing service meshes. In just a few easy steps, I could download and deploy  Meshery into my VM instance and compare the performance of my microservice application running atop two different service meshes:  Istio and Linkerd, thereby gathering various statistics on how they worked on my application.
+
+There are tons of resources online that compare different DevOps tools for your deployment, however, Meshery was the only project that actually offered a practical way of comparing your Kubernetes clusters. In just a few easy steps, I could download and deploy  Meshery into my VM instance and compare the performance of my microservice application running atop two different infrastructure configurations. It gathered various statistics on how they worked on my application.
 
 What really got my hooked though was Meshery's intuitive UI and the amazing open platform support, which made me strive to rise above and beyond my project goals, to truly understand and value the underlying idea.
 
 ## Insights While Meshing Around
 
-While using Meshery to deploy both Istio and Linkerd, I came to the understanding that while Meshery uses common methods for interfacing with and managing service meshes, that Meshery is also capable of exposing service mesh-specific features. This became apparent by how robust Meshery’s adapter for Istio is, which includes the ability to analyze and validate my deployment’s configuration against best practices. Each adapter includes a set of sample applications that makes it convenient to explore the functionality of different meshes, using the same application across them.
+While using Meshery to deploy both Istio and Linkerd, I came to the understanding that while Meshery uses common methods for interfacing with and managing cloud services, that Meshery is also capable of fully configuring all my infrastructure. This became apparent by how robust Meshery’s adapter for Istio is, which includes the ability to analyze and validate my deployment’s configuration against best practices. Each adapter includes a set of sample applications that makes it convenient to explore the functionality of different meshes, using the same application across them.
 
-The behavior that was of keen interest to me, however, was that of my custom, microservices. When deploying my microservices application, Meshery helped me understand how different service meshes were interacting with my software application.
+The behavior that was of keen interest to me, however, was that of my custom, microservices. When deploying my microservices application, Meshery helped me understand how different infrastructure was interacting with my software application.
 
-I learned that in addition to the easy integration of Meshery in my application, it also provides one of the best platforms out there to manage service meshes and gives you a fair assessment of your deployment, which can otherwise prove to be a daunting task.
+I learned that in addition to the easy integration of Meshery in my application, it also provides one of the best platforms out there to manage modern infrastructure configuration and gives you a fair assessment of your deployment, which can otherwise prove to be a daunting task.
 
-While presenting my findings to my class and professor, they were able to gauge the brilliancy each service mesh would bring into the microservice application.
+While presenting my findings to my class and professor, they were able to gauge the value that each piece of tech would bring into the microservice application.
 
 ## Shout out to the Community
 

src/collections/blog/2020/2020-07-16-communitybridge-2020-teaching-service-meshes-to-be-compliant/index.mdx

@@ -48,7 +48,7 @@ Meshery is the multi-service mesh management plane, offering lifecycle, configur
 
 
 We had found our solution. By leveraging the features provided in Meshery, we would be able to focus on the conformance validation and testing instead of sweating over the complexity in deployments. We can also use the performance management infrastructure to manage the conformance tests and their results. And so,  the tool will be developed as an integral part of Meshery to aid and abate SMI conformance woes.
-We are now enhancing Meshery to automate the process of verifying conformance against a standard set of tests against a sample workload designed specifically for SMI conformance testing. By the time we’re through, this capability of Meshery will allow each service mesh project to validate its conformance to each version of the SMI specifications and will provide a detailed report.
+We are now enhancing Meshery to automate the process of verifying conformance against a standard set of tests against a sample workload designed specifically for SMI conformance testing. By the time we’re through, this capability of Meshery will allow each project to validate its conformance to each version of the SMI specifications and will provide a detailed report.
 
 <h4> My Projects </h4>
 

src/collections/blog/2020/2020-07-16-growing-as-an-open-source-contributor-with-layer5/index.mdx

@@ -23,18 +23,19 @@ It all started 9 months ago when I stumbled across the following LinkedIn post,
 
 <img src={pic3} alt="book"/>
 
-This led me to a long-winding conversation with Subham Kumar Rai and Anand Kumar Singh about Layer5 and how amazing an opportunity it would be to be a part of this emerging community. I did some research on service meshes and made my way to the Layer5 Github repo. From there, it was a swift journey to the Layer5 Slack Channel where I truly understood what Subham had meant about the warm welcome. I was amazed by how helpful and willing the entire community was. Armed with the resources I needed, I delved into the projects and churned out a few PRs and I was hooked. I dove aggressively into the projects and handled any curve balls with the help of my mentors. My participation in the Layer5 community drove me to a well earned obsession with open source projects which led me to make my own contributions in the FOSSASIA and GATSBY projects and take part in many open-source contests such as Hacktoberfest, DevopsCember, Kharagpur Winter Of Code (KWOC), NJACK Winter Of Code (NWOC), Girlscript Summer Of Code (GSSOC).
+This led me to a long-winding conversation with Subham Kumar Rai and Anand Kumar Singh about Layer5 and how amazing an opportunity it would be to be a part of this emerging community. I did some research on Kubernetes and made my way to the Layer5 Github repo. From there, it was a swift journey to the Layer5 Slack Channel where I truly understood what Subham had meant about the warm welcome. I was amazed by how helpful and willing the entire community was. Armed with the resources I needed, I delved into the projects and churned out a few PRs and I was hooked. I dove aggressively into the projects and handled any curve balls with the help of my mentors. My participation in the Layer5 community drove me to a well earned obsession with open source projects which led me to make my own contributions in the FOSSASIA and GATSBY projects and take part in many open-source contests such as Hacktoberfest, DevopsCember, Kharagpur Winter Of Code (KWOC), NJACK Winter Of Code (NWOC), Girlscript Summer Of Code (GSSOC).
 
 <img src={pic4} alt="github-profile"/>
 
 #### What is Meshery?
 
-Meshery is a multi-service mesh management plane that offers lifecycle, configuration, and performance management of service meshes and applications running on top of those meshes.<br/>
+Meshery is a multi-platform management that offers lifecycle, configuration, and performance management of Kubernetes and cloud platforms and applications.<br/>
 
 <img src={pic1} alt="meshry"/>
 
-Meshery uses a common service mesh performance specification to describe and capture performance benchmarks and results. The spec contains general information about the performance test (e.g. start/end times), service mesh and proxy build numbers, Kubernetes cluster details (nodes, type of nodes, memory information), and the actual results. One of the ideas behind Meshery is to be a vendor and project-neutral tool that can benchmark the performance of different service meshes. <br/>
-It is a one stop for all your service meshing needs. Service meshes are still a novel concept for both, developers and users. Meshery steps in to bridge this gap and allows you to have a better understanding of what a service mesh can provide by helping you judge service mesh for your personal and professional needs. Meshery accomplishes this by providing you a thorough analysis of the options available so that you can make an informed choice.<br/>
+As a self-service engineering platform, Meshery enables collaborative design and operation of cloud and cloud native infrastructure.
+ <br/>
+Meshery seamlessly integrates with every CNCF project, your existing tools, multiple Clouds and Kubernetes clusters.<br/>
 
 <img className="align-right" src={pic2} alt="Lee Calcote" />
 

src/collections/blog/2020/2020-08-04-how-i-schooled-my-seniors/feature-image.svg

@@ -26,9 +26,9 @@ I pitched my idea to [Lee Calcote](https://layer5.io/community/members/lee-calco
 <center>
 <iframe src="https://docs.google.com/presentation/d/e/2PACX-1vQNpnp_SIkYNMe1rx-Cw_armxHRmQvkcp8d3BVML6XEhsSgy7k0w9xDKrGGs4EPew/embed?start=true&loop=true&delayms=3000" loading="lazy" frameborder="0" width="100%" height="300" allowfullscreen={true} mozallowfullscreen="true" webkitallowfullscreen="true"></iframe></center>
 
-When the day arrived to present the concepts of service meshes, Meshery, and other cloud native initiatives to my team, I held a Google Meet with a full attendance. I started the session with a reader’s digest version of microservices and service meshes to set the stage for any newcomers to the world of cloud native, I went on to elaborate on Layer5 ‘s contributions to the CNCF landscape and the SMI project. This was followed by an in-depth discussion on data planes, control planes, and management planes. I spoke at-length about Meshery’s functionality including, its features for facilitating the benchmarking, interoperability and standardization of service meshes. I wrapped up the session with some insider tips that I have learned in my months as an open source contributor in the Layer5 community. In the stream of feedback received from my colleagues, the session seems to have been a success.
+When the day arrived to present the concepts of cloud native infrastructure, Meshery, and other cloud native initiatives to my team, I held a Google Meet with a full attendance. I started the session with a reader’s digest version of microservices and cloud native infrastructure to set the stage for any newcomers to the world of cloud native, I went on to elaborate on Layer5 ‘s contributions to the CNCF landscape and the SMI project. This was followed by an in-depth discussion on data planes, control planes, and management planes. I spoke at-length about Meshery’s functionality including, its features for facilitating the benchmarking, interoperability and standardization of cloud native infrastructure. I wrapped up the session with some insider tips that I have learned in my months as an open source contributor in the Layer5 community. In the stream of feedback received from my colleagues, the session seems to have been a success.
 
-This whole experience has been an amazing journey for me. From being a complete noob to utilizing my expertise in the service mesh domain to landing an actual job, the experience has been a maze of ups and downs. But, I feel like I have finally arrived and arrived with a pot of gold. I’m eternally grateful to Lee Calcote for motivating me and providing me with the appropriate resources. Entering and exploring an open source community can be a daunting task and the [resources provided by Layer5](https://layer5.io/community/newcomers) helped them in overcoming that challenge and enabled them to learn more about the widespread work of [Meshery](https://meshery.io).
+This whole experience has been an amazing journey for me. From being a complete noob to utilizing my expertise in the cloud native infrastructure domain to landing an actual job, the experience has been a maze of ups and downs. But, I feel like I have finally arrived and arrived with a pot of gold. I’m eternally grateful to Lee Calcote for motivating me and providing me with the appropriate resources. Entering and exploring an open source community can be a daunting task and the [resources provided by Layer5](https://layer5.io/community/newcomers) helped them in overcoming that challenge and enabled them to learn more about the widespread work of [Meshery](https://meshery.io).
 
 I’m glad to have found a community that not only feeds my professional success, but also my personal growth. It’s not out of obligation, but out of a sense of gratitude and paying it forward to others (a tenant of the Layer5 community) that I now spend much of my time as a MeshMate. I help welcome and guide other new contributors along their open source path as they learn and grow. Giving to others and while continuing to grow professionally and personally is time well spent.   I encourage you to join me and others in the Layer5 community by jumping into our [Slack](https://slack.layer5.io/) to start meshing around!