Merge branch 'layer5io:master' into master

CONTRIBUTING.md

@@ -1,9 +1,9 @@
 # <a name="contributing">Contributing Overview</a>
 Please do! Thanks for your help improving the project! :balloon:
 
-All contributors are welcome. Please see the [newcomers welcome guide](https://docs.google.com/document/d/17OPtDE_rdnPQxmk2Kauhm3GwXF1R5dZ3Cj8qZLKdo5E/edit) for how, where and why to contribute. This project is community-built and welcomes collaboration. Contributors are expected to adhere to our [Code of Conduct](.CODE_OF_CONDUCT.md).
+All contributors are welcome. Please see the [newcomers welcome guide](https://layer5.io/community/newcomers) for how, where and why to contribute. This project is community-built and welcomes collaboration. Contributors are expected to adhere to our [Code of Conduct](CODE_OF_CONDUCT.md).
 
-Not sure where to start? First, see the [newcomers welcome guide](https://docs.google.com/document/d/17OPtDE_rdnPQxmk2Kauhm3GwXF1R5dZ3Cj8qZLKdo5E/edit). Grab an open issue with the [help-wanted label](../../labels/help%20wanted) and jump in. Join the [Slack account](http://slack.layer5.io) and engage in conversation. Create a [new issue](/../../issues/new/choose) if needed.  All [pull requests](/../../pulls) should reference an open [issue](/../../issues). Include keywords in your pull request descriptions, as well as commit messages, to [automatically close issues in GitHub](https://help.github.com/en/github/managing-your-work-on-github/closing-issues-using-keywords).
+Not sure where to start? First, see the [newcomers welcome guide](https://layer5.io/community/newcomers). Grab an open issue with the [help-wanted label](../../labels/help%20wanted) and jump in. Join the [Slack account](http://slack.layer5.io) and engage in conversation. Create a [new issue](/../../issues/new/choose) if needed.  All [pull requests](/../../pulls) should reference an open [issue](/../../issues). Include keywords in your pull request descriptions, as well as commit messages, to [automatically close issues in GitHub](https://help.github.com/en/github/managing-your-work-on-github/closing-issues-using-keywords).
 
 **Sections**
 - <a name="contributing">General Contribution Flow</a>

assets/scss/_navbar_project.scss

@@ -10,9 +10,19 @@
     color: $primary !important;
   }
 
+ @media (min-width: 768px) {
+  &:hover {
+    .dropdown-menu {
+      display: block;
+    }
+      .dropdown-menu {
+        transform: translate(-15%, 0rem);
+      }
+  }
+}
   .dropdown-menu {
     padding: 0;
-    transform: translate(-15%, 2.5rem) !important;
+    transform: translate(-15%, 2.5rem);
     border-radius: 0;
     .dropdown-item {
       height: 5rem;

content/en/cloud/self-hosted/_index.md

@@ -6,7 +6,7 @@ description: >
   Keep your MeshMap designs internal to your workplace. Get remote support from Layer5 when you need it.
 ---
 
-![self-hosted](images/self-hosted.svg "image-right-no-shadow")
+<img class="image-right-no-shadow" src="images/self-hosted.svg" width="40%" />
 
 ## On-premises Deployment of Layer5 Cloud
 

content/en/meshmap/designer/export-designs/_index.md

@@ -44,4 +44,4 @@ If your design was generated from a source like HelmChart, Kubernetes manifest,
 ## Exporting as Embedding
 
 Exporting your design as an embedding allows you to integrate it into websites, blogs, or other platforms that support HTML, CSS, and JavaScript. The embedded design version offers a visually interactive representation of your design, making it easy to share with infrastructure stakeholders.
-[Learn more](embedding-designs) about Embedding Designs.
+[Learn more](../embedding-designs) about Embedding Designs.

content/en/meshmap/reference/contributing-to-docs.md

@@ -33,7 +33,7 @@ Here's a quick guide to updating the docs:
    See the [Layer5 contributor guide](https://layer5.io/community/handbook/contribution).
 
 If you need more help with the GitHub workflow, follow
-this [guide to a standard GitHub workflow](https://github.com/layer5io/docs/blob/master/quick-github-guide.md).
+this [guide to a standard GitHub workflow](https://github.com/layer5io/docs/blob/master/CONTRIBUTING-gitflow.md).
 
 ## Local development
 

content/en/meshmap/tasks/designs/deploying-designs.md

@@ -7,10 +7,55 @@ categories: [Designer]
 tags: [designs]
 ---
 
-{{% pageinfo %}}
-Page under construction.
-{{% /pageinfo %}}
+1. To deploy a design, navigate to the **Actions** button at the top of the Design canvas.
 
+2. Click on the **Deploy** icon.
+
+3. This opens a modal that will take you through all the steps before the final deployment.
+
+4. Click on **Open In Visualizer** to see the pre-filtered view of the deployed resources in the cluster
+
+5. Click **Finish**
+
+![success-deploy](/meshmap/getting-started/images/deploy-designs/success-deploy.png)
+
+### Deployment Errors
+
+1. **Missing Namespace**: This error occurs when you attempt to create a Kubernetes resource without specifying a namespace. Kubernetes requires that all resources have an associated namespace.
+
+![missing-ns](/meshmap/getting-started/images/deploy-designs/missing-ns.png)
+
+2. **Empty Label Selector**: This error indicates an empty label selector.
+
+![empty-ls](/meshmap/getting-started/images/deploy-designs/empty-ls.png)
+
+### Troubleshooting Errors
+
+When reviewing validation, dry run, or deployment issues, you’ll notice specific error codes denoted from time to time.
+
+As a system, Meshery itemizes different errors that occur and assigns a unique error code to each along with details on how to remediate the issue at hand.
+
+For the comprehensive list of error codes refer to [Error Code Reference](https://docs.meshery.io/reference/error-codes) in the Meshery documentation.
+
+If you encounter persistent issues consider consulting the [Meshery Community forum](https://discuss.layer5.io/c/meshery/5)
+
+![error-code](/meshmap/getting-started/images/deploy-designs/error-code.png)
+
+
+### Using the Notification Center for Troubleshooting
+
+The Notification Center in Meshery helps manage events during the deployment process. It provides real-time updates and alerts on the status of the deployment. This feature can be particularly useful for troubleshooting, as it:
+
+1. Displays immediate feedback on the success or failure of each deployment step.
+1. Highlights specific error messages and codes, helping you quickly identify and understand issues.
+1. Offers links to detailed documentation and guides for resolving common problems.
+1. Keeps a log of past notifications, allowing you to track and review previous errors and their resolutions.
+
+![notification](/meshmap/getting-started/images/deploy-designs/notification.png) 
+
+![notification-center](/meshmap/getting-started/images/deploy-designs/notification-center.png)
+
+By actively monitoring the Notification Center, you can promptly address issues as they arise, ensuring a smoother deployment process. Learn more about [Managing Events with the Notification Center](https://docs.meshery.io/guides/events-management).
 
 <!-- Text can be **bold**, _italic_, or ~~strikethrough~~. [Links](https://gohugo.io) should be blue with no underlines (unless hovered over).