Implementing publishing
This section explains the business logic of publishing, as well as how to configure publishing for your organization after you have set up the publishing framework during installation.
- Publishing pipeline and process
Tridion Sites supports flexibility in how you publish content from Content Manager, including the choice of two publishing models that you can use independently or at the same time. - Topology Manager and the publishing infrastructure
Simply put, Topology Manager is the managing part of the publishing infrastructure. Define the publishing infrastructure in Topology Manager so that content published from Content Manager can be delivered to the appropriate location in Content Delivery. - Business Process Types
A Business Process Type is a collection of configuration settings describing how your organization works with its content, both before and during publishing. - Making a Publication publishable
In a recommended BluePrint hierarchy, many Publications are not intended to be publishable. For example, a Publication that contains only Schemas should never be published. But Publications that contain the actual Components and Pages that constitute the contents of a website need to be made publishable. This section explains how. - Transport Service
The Transport Service assembles items to be published (and any dependencies) into a Transport Package, which it then transports from Content Manager to the Content Deployer in the Content Delivery environment. The Transport Service takes the form of a Java microservice running on the Content Manager server. - Enabling templateless, data-only publishing in Content Manager
You can use the templateless, data-only publishing framework to publish content "as is" to Content Delivery, without rendering the content with a template. This leaves the data modeling and rendering to your web development team. To enable templateless, data-only publishing in Content Manager, you need only to ensure certain settings are selected in your schemas and ensure an appropriate Page Template is selected. Optionally, you can configure the recursion depth for link resolving. This topic summarized the settings that impact data publishing specifically. - Implementing the legacy templating framework
This section is relevant only to the legacy, template-based publishing framework. This framework relies on templates to turn Content Manager content into publishable content. As of August 2020 , the template-based publishing framework is considered legacy in favor of templateless, data-only publishing. - Publisher service
The Publisher service performs the publishing of content in Tridion Sites. In Content Manager, either a user or an automated event triggers the publishing of an item. The Publisher offers this item to the Transport Service. - Results of publishing and unpublishing different items
You can publish, republish and unpublish different types of items in Content Manager. For example, you can publish entire Publication, only a certain Page, only a selected Component, a Bundle of different items and other items. It is important to understand the differing results of each publish or unpublish action. - Setting User and Group rights and permissions for publishing
To publish items, a User or User Group needs permissions to publish to one or more Target Types (configured in a Business Process Type) and have Publish to Content Distributor rights for the Publication. For example, the User Group Author may have permission to publish to the Target Type Staging (the staging server) while the User Group Editor has permission to publish to Staging and Live (production server). - Publishing to server clusters
Tridion Sites has an advanced publishing option to use when publishing to a cluster of machines that should be considered as one. If publishing to one machine fails, publishing on all machines can be rolled back in every phase except the post-transaction phase.
Related tasks