Create website TemplateTemplate creation
Creating website templates in the cosm
First take a look at the website and divide it into three sections: Headline, Bodies and Footsteps. When you create a "theme" (e.g. multiple template for an whole website as distinct from a stand-alone landing page or weblog template), you should scroll through multiple pages to make sure the header/footer items are consistently across pages.
Next, scroll through multiple pages and notice which module appears on ALL pages in the side bar. In order to help the users easily recognize the asset (templates, pictures, file, etc...), you should select a "theme name" and use it in all folders/files that have been generated for this particular name.
If the template is intended for the about section, for example, you should select "About" as theme name. If a user-defined design already existed, it is important to differentiate the new design from the old one. The example above allows you to select "about_v2" as theme name. For a complete website, begin with an inner page, e.g. site pages > 2 columns, not the home page.
Store the template according to the naming conventions you set up in #1. Next is to create a "Global Group" for your header/footer to make these parts reusable across pages. Clone all single moduls into each template without having to create groups globally. If you need to make a modification, you will need to modify each of your template files and modify a number of separate module files.
In the case of groups that are globally defined, you are editing the "Header" group and it changes on all pages. A further important characteristic is the possibility to make each modul globally. That means that anything you create that can be re-used across pages should be done "globally" to make it easy to reuse. If you have, for example, a part of HTML (e.g. a user-defined lookup module), you can make this modul "global" so that it can be re-used across styles.
When you are about to copy/paste the same HTML more than one place, create a globale group/module instead. When you create a Web page template, you should put a custom template onto the sideline. It allows the individual using the template (to create a particular page) to directly attach moduls to the page.
You should group all common page sharing moduls in a single group. Resilient bins should be used for unique panels that only appear on one side. Create a site map (under Content Settings > Site Maps) that you can append to the navigational engine and fill with elements.
When you create a template for a blogsite or target page, you should point the navigator to the available pages (i.e. outside URLs), otherwise you should do so as part of the location migration process. Sometimes this means smart moves like piling the navigations in the portable screen.
They can either link directly to an already created JS or get the corresponding link from the File Manager or the Template Builder.