Content mashup overview
To do a content mashup, you need to perform tasks in both products.
- A shared Taxonomy
- To make it possible for content from both products to appear on the same webpage, you must ensure that SDL Tridion Docs authors can tag their content with Keywords from a Taxonomy in SDL Tridion Sites. The first step toward achieving this goal is deciding which metadata you want to share between the products, and create or reuse a Taxonomy in SDL Tridion Sites to facilitate this sharing.
- A GraphQL client
- The easiest way to create a Public Content API client is to use the one provided with SDL DXA, even if you don't use any other part of that product. The client (a .NET assembly or JAR file, depending on your web site technology) can be used without the rest of DXA.
- A shared visualization
-
Depending on your specific requirements, you may want to make your published SDL Tridion Docs and SDL Tridion Sites content look different, or the same. In the latter case, you may want to, say, make the
<title>of your SDL Tridion Docs DITA topic appear the same as a field containing the title of your SDL Tridion Sites Component. Because the content is fetched in JSON, you can create CSS files and other styling in order to implement this uniformity of style. Here, too, refer to the SDL DXA downloadable for useful CSS files. - Setting up the API
- Doing a content mashup requires that you use the Public Content API; you cannot use the CILs (Content Interaction Libraries). The Public Content API is namespace-aware, so you do not need to configure a namespace in the Content Service; the Public Content API ignores such a configured namespace.