[MGNLGQL-18] Investigation: Provision a GraphQL API for Page content Created: 13/May/20  Updated: 26/Jan/21  Resolved: 26/Jan/21

Status: Closed
Project: Magnolia GraphQL
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Canh Nguyen
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 5d
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Documentation update required:
Yes
Date of First Response:
Epic Link: GraphQL Phase 1
Sprint: HL & LD 20
Story Points: 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.)

 



 Comments   
Comment by Simon Lutz [ 17/Jun/20 ]
  • Complex cases needs to be tested - had problems with getting /travel page
  • Content of pages is highly dynamic, components are returned using special syntax (three dots)
  • AC needs to be verified
Comment by Canh Nguyen [ 26/Jan/21 ]

Please see the investigation on this page https://wiki.magnolia-cms.com/x/xRkTDg

Generated at Mon Feb 12 05:51:45 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.