Details
-
Story
-
Resolution: Done
-
Neutral
-
None
-
None
-
None
-
-
Empty show more show less
-
Yes
-
HL & LD 20
-
5
Description
User story:
As a developer I want to provision a GraphQL API for the content in magnolia Pages app, so that other systems (including frontends) can use the content.
Notes:
Page content is more complicated then content type content:
- Each page template can be thought of as a content type.
- Each component template can be thought of as a content type.
- Pages can have children
- Components and Pages can have children
Acceptance criteria:
- Developer can provision API using light development
- It should not require a lot of additional configuration due to reasonable default behaviour.
- The system gets the model information it needs from the existing template dialog definitions.
- API should return the properties specified in the model (there is an implicit model in the dialog of a template).
- API should respect the relations sepecified in the content types and be able to handle queries that request the referenced content. (There are implicit relations in the 'link fields' in the dialog of a template.)
Checklists
Acceptance criteria