Skip to content

Commit 1985e6f

Browse files
authored
Merge pull request #564 from zihanKuang/url-parameters
Docs: Introduce 'render=full' URL parameter for detailed design rendering
2 parents b456286 + 22c5f76 commit 1985e6f

File tree

3 files changed

+55
-0
lines changed

3 files changed

+55
-0
lines changed
Lines changed: 55 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,55 @@
1+
---
2+
title: Design Render Quality
3+
description: >
4+
Control the level of detail in Kanvas design rendering using advanced URL query parameters.
5+
weight: 2
6+
categories: [Designer, Operator]
7+
tags: [performance]
8+
---
9+
10+
By default, Kanvas optimizes the rendering of your designs to ensure good performance and responsiveness. This means that some computationally intensive visual elements, such as advanced relationships like **TagSets** (groups of components visually demarcated), might not be displayed initially to reduce system load.
11+
12+
> To learn more about defining relationships between components, including the detailed use and creation of **TagSets**, please see the [Creating Relationships | Layer5 Documentation](https://docs.layer5.io/kanvas/getting-started/creating-relationships/).
13+
14+
## Enable Full Render Mode
15+
16+
To activate this full render mode, you will need to add the `render=full` parameter to your Kanvas design URL. This mode ensures all elements, including **TagSets**, are displayed, which might otherwise be hidden for performance optimization.
17+
18+
The images below illustrate the difference this parameter makes:
19+
20+
<figure>
21+
<img src="/kanvas/advanced/url-parameters/no-tagsets.png" alt="Design rendering in Kanvas with default settings" />
22+
<figcaption>A design with default rendering; TagSets may not be visible</figcaption>
23+
</figure>
24+
25+
<figure>
26+
<img src="/kanvas/advanced/url-parameters/with-tagsets.png" alt="The design in Kanvas showing full details" />
27+
<figcaption>The same design with `render=full` applied; TagSets and all other details are now visible</figcaption>
28+
</figure>
29+
30+
For example, to apply this to a Kanvas design URL, you would modify it as follows: `https://kanvas.new/extension/meshmap?render=full&mode=design&design=xxxx`
31+
32+
{{< alert title="Advanced Usage Note" type="info">}}
33+
This is an advanced feature primarily intended for power users, debugging scenarios, or system-level integrations. You will not need to manually adjust this parameter for everyday design work.
34+
{{< /alert >}}
35+
36+
## Why Use Full Render Mode?
37+
38+
This capability is particularly valuable for:
39+
40+
* **Detailed Inspection & Debugging:** When you need to meticulously review, debug, or verify all components, relationships, and intricate details within a design.
41+
* **Comprehensive Documentation:** For creating thorough screenshots or technical documentation that requires all visual elements to be accurately represented.
42+
* **System & Integration Testing:** During testing phases to ensure all parts of a design are processed and displayed by the rendering engine exactly as expected.
43+
44+
## Best Practices
45+
46+
To use full render mode effectively:
47+
48+
1. **Use Selectively for Performance**
49+
Activate `render=full` mainly when you need to inspect specific designs in detail. Since it can impact performance on large or complex designs, stick to the default optimized mode for general browsing to maintain responsiveness.
50+
51+
2. **Promote Consistent Shared Views**
52+
When sharing a design link with `render=full` for review, advise collaborators to also enable the relevant toggles in their **Layers panel**. This helps prevent discrepancies caused by individual layer settings, ensuring everyone sees the same details.
53+
54+
3. **Check the Layers Panel if Details Are Missing**
55+
If `render=full` is active in your URL but expected elements (like **TagSets**) are not visible, verify that their visibility is enabled in your **Layers panel**. Your Layers settings can hide elements even when full render is requested.
Loading
Loading

0 commit comments

Comments
 (0)