Skip to content

Commit 3dd66a6

Browse files
text updates
1 parent 5be065e commit 3dd66a6

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

modules/ROOT/pages/prerender.adoc

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -51,6 +51,7 @@ Pre-rendering offers the following advantages:
5151
=== Pre-render with Liveboard ID
5252

5353
This method allows you to:
54+
5455
- fully load the embed iframe, including all assets and Liveboard data, as soon as the component is rendered.
5556
- provide the fastest access to the specified Liveboard.
5657
- allow maximum resource usage if the user never views the embed.
@@ -91,11 +92,15 @@ image::./images/pre-render/pre_render_with_liveboard_id.png[]
9192
=== Pre-render without Liveboard ID
9293
This method offers the following advantages:
9394

94-
- Loads common assets and bootstrap logic early
95+
- Loads common assets and bootstrap logic early.
9596
- Defers Liveboard-specific data/API calls until needed.
9697
- Keeps the app ready, making the first Liveboard load faster.
9798
- Still loads some assets even if the user never opens the embed.
9899

100+
As shown in this figure, this method pre-renders common assets and bootstrapping logic early, and then loads the embedded component.
101+
102+
image::./images/pre-render/prerender_without_liveboard_id.png[]
103+
99104
To use this strategy, place the following component on your application's home page, loading page, or landing page:
100105

101106
[source,jsx]
@@ -129,7 +134,6 @@ const PreRenderLiveboardWithoutLiveboardId = () => (
129134
);
130135
----
131136

132-
image::./images/pre-render/prerender_without_liveboard_id.png[]
133137

134138
=== Pre-rendering on demand
135139

0 commit comments

Comments
 (0)