When configuring hst:async = true on an hst component, the default asynchronous rendering mode is by a client side ajax request that fetches the content of the asynchronous components and aggregates it in the page when done. The latter will make sure that the loading of asynchronous parts in the html through ajax calls is triggered Supported Asynchronous Modes Ģ) And make sure that at the end of the renderer, for example just before the closing of the html body ( ) you include the following: If you already have categoryExcludes, it can contain multiple categories separated by a comma. The only thing that needs to be present in the root renderer (jsp / freemarker) template is the following:ġ) If you already have in your renderer the inclusion of hst:headContributions, then make sure you add 'scripts' to the categoryExcludes. The javascript file will execute separate Ajax calls to fetch the rendered output of each asynchronous component and/or container. Pages that contain asynchronous components and/or containers will automatically include a Javascript file in the response. Configure an HST Component to be Rendered AsynchronouslyĪdd the following JCR property to an hst:component or hst:container node to make it asynchronous: hst:async: true For preview requests or views of the application in the Experience manager in the CMS, components that are marked to load asynchronously will be rendered synchronously. Only live requests will actually load components asynchronously. a Twitter feed)Ĭontent that should not be cached or indexed by search engines a 'stores near you' component)Ĭontent that accesses a potentially slow external service (e.g. Common use cases are:Ĭontent that is customized for a particular visitor (e.g. Asynchronous HST Components and Containersīoth HST components and HST containers can be rendered asynchronously out-of-the-box.

Dotbot copy file to repo