update

Signed-off-by: Lee Calcote <[email protected]>

content/en/_index.md

@@ -35,22 +35,8 @@ title: Layer5
 <div class="dash-ircle-container">
   <div class="dash-ircle"></div>
 </div>
-<!-- {{< /blocks/cover >}}
 
-{{< card header="**Imagine**" title="Artist and songwriter: John Lennon" subtitle="Co-writer: Yoko Ono"
-          footer="![SignatureJohnLennon](https://server.tld/…/signature.png 'Signature John Lennon')">}}
-Imagine there's no heaven, It's easy if you try<br/>
-No hell below us, above us only sky<br/>
-Imagine all the people living for today…
-
-…
-{{< /card >}}
-
-{{% blocks/lead color="primary" %}}
-Jump right in and learn about Layer5.
-{{< blocks/link-down color="info" >}}
-
-{{% /blocks/lead %}} -->
+{{< /blocks/cover >}}
 
 <!--
 {{% blocks/section color="dark" type="row" %}}

content/en/meshmap/_index.md

@@ -1,6 +1,6 @@
 ---
-title: Documentation
-linkTitle: MeshMap
+title: MeshMap Documentation
+linkTitle: Overview
 type: docs
 menu: {main: {weight: 3}}
 weight: 1
@@ -34,21 +34,36 @@ cascade:
 
 {{% /pageinfo %}}
 
+## What is MeshMap?
+
+<div style="display:flex;justify-content:center;margin:1rem;">MeshMap is a web-based application that allows users to create and share diagrams of cloud native infrastructure for Kubernetes. Users can draw shapes, lines, text, and icons to represent the components and relationships of their Kubernetes clusters. MeshMap supports freestyle design, meaning that users can customize the appearance and layout of their diagrams without any constraints. MeshMap also enables real-time collaboration, meaning that users can invite others to join their sessions and edit the diagrams together. MeshMap is a simple and intuitive tool for designing and communicating cloud native infrastructure for Kubernetes.</div>
+
+## What is MeshMap Modes
+
+Choose your mode of operation for MeshMap.
+
 <div style="display:flex;justify-content:center;">
 {{< cardpane >}}
     <a href="../designer/">
   {{< card header="Designer" >}}
-    <a name="visualizer"></a>Designer mode is for those who want to create their own MeshMap, using the palette of components provided by Meshery.
+    <a href="../designer/">Designer</a> mode is for those who want to create their own MeshMap, using the palette of components provided by Meshery.
+    <p>Drag-and-drop your cloud native infrastructure using a pallete of thousands of versioned Kubernetes components.</p>
+    <p>Use context-aware relationships configure your infrastructure intuitively.</p>
   {{< /card >}}
     </a>
   <a href="../visualizer/">
   {{< card header="Visualizer" >}}
-    <a name="visualizer"></a> Visualizer mode is for operating your Kubernetes clusters and cloud native infrastructure.
+    <a href="../visualizer/">Visualizer</a> mode is for operating your Kubernetes clusters and cloud native infrastructure.
+    <p>Bring all your Kubernetes clusters under a common management. Deploy designs, apply patterns, manage and operate your deployments and services in real-time.</p>
+    <p>Interactively connect to pods and containers to debug and troubleshoot.</p>
   {{< /card >}}
   </a>
 {{< /cardpane >}}
 </div>
 
+
+
+
 <!-- ## What is MeshMap?
 
 Introduce your project, including what it does or lets you do, why you would use it, and its primary goal (and how it achieves it). This should be similar to your README description, though you can go into a little more detail here if you want.

content/en/meshmap/visualizer/_index.md

@@ -2,18 +2,36 @@
 title: Navigating Visualizer
 weight: 5
 description: >
-  Visualizer mode is for operating your Kubernetes clusters and cloud native infrastructure.
+  Visualizer mode is for operating your Kubernetes clusters and cloud native infrastructure. 
 categories: [Visuzalizer]
 ---
 
-{{% pageinfo %}}
-Discover and visualize your Kubernetes clusters and cloud native infrastructure.
-{{% /pageinfo %}}
+Discover and examine your Kubernetes clusters and cloud native infrastructure using Visualizer mode.
+
+## Using Filters
+
+Using filters you can select the Kubernetes resources you want to view. Apply one or more filters to narrow down the resources you want to view.
+
+## Search and Select Specific Resources
+
+Using the search bar, you can search for specific resources and select them. The selected resources are highlighted in the Visualizer canvas. Details of the selected resources are displayed in the right panel.
+
+<!-- {{< figure src="images/visualizer-filters.png" link="images/visualizer-filters.png"  width="100%"  >}} -->
+
+## Connecting with Kubernetes Pods
+
+Visualizer supports connecting to Kubernetes pods via the following methods.
 
 ### Understanding Log Streamer
 
 {{< figure src="images/log-stream-sequence-diagram.svg" link="images/log-stream-sequence-diagram.svg"  width="100%"  >}}
 
-<!-- For many projects, users may not need much information beyond the information in the [Overview](/docs/overview/), so this section is **optional**. However if there are areas where your users will need a more detailed understanding of a given term or feature in order to do anything useful with your project (or to not make mistakes when using it) put that information in this section. For example, you may want to add some conceptual pages if you have a large project with many components and a complex architecture.
+### Understanding Interactive Terminal
+
+The interactive terminal behaves in a fashion similar to similar to the behavior of the `kubectl exec` command, but web-based.
+
+While using using the interactive terminal, understand that you can only open one session per container.
+Each session's data is streamed via Meshery Broker (NATS) from MeshSync to Meshery Server / MeshMap.
+The GraphQL subscription between your web browser running MeshMap and Meshery Server provides isolation between other users who might be concurrently sharing an interactive terminal. Each connection established a unique session ID.
 
-Remember to focus on what the user needs to know, not just what you think is interesting about your project! If they don’t need to understand your original design decisions to use or contribute to the project, don’t put them in, or include your design docs in your repo and link to them. Similarly, most users will probably need to know more about how features work when in use rather than how they are implemented. Consider a separate architecture page for more detailed implementation and system design information that potential project contributors can consult. -->
+{{< figure src="images/interactive-terminal-sequence-diagram.svg" link="images/interactive-terminal-sequence-diagram.svg"  width="100%"  >}}