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

DOC: Content Management API

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Neutral
    • None
    • None
    • None
    • None
    • HL & LD 34
    • 2

    Description

      DOCU-2179 refactored the REST docs, including the names of the APIs, turning the Nodes API into a legacy API. This is a bit misleading. 

       Nodes API ... is the one and only API for managing content.

      This PR (https://git.magnolia-cms.com/projects/DOCUMENTATION/repos/product-docs/pull-requests/547/overview) fixed this partially, but we need to make sure that the association of "legacy" with the Nodes API doesn't occur elsewhere in the docs. Instead, 

      We need to position this as our Content management API. ... 

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                mdrapela Martin Drápela
                mdrapela Martin Drápela
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Task DoR