Development processesAdded by IBM | Edited by IBM on January 8, 2014 | Version 12 (Show original)
|In addition to being a package of ready-to-use templates, Content Template Catalog also embodies a new pattern for site development based around page templates and microsites.
While Content Template Catalog may often only be used during the initial build phase of a site, it could also be used as the basis for a self-serve templating infrastructure. In this kind of environment, you need a development process for building templates.
For the Content Template Catalog software developers, what made this possible was the Portal Solution Installer. It allowed the developers to deploy applications, themes, pages, portlets, and content assets from a single package. This became the basis for the source control and build process.
Using source control and buildingParent topic: Deploying sites built with Content Template Catalog
The source control for Content Template Catalog contains all the code artifacts (plug-ins, text providers, context providers, JSPs), portal artifacts (theme and layout files, exports of pages, page templates, and portlets), and IBM
® Web Content Manager artifacts (exported libraries).
Testing and deploying
A copy of the production content libraries would be installed in test environments, and then used as test data during a development project. This allows a thorough testing of the deployment of the full package of changes, including IBM
Web Content Manager assets, before deploying to the production environment.
Multilingual design content
To support multiple languages for the users of your website, it is necessary to use the Multilingual Solution. This requires separate CTC Content libraries for each language in your site.