Template Development. We will develop the page type templates based on the approved designs.
Template Development. Timing: approximately 10 to 12 business days Based on our discussions, it is our understanding that the site will continue to leverage the ektron content management tool and will be hosted with Xxxxxxx.xxx. We, therefore, assume that OneBeacon will provide Small Army with any necessary software/licenses for such development. Upon approval of the site design, Small Army will immediately develop a series of HTML templates that will serve as the foundation for the entire site. Small Army will conduct this development Internally on Small Army development servers, and provide access to OneBeacon for regular review and approval. All templates will also be tested across Web browser and operating systems to ensure 100% compatibility with identified browsers.
Template Development. Timing: approximately 6 to 8 business days per site Upon approval of the site design, Small Army will immediately develop a series of HTML templates that will serve as the foundation for the entire site. Small Army will conduct this development internally on Small Army development servers, and provide access to OneBeacon (and the reciprocal companies) for regular review and approval. All templates will also be tested across Web browsers and operating systems to ensure 100% compatibility with the required browsers. Recognizing that the majority of content on the site will be static, we are not recommending that a content management tool be implemented at this time for the entire site. However, once the site maps are established, we may identify some areas where a content management tool could be useful for more frequent updating. In this proposal, we have not included costs for a content management feature, but we can provide a subsequent proposal for such implementation if it is determined to be necessary,
Template Development. Decca will present 2 design options. Estimate includes design, layout, and 2 revision cycles. Templates will include Letterhead and Business cards, 1-page ad, 2-page brochure, e-newsletter, presentation template, and poster. Communications Strategy
Template Development. The template files are located in your project plugin (bundles/<PROJECT>/tpl and bundles/<PROJECT>/res. In res folder you can find static resources (css, images, javascript), and tpl folder is the one where your velocity templates are located. By default Chon CMS will have 3 types on nodes (home page, category and html), and corresponding velocity templates are located in tpl/pages/, home.html, category.html and view.html. HTML rendering starts with tpl/pages/base.html (for all nodes), and inside body your specific content is rendered based on your node type (home.html, category.html or view.html). In templates 3 variables are passed: $this – current node $ctx – application context $ext – extension map Creating new plugin To generate new plugin, navigate to bundles directory and use: mvn com.choncms:chon-generate:new-plugin Let’s say we want very simple plugin that updates a counter when we get a hit on the page. When above mvn command asks for a name we would call it com.interworks.visitor.counter; that will generate new OSGi based plugin in bundles directory. Note the creation structure of a plugin. It is fully compliant OSGi bundle that can be right after creation imported in eclipse and ready for development. Best way to develop a plugin is to use eclipse PDE features. To setup eclipse see next section. For counter plugin, update count code initial trigger would be in base.html since in that file all other templates are included. Each html node request is rendered using base.html. So, in base.html an extension can be called that updates simple counter stored in JCR. Anywhere in base.html add code: $ext.counter What will happen in rendering pipeline: The framework will see if counter extension is registered (see app.registerExtension), get extension object (the class that implements org.chn.cms.core.Extenstion) and retrieve front end template object (call getTplObject on extension). For counter only call to getTplObject can be used to update back end storage counter. Here is complete example how Extension implementation would look like: package com.interworks.visitor.counter; import xxxx.xxxx.Xxx; import org.chon.cms.core.Extension; import org.chon.cms.model.ContentModel; import org.chon.cms.model.content.IContentNode; import org.chon.cms.model.content.PropertyType; import org.chon.web.api.Request; import org.chon.web.api.Response; import org.chon.web.mpac.Action; public class CounterExtension implements Extension { @Override public Map<String, Action> ...
