Uploaded image for project: 'Magnolia REST Framework'
  1. Magnolia REST Framework
  2. MGNLREST-796

Delivery API support for headless component inheritance

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Neutral Neutral
    • None
    • None
    • delivery
    • None

      Currently, if a page is inheriting components from a parent, that information is not provided via the Delivery API. To make this work for content authors and the headless FE team, our stop-gap solution is to have a checkbox on each child page to indicate whether it should inherit a specific area from its parent. If yes, then the FE needs to make another API call to the parent area to fetch the desired content on the child page. It's not an ideal workflow, and added support for this would greatly improve the experience for both content editors and developers.

      Ideal state: When making a call to a child page that inherits components from a parent, those components are served through the Delivery API call to the child page.

        Acceptance criteria

              Unassigned Unassigned
              khill Kevin Hill
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: