Modular Templating Running demo. Process Flow. The demo will follow these steps: The Web master changes a template for the Web site The designer changes the design of the template The developer creates new functionality The Web master adds the new functionality to the template
The running demo will only take 4 minutes
The Web master want to change a template so opens it with Template Builder.
He finds it consists of three different modules. Template Builder.
He runs the template to see how it will look on the Web site.
Template Builder prompts him to select the page he wants to test this template with.
The modular template is executed on the server. Template Builder shows its progress…
He chooses to view the result in a bigger screen. Builder shows its progress…
And allows the Web master to view the result.
Since he is not very satisfied with the visual design, he will ask the Designer to change the design module.
The Designer uses will ask the Designer to change the design module.Dreamweaver to change the design module. She can use all standard Dreamweaver functionality, and needs no specific knowledge of SDL Tridion R5 templates.
The Designer can open and check out the template directly from R5.
She makes the desired changes… will ask the Designer to change the design module.
…and saves these back to R5. She notifies the Web master who can now review the changes.
The Web master runs the template again within who can now review the changes.Template Builder…
… and views the result in a bigger screen in order to see the changes
The Developer can use any .NET language to write the functionality. In this case, he uses C#, and he can easily write code using IntelliSense.
In the mean time, the team’s Developer is creating new functionality using Visual Studio.NET. In this case, he builds a bread crumb trail.
Using remote debugging, the Developer can execute the code on the server while doing his debugging work within Visual Studio. While he debugs the code, other users can continue to work on the server.
To start the debugging process, he runs the template from Template Builder, and uses breakpoints to bring him to the right part of his code inside Visual Studio.
After building his .NET assembly, the assembly and its associated classes are automatically saved in R5 so they can be used.
The new functionality now appears in Template Builder, and can be dragged onto the template
The Web master runs the template again but sees that the bread crumb has not been added to the page yet…
However, he sees that the bread crumb has not been added to the page yet…BreadCrumb assembly itself gives a correct result. He therefore asks the Designer to add the BreadCrumb to the design module.
The Designer uses bread crumb has not been added to the page yet…Dreamweaver to add a simple tag to the design, and saves it.
The Web master runs the template again… bread crumb has not been added to the page yet…
…and sees the bread crumb is now displayed correctly.
He is now happy with the design and starts using he template for the Web site!
As a next step, he needs to modify the design for Switzerland, that uses a separate brand.
To achieve this, he only needs to localize the design module of the modular template. After doing this, he asks the Designer to apply the local brand.
The Designer opens the localized design module, and changes it to match the local brand.
The changes include a new logo and a different it to match the local brand.color scheme.
All functionality in the modular template works correctly. If the Developer decides to change for example the bread crumb functionality, the Swiss template will automatically pick up those changes, since only the design module was changed.