update

Signed-off-by: Lee Calcote <lee.calcote@layer5.io>

Author: leecalcote

content/en/cloud/workspaces/_index.md

@@ -42,7 +42,7 @@ After creating a Workspace, of your next steps is to resource that Workspace. Li
 - One or more environments can be assigned to a workspace.
 - Same environment can be assigned to multiple workspaces.
 
-See "[Environments](/concepts/environments)" section for more information.
+See [Environments](https://docs.meshery.io/concepts/environments) section for more information.
 
 ### Designs
 
@@ -51,22 +51,22 @@ See "[Environments](/concepts/environments)" section for more information.
 - One ore more designs can be assigned to a workspace.
 - Same design can be assigned to multiple workspaces.
 
-See "[Meshery Designs](/concepts/designs)" section for more information.
+See [Meshery Designs](https://docs.meshery.io/concepts/designs) section for more information.
 
 ### Teams 
 - A Workspace is closely associated with Teams in Meshery. Teams are groups of users with varying permissions, and they are at the center of resource access and management within a Workspace.
 - One ore more teams can be assigned to a workspace.
 - Same team can be assigned to multiple workspaces.
 
-See "[Teams](/extensions/team-management)" section for more information.
+See [Teams](../identity/teams) section for more information.
 
 ### Connections
 
 - Connections in Meshery refer to various resources that can be either managed or unmanaged, but are discovered and made accessible for use. Examples of Connections include Kubernetes clusters, Prometheus instances, Jaeger services, Nginx deployments, and more. These Connections serve as a fundamental part of Workspaces, as users can deploy infrastructure designs within the context of these Connections.
 - Connections can be assigned to one or more environments.
 - Same connection can be assigned to multiple environments.
 
-See [Connections in Meshery Docs](https://docs.meshery.io/concepts/connections) section for more information.
+See [Connections](https://docs.meshery.io/concepts/connections) section for more information.
 
 ## Best Practices
 

content/en/meshmap/concepts/_index.md

@@ -3,15 +3,22 @@ title: Working with Components
 weight: 4
 type: docs
 description: >
-  What does your user need to understand about your project in order to use it - or potentially contribute to it?
+  Meshery Designs are descriptive, declarative characterizations of how your Kubernetes infrastructure should be configured.
 categories: [Designer]
 tags: [designs]
 ---
 
-{{% pageinfo %}}
-Page under construction.
-{{% /pageinfo %}}
+## Designs
 
-<!-- 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.
+Designs are declarative, descriptive characterizations of how your Kubernetes infrastructure should be configured. Designs are versioned and can be shared with other users and teams. Designs are the primary tool for collaborative authorship of your infrastructure and services. 
 
-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. -->
+### Using Designs
+
+
+### Design Relationships and Restrictions
+- Access to Designs may be granted to one or more users.
+
+### Controlling Access to Designs
+When creating a new design by default it's visibility level will be set to __public__ unless you are an active Lara, five subscriber, in which case you can change this default to __private__. 
+
+{{< alert title="Google Docs Analogy" >}}Google Docs are a useful analogy for understanding Meshery designs. In many ways a Meshery design is like a single Google Doc in that they are collaboratively authored, versioned, permissioned and can move from workspace to workspace. Workspaces, a shared collection of designs, can be likened to a Google Drive, a shared collection of files.{{< /alert >}}