In version R5.3 Tridion has introduced Modular/Compound Templating, which offers (more) separation between layout and business logic. It also allows the implementation of Template Building Blocks (TBBs) with C# and/or .NET assemblies. A Template Building Block used with Modular/Compound Templating is (normally) responsible for one major task. For example: Converting XML to HTML, Publish all… Read More »
Tridion has two main methods for publishing information to websites: Publishing chunks of content to the Tridion broker Publishing whole pages to the file system. Both publishing strategies have already been explained in previous posts. However the fundamental differences between both strategies deserves some additional attention. Publishing chunks of content (dynamic) In tridion chunks of… Read More »
Tridion uses a transactional publishing architecture which enables it to publish content to different websites or channels. To publish your content to a website or channel you specify a publish transaction which includes the publishing target and a date (and some advanced options). The publish transaction will then be placed in the publishing queue where… Read More »
A component link is a reference within the content, or meta data of a component (A), to another component(B). The link in component A is a reference based on the unique ID from component B. On the presentation server this reference will be translated to the URL where the rendered content from component B can… Read More »
Tridion folders are used to store components and subfolders and are similar to directories (or folders on windows) on a file system. A folder can also contain metadata which can be used to describe the content of the folder. Permissions for different users or user groups can be set per folder. It is good practice… Read More »
Tridion publications contain the building blocks used in Tridion blue printing. A Tridion Publication contains ONE of the following website parts: Nothing. Also known as the “Empty Master” has no parents and can never be given a parent. Placed to ensure that in the future the publications below it can be given new parents. Data… Read More »
A Tridion page corresponds with a physical page (HTML/ASP/JSP/XML/CSS etc) on a website. The type and layout of the page are defined by the Page Template that is used on the page. A page is also a container for Component Presentations. It is possible to add 0 or more Component Presentations (chunks of rendered content)… Read More »
The Page Template (PT) defines the overall layout of a page. It is in fact a master page which defines the header, footer and navigation on a particular page type. It also defines where Component Presentations are placed on the page. The picture belows shows what is defined in the Page Template In addition it… Read More »
A Component Presentation (CP) is a rendered chunk of a component(content). The rendering is done by a Component Template. A component Presentation is either used as part of a fully rendered Page(see page 2) or it is published to the broker DB (see below). Using different Component Templates you can create different Component presentations from… Read More »
A Component Template or CT is a small program which is used to render (parts of) components based on specified schema’s. In other words programs which create chunks of XHTML. In Tridion parlance these chunks are called Component Presentations. It is possible to use different CT’s to render the same content. An example might be… Read More »