The templateManager grade currently uses two separate fluid.resourceLoader subcomponents which handle loading the template and l10n messages (named templateLoader and messageLoader, respectively), and, once loaded, a gpii.handlebars templateRenderer that will combine the two and render the markup in the page. This issue is briefly discussed in the pull request for SJRK-288 & SJRK-359

This structure is complex, prone to race conditions, and can be simplified by taking advantages of features introduced to the resourceLoader in / branches of Infusion. See here for documentation of those new features:
https://github.com/fluid-project/infusion-docs/blob/a46115785fff485ecae3b827eedfc2c2b3072b5e/src/documents/ResourceLoader.md#resourceloader-lifecycle

The scope of this Jira is to simplify the way the templateManager works to remove the need for listeners to the onTemplateRendered event in all parts of the Storytelling Tool.