@christianv maybe not for this iteration but was thinking the lti embedded page can be directed to a different asset compiled page, and then triggered through the different embedded layout. Would probably greatly slim down the amount of css/js load (you could probably even consider stripping out a good portion of foundation css). ``_roster.scss`` would still stick around for the normal calcentral.scss asset, to support the case of viewing within calcentral of course.