Affects Version/s: None
Fix Version/s: None
Component/s: Headless CMS
When having several templates, and those being large ones, the JSON generated can be huge.
In order to minimize that, and taking into account that customers will require 1 rendered content at a time, it is better to create a new resource where the renderedContent is stored.
The consumer of this API will be able to:
- Check the list of rendered content associated with a structuredContent
- Retrieve the rendered content for a given template
The list should contain only the elements the user has permission to view. If a structured content is requested and the current user doesn't have permission to view it, a 404 error should be returned.
The API should support at least Plain JSON, JSON-LD and HAL as output formats.
The consumer developer should be able to control which linked resources are embedded so that they can be retrieved along with a structured content in a single request.
The consumer developer can specify which fields are desired, to reduce the data transfer when the API is used from a consumer sensitive to it.
Given a structure like structure.json
and a template associated with it (not attached as it is not accessible through the api, but any will work, it is not the goal of this issue)
and a structured content created using this structure
When the structuredContent is retrieved
Then the response is like JSONExample.json
-renderedContent: html with the template applied to the structuredContent
-templateName: name of the template used.