The [@cms.init /] directive name is misleading. When it was created in Magnolia 4.5 the name actually reflected what the directive did (at least in part) as it injected the GWT-generated js and css which were needed to make page editor work, besides providing info about the preview status, i18n and what not. As of Magnolia 5.0 all it does is actually creating a "cms:page" tag to instruct the page editor about the current content and the page properties dialog id. We should thus deprecate the old cms.init and replace it with a more properly named cms.page directive.