Implementing Content Delivery
Content Delivery provides modules for getting content out of the Content Manager and on to the Presentation Server and APIs for implementing dynamic website functionality.
- Microservice memory footprints and heap sizes
The various Content Delivery microservices have default Java heap size settings preconfigured in their startup scripts. The actual maximum heap size needed by your microservices depends on the loads placed on them. - Versions of microservices (Content Interaction Services)
By default, any code you write that interacts with the Content Delivery microservices, also called Content Interaction Services (CIS), is assumed to work with any version of the microservices. But both in Java and in .NET, you can use annotations to specify exactly which version(s) of the CIS your code will work with. - Configuring logging for a Content Delivery software component
This task applies if you run Content Delivery software components in a Java/JSP web application. You already set up logging when you installed your Content Delivery software components. But you can configure logging in more detail by editing thelogback.xml, the configuration file for the Logback logging framework used by Content Delivery. - Websites based on Tridion Sites
Content Delivery receives publishable content from the Content Manager and serves it out to the presentation environment. This section explains the data models used in Content Manager and Content Delivery, and the basics of creating a dynamic website under the template-based publishing framework. - Content Deployer extensions
When a user publishes content, the Content Deployer unpacks the incoming Transport Package and processes its transport instructions. You can extend the default behavior of the Content Deployer by creating a custom Module and adding it to a Step, or by extending an existing Module. - Managing website code (TCDL)
RWS recommends that you manage your website code using Tridion Sites. When you use and create tags in a technology-neutral language called TCDL, Content Delivery can transform them into your website's language (actual code) at various stages of the delivery process. - Dynamic Link Resolving
You can create links to Components, Multimedia Components or Pages. On the published Web site, the links become links between published Web pages. You can configure how Content Delivery handles dead links, ambiguous links, and links to Components that were published but not embedded on a Page. - Navigation
You can implement website navigation in a Tridion Sites-based website using the organization of Structure Groups in the Content Manager, or you can use a taxonomy tree (Categories and Keywords) to create more sophisticated navigation (intelligent navigation). - Implementing Content Delivery search
After installing the Content Delivery search feature, you can set up indexing in detail, and use the Public Content API to execute queries on Elasticsearch. - Extension points in the .NET Content Interaction Libraries
Various interfaces in the .NET CIL enable you to override various default implementations. You can use Microsoft Unity to inject any new dependencies you create. - Content Delivery Public Content API
Content Delivery exposes its content through the Public Content API, in the GraphQL query language. To interact with the API and the published content, use an in-browser GraphQL IDE such as GraphiQL. - Content Service
The Content Delivery Content Service, or Content Service for short, is the web service that delivers content from the Content Delivery environment to the presentation environment. It can also be used for integration with affiliate websites. - Reference section
This section contains reference information for Content Delivery.