Installing core Content Manager clients
For a basic SDL Tridion installation, install the Content Manager Explorer to manage your content; Template Builder, .NET assembly templating, and Dreamweaver templating to develop templates; and the Experience Manager to edit content.
About this task
- Configuring your browser to allow mixed content
Content Manager Explorer and Experience Manager may fail to display non-secure content if they are themselves secure. The end user can allow the loading of secure content in this mixed-content scenario, but you can also configure the end user's browser to always allow mixed content. SDL does not recommend this as it compromises security for all secure sites with non-secure content. - Setting up the Content Manager Explorer client
Content Manager Explorer is a Web-based Graphical User Interface to the Content Manager Server, used for managing your content. To get Content Manager Explorer up and running on a client machine, check the prerequisites, configure the browser, and configure Content Manager Explorer. - Setting up Template Builder
This section explains how to set up Template Builder on a client machine. Template developers use Template Builder to create, edit and debug Component Templates or Page Templates by combining Template Building Blocks. - Setting up .NET assembly templating
This section explains how to set up .NET assembly templating on a client machine. Use .NET assembly templating to create and upload .NET assemblies that can be used as Template Building Blocks in a Compound Template. - Setting up Dreamweaver templating
In Adobe Dreamweaver, you can create and edit Adobe Dreamweaver Templates (.dwt files) for use in Compound Templates using WebDAV. This section explains how to set up Dreamweaver templating on a client machine by setting up a site that connects to the Content Manager using WebDAV. - Setting up the Experience Manager client
This section explains how to install the Experience Manager client on the Content Manager side. To do so, perform installation and configuration tasks on the Content Manager server. Note that to make Experience Manager work, Experience Manager Server Roles must be installed on the Content Delivery side.