RWS Community

Expand linked ("nested") content in the Public Content API

Alvin Reyes

This idea is asking for the ability to retrieve nested/linked content in the GraphQL-based Public Content API (PCA) for pages or Components that contain Components that link to other Components . Use case The use case is to give developers using the…
- over 2 years ago
- Tridion Ideas
- Tridion Sites Ideas
PCA endpoint for retrieving only "Draft" or "Released" publications

Damian Jewett

One of the desired use cases we've seen is to allow control over which publications of the drafts and released ones to display on the front-end (e.g. display drafts on a staging site and released publications on a production site). We could not find an…
- over 4 years ago
- Tridion Ideas
- Tridion Docs Ideas
Make topic IDs consistent across translated publications

Damian Jewett

In Docs DXA / Public Content API, topics are given different IDs depending on the language selected (/api/<pub-id>/<topic-id>). For instances, the same topic might appear as: EN: /api/123/456 NL: /api/789/012 It would be easier in some scenarios to…
- over 5 years ago
- Tridion Ideas
- Tridion Docs Ideas
Mechanism for converting GUIDs to item IDs and vice versa

Damian Jewett

In some scenarios, it can be difficult or tedious to find an item's GUID given its item ID, or vice versa. For instance, if I am browsing a publication in the Docs DXA website, I can easily get a topic's ID from the URL. But from there, if I want to find…
- over 5 years ago
- Tridion Ideas
- Tridion Docs Ideas

Expand linked ("nested") content in the Public Content API

PCA endpoint for retrieving only "Draft" or "Released" publications

Make topic IDs consistent across translated publications

Mechanism for converting GUIDs to item IDs and vice versa