...
Create the MultiExcerpt key containing the content you want to leverage by reusing/displaying it in other locations. To know more on how to create MultiExcerpt content, click here.
The following are the available MultiExcerpt macros:MultiExcerpt Macro
MultiExcerpt Fast Excerpt (InlineAdvanced)
MultiExcerpt Fast Excerpt (BlockAdvanced Inline)
Inserting the MultiExcerpt Include to reuse/display the excerpted content. To know more on how to reuse MultiExcerpt content, click here.
The following are the available MultiExcerpt Include macros:MultiExcerpt Include
MultiExcerpt Fast MultiExcerpt Include (InlineAdvanced)
MultiExcerpt Fast MultiExcerpt Include (BlockAdvanced Inline)
Difference between MultiExcerpt
...
and MultiExcerpt Advanced
Summary:
for legacy pages, you should prefer the "FastAdvanced" macros
for new "fabric" pages you should prefer the regular macros (MultiExcerpt, MultiExcerpt Include) because there is no speed advantage in the Fast Advanced macros on new pages and dynamic macros have limitations.
...
In a past Confluence version, Atlassian made changes to the rendering of pages which slowed down page loading for pages with several MultiExcerpts or MultiExcerpt Includes. MultiExcerpts are "static" macros and, for pages created with the old legacy page editor, page rendering was blocked until all "static" macros were ready. We resolved this issue by implementing the MultiExcerpt Fast Excerpt and MultiExcerpt Fast Include MultiExcerpt (Advanced) and MultiExcerpt Include (Advanced) macros within the MultiExcerpt app. The "FastAdvanced" versions are based on dynamic Connect app technology that does not block page rendering for pages created with the old legacy page editor.
Fast forward to today and Atlassian has introduced a new page editor (a.k.a. the fabric page editor). Pages created with the new page editor do NOT block rendering for "static" macro processing. It is not necessary to use the "FastAdvanced" (dynamic) versions of the MultiExcerpt macro for new/fabric pages. It may be preferable to stick with the "static" MultiExcerpt and MultiExcerpt Include macros for new/fabric pages because the Fast Advanced macros have some limitations due to the nature of dynamic macros (rendered in an iFrame).
As an added complexity: there are many behaviours of new/fabric pages that are undesirable and inconsistent with the behaviours of legacy pages. In some cases, you may be forced to use a legacy page to get a feature or behaviour that has not been implemented or does not work in the new/fabric pages. When you are forced to use a legacy page you should prefer the "FastAdvanced" versions of the macros but beware that they come with some limitations: for example, if you nest a Confluence Table macro inside of a MultiExcerpt then table sorting will not work in the "FastAdvanced" version because the iframe containing the content does not have access to the CSS styling of the containing page and Confluence's Table macro depends on the CSS styling of the containing page. In a case like that, you must choose the simpler, but not as performant, "static" macros.
...
Difference between inline and block
The MultiExcerpt Fast Advanced macros provide you with two different options inline and block. The following table provides the differences between inline and block macros:
...