Response rendering for themes
To improve response times of the portal, a template parser resolves which modules are needed, and collects all of the modules enabled by the current profile. Dynamic content spots (dyn-cs) are resolved by invoking the Dynamic Content Spot Mapping DataSource. If logical names mapped to a URI includes module information, the spot is rendered if the module is defined for the current profile. When the template parser encounters a dynamic content spot, the combiner service...
- Decodes the URI
- Collects modules enabled by the current profile
Contributions to each type are aggregated into sets and processed in this order...
- CSS
The framework generates a link element with an href attribute whose value is a URL that resolves to the combined results of all contributions to CSS at the head extension point. When debug is enabled, separate link elements are generated for each contribution. CSS is only valid in the head extension point.
- Static JavaScript configuration
The framework writes an external <script> tag with a src attribute whose value is a URL that resolves to the combined results of all contributions to static JavaScript configuration at the current extension point. When debug is enabled, separate script elements are generated for each contribution.
- Dynamic JavaScript configuration
The framework generates an inline script tag that loads the combined results of all contributions to dynamic JavaScript configuration at the current extension point.
- JavaScript code
The framework generates an external script tag that loads the combined results of all contributions to JavaScript code at the current extension point. When debug is enabled, separate script elements are generated for each contribution.
- Markup
The framework directly writes the output from each markup contribution at the current extension point to the output stream. This framework is intended to be used for markup that always shows in the page when this module is enabled. Use markup for content that is not visual but is semantic. Do not use portal render request-dependent attributes, because there is no guarantee that those attributes are available in all cases. For example, when used in deferred mode, the render context is not available.
Parent The module framework