You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/kanvas/designer/understanding-edges/index.md
+20-21Lines changed: 20 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,15 +7,15 @@ categories: [Designer]
7
7
tags: [designs]
8
8
---
9
9
10
-
When you connect components in [Kanvas](https://kanvas.new/), the line you draw is called an edge. Each edge visually represents a [relationship](https://docs.layer5.io/kanvas/concepts/relationships/) between your components. This guide will help you understand how to use different edge styles to create clear and effective infrastructure diagrams.
10
+
When you connect components in [Kanvas](https://kanvas.new/), the line you draw is called an **edge**. Each edge visually represents a [relationship](https://docs.layer5.io/kanvas/concepts/relationships/) between your components. This guide explains how to use different edge styles to create clear and effective infrastructure designs.
11
11
12
12

13
13
14
-
## Types of Edges
14
+
## Understanding Edge Types
15
15
16
16
In Kanvas, there are two main types of edges, each serving a different purpose:
17
17
18
-
### Semantic Edges
18
+
### Semantic Edges: Representing Real Infrastructure
19
19
20
20
These edges represent real infrastructure relationships that Kanvas can understand and manage. For example:
21
21
- Network connections between services
@@ -26,7 +26,7 @@ Kanvas uses these edges during deployment to understand how your components shou
26
26
27
27
> For detailed information about each relationship type, visit [Relationships Documentation](https://docs.layer5.io/kanvas/concepts/relationships/)
28
28
29
-
### Non-semantic Edges
29
+
### Non-semantic Edges: Annotating Your Designs
30
30
31
31
These are visual aids that help you document and explain your design. They are useful for:
32
32
- Adding explanatory notes
@@ -35,20 +35,20 @@ These are visual aids that help you document and explain your design. They are u
35
35
36
36
Kanvas ignores these edges during deployment as they are purely for documentation.
37
37
38
-
## Edge Styles
38
+
## Working with Edge Styles
39
39
40
-
### Default Edge Styles
40
+
### Default Styles
41
41
42
-
To help you quickly understand your diagrams, Kanvas uses specific default styles for each type of edge:
42
+
To help you quickly understand your designs, Kanvas uses specific default styles for each type of edge:
@@ -57,52 +57,51 @@ To help you quickly understand your diagrams, Kanvas uses specific default style
57
57
58
58
### Customizing Edge Styles
59
59
60
-
While the default styles are designed to be clear and consistent, Kanvas gives you the flexibility to customize any edge to better suit your needs. Simply select an edge to reveal the styling toolbar.
60
+
While the default styles are designed to be clear and consistent, Kanvas gives you the flexibility to customize any edge to better suit your needs. Simply click an edge to reveal the styling toolbar.
61
61
62
-
#### Line Types
62
+
#### Choosing a Line Type
63
63
- Dashed Line: For proposed or optional connections
64
64
- Wave Line: For asynchronous or non-continuous connections
65
65
- Zigzag Line: For disrupted or unreliable connections
66
66
- Tree Line: For hierarchical relationships (parent-child, system-subsystem)
67
67
- Line with Circles: For weak or indirect associations
68
68
- Bezier Curve: For non-linear or indirect connections
69
69
70
-
#### Endpoint Types
70
+
#### Defining Connection Points
71
71
- Arrow Head (Default): Shows general direction or flow
72
72
- Filled Diamond: For "whole-part" relationships (aggregation)
73
73
- Filled Square: For strong ownership relationships (composition)
74
74
- Filled Triangle: For inheritance or "is-a" relationships
75
75
- Filled Circle: For loose containment relationships
76
76
77
-
> **Note**: While Kanvas supports these UML-style relationships, the most commonly used styles are straight lines, dotted lines, and arrow heads. Use other styles when you need to express specific types of relationships in your diagrams.
77
+
> **Note**: While Kanvas supports these UML-style relationships, the most commonly used styles are straight lines, dotted lines, and arrow heads. Use other styles when you need to express specific types of relationships in your designs.
78
78
79
-
#### Colors
79
+
#### Using Color for Visual Cues
80
80
81
-
Colors help you create a visual language in your diagrams. While Kanvas has default colors, you can use any color to convey meaning:
81
+
Colors help you create a visual language in your designs. While Kanvas has default colors, you can use any color to convey meaning:
82
82
83
-
Default Colors
83
+
**Default Colors**
84
84
- Green: For non-semantic annotations
85
85
- Grey/Blue: For semantic relationships
86
86
87
-
Suggested Color Meanings
87
+
**Suggested Color Meanings**
88
88
- Yellow: For connections that need review
89
89
- Red: For issues or breaking changes
90
90
91
-
###Labels and Annotations
91
+
#### Adding Labels
92
92
93
93
You can add text directly to edges to provide more information. This is especially useful for:
94
94
- Describing traffic flow (e.g., "User Traffic → API Gateway")
95
95
- Adding process steps (e.g., "Requires Manual Review")
96
96
- Noting important details (e.g., "Backup Route (Low Priority)")
97
97
- Specifying protocols (e.g., "gRPC / 50051")
98
98
99
-
### Visual Effects
99
+
#### Applying Visual Effects
100
100
101
101
The "Marching-ants" animation effect can be added to any edge to:
102
102
- Highlight specific connections in team reviews
103
103
- Emphasize critical paths
104
104
105
-
106
105
{{< alert title="Learn More About Interpreting Designs" type="info" >}}
107
106
To learn how to interpret and understand designs in practice, including how components work together in a design, visit our comprehensive guide in the [Layer5 Academy](https://cloud.layer5.io/academy/learning-paths/mastering-meshery/introduction-to-meshery?chapter=interpreting-meshery-designs).
0 commit comments