SDL Receives Top Score Among All Vendors in Experience Management Category According to Independent Research Firm.
April 9, 2013
The SDL Tridion community has grown over the past years and this is certainly noticable through the amount of bloggers which on a regular basis write articles about SDL Tridion.
The SDL Tridion MVP Award program is a program developed to thank and recognize all the great professionals that freely share their knowledge, real world experience and objective feedback to help others implement and enhance our technology. An MVP award is given to those who offer exceptional contributions to the SDL Tridion community. You can nominate candidates at any time during the entire year.
The SDL Tridion MVPs for 2012 had a great time during their retreat, and we thought we should share these moments with the whole community.
The first meeting held at Indivirtual NL Headquarters on Wednesday, November 28th, 2012 for the SDL Tridion Benelux User Group was a great success.
Responsive design is a technique to make your existing web site suitable for a broader range of devices by having it respond to the media it is displayed on. This article looks at how we made SDL Tridion World better looking on mobile devices by employing responsive design techniques.
The focus of this document is to discuss the delivery aspect of SDL Tridion, specifically to deploying content to portals. First, we will outline general integration principles around the Web Services that is true for all Portal deployments. We will then outline three portal deployment scenarios, discuss the pros and cons of each, and address typical portal integration concerns. Ultimately, the decision as to which is best will be based on specific business needs of the customer.
In this tutorial we will cover all the steps you must follow to create a deployer extension using Eclipse. We will create a "Custom Module" and will configure Eclipse from scratch to develop, test and debug our code.
With the release of Tridion 2011, SDL has incorporated OData support into its API's for the display layer via web services. By doing this Tridion allows developers to talk to the content broker and retrieve data for consumption within their own code.
This guide will walk you through setting up, and using OData for your first time to connect to Tridion
This document describes a process to move Content Manager changes between various different Tridion systems (Typically named DTAP, or Development, Test, Acceptance and Production)
In this series of articles, a unified way of working with the Compound Templating Framework is presented. Part one started with Dreamweaver Template Building Blocks, this part is a continuation of part one and describes Custom Functions for Dreamweaver TBBs. The other parts cover C# fragment Building Blocks and .NET assembly Building Blocks.
The Dreamweaver integration for Modular Templating enables you to rapidly upload HTML designs into SDL Tridion and publish them onto your website. However there are some common stumbling blocks related to how 2nd level dependencies are managed (for example the relationship between CSS and images), and the structure of the published files on your website. This article outlines these issues and illustrates a simple approach to overcome them.
This tutorial shows how to configure an extension for the SDL Tridion 2011 GUI from start to finish.
The SDL Tridion Object Cache is an in-memory cache that stores frequently used objects from the Content Data Store. The cache keeps objects available to applications for repeated usage. This prevents SDL Tridion Content Delivery from having to retrieve objects from the Content Data Store for each request. Typically caching includes linking information, metadata and component presentations. The Object Cache is designed to significantly improve the performance of your Web sites and is available to every Content Delivery module. SDL Tridion recommends implementing it in every production environment.
The SDL Tridion uses two and possibly three different databases. The SDL Tridion Content Manager Database (called Tridion_cm by default) that is used to store all Tridion content, the SDL Tridion Logging Database (called Tridion_cm_log by default) which holds all error and warning messages that the Content Manager server logs and the SDL Tridion Content Delivery Database (called Tridion_broker by default) which stores all dynamic content and metadata information that is available for the Content Broker, Dynamic Linking, Dynamic Content Delivery and Personalization and Profiling on the Presentation Servers.