For HTML5 outputs, Author-it automatically creates the chrome for each output, where chrome is the HTML5 application in which the content is displayed to the user. The chrome includes structure and navigation, resource management, responsive/adaptive behaviours, and other non-content functionality typically associated with knowledge portals, elearning/mobile learning/assessments, presentations, and interactive information applications.
In summary, Author-it will insert your interactive asset inside a content element, within the Author-it chrome. With a few exceptions, your interactive assets should not include any chrome at all. The only exceptions could be navigation items required within the individual asset, and these navigation items should use an absolute minimum amount of screen space compared to the content. Consider the following:
Maximum screen space for your asset:
Reduced screen space for your asset:
In some uses, your asset can be opened in a modal window and therefore operate independently of the Author-it chrome. This is decided by the Author-it user on a case by case basis, and it is feasible that a single asset may be re-used multiple times sometimes within the Author-it chrome and sometimes in a modal window, possibly in the same course. We suggest you discuss the requirements with your client, define possible and preferred usage before starting development, and test as early as possible.