Above-the-fold loading is a technique that prioritizes the creation of components that are “above the fold”. The term “above the fold” is traditionally known as the upper-half of a newspaper, where the most important stories are located. When this concept is transferred to the web, it refers to all the components that are placed at the top of the page, where the experience starts.
簡而言之,頁面上部分最重要的内容最先加載。
Above-the-fold loading要想工作,需要以下三個基礎設施的支撐:
Deferred loading, which is a technique that postpones the creation of components that are “below the fold”. For more information, see Deferred Loading.
對below the fold的元件進行延遲加載。
The notion of the “page fold”. The page fold is not static, and differs from device to device, from screen to screen, and even changes depending on the size of the browser.
Page fold的定義。該定義不是一成不變的,随着裝置和螢幕的不同,甚至浏覽器尺寸的改變而變化。
A couple of CSS rules that initially move components below the page fold.
The page fold is configurable for each page template and breakpoint.
Page fold基于每個頁面模闆和breakpoint來配置。
The page fold configuration is only an indication to speed up the initial creation of page slots that are above the fold. All page slots are eventually rendered if they happen to be above the fold. You designate the page fold by assigning a page slot to the pageFold parameter. This page slot, and all previous, sibling page slots, are “above the fold”. These page slots are prioritized ahead of page slots that are “below the fold”.
The page fold is part of the LayoutConfig configuration. The page fold indicates the last page slot that should be rendered above the fold.
Page fold是LayoutConfig的一部分,page fold是一個基點,所有page fold之前的Component,都會優先被渲染。
一個例子:
LandingPage2Template: {
pageFold: 'Section2B',
slots: [
'Section1',
'Section2A',
'Section2B',
[...]
]
}
1
2
3
4
5
6
7
8
9
Section2B和之前的Component,Section1和Section2A都會得到優先渲染的機會。
還可以基于每個breakpoint定義page fold:
ProductDetailsPageTemplate: {
md: {
pageFold: 'UpSelling'
},
xs: {
pageFold: 'Summary'
'Summary',
'UpSelling',
10
11
12
13
Page fold和CSS相關的設定
By default, when page slots are loaded on the page, there is no minimum height available for the page slots or components.
預設情況下,當頁面page slot内的Component加載時,沒有所謂的minimum height設定。
The actual height is only added when components are loaded, and the associated CSS rules are applied to the components.
隻有當Component真正被加載時,才能确定真實的高度是多少。
The page slots adjust their height automatically when components are loaded. Therefore, page slots do not have an initial height, which is why they initially end up in the viewport. This prevents the deferred loading technique from working, because it depends on content not being in the viewport.
Given that content can be added at runtime, it is not possible to implement a (hard-coded) minimum height for page slots or components – it all depends on what the business will add at runtime.
所謂的ghost design:
While this lack of minimum height could be filled up by so-called “ghost design” CSS rules, there will always be a gap between the ghost design and the actual content. Furthermore, ghost design rules require an implementation effort that might not be available.
To make it possible to defer the loading of below-the-fold content, Spartacus marks page slots that are below the page fold while page slots above the fold are being loaded. All page slots are marked with an is-pending class as long as all the inner components are not loaded.
below-the-fold Component被标記成is-pending class和page-fold class.
Additionally, the page fold slot has a page-fold class. With these two classes, Spartacus can apply various CSS rules to control deferred loading of below-the-fold content.
The following CSS shows all pending page slots after the pending page-fold, and moves them below the fold with a margin-top.
下列css使用margin-top, 将below-the-fold的Component移動到page-fold之下:
cx-page-slot.cx-pending.page-fold ~ cx-page-slot.cx-pending {
margin-top: 100vh;