Uploaded image for project: 'Content Editor'
  1. Content Editor
  2. CONTEDIT-124

Move type-mappings and component definitions from article-editor to content-editor

    XMLWordPrintable

Details

    • Task
    • Resolution: Fixed
    • Major
    • 1.0.6
    • 1.0.5
    • None
    • Basel 104, Basel 105
    • 2

    Description

      In the workshop we had realised that type-mapping's are missing if you want to have your own content-editor instance. Article-editor already contains those and those should moved to content-editor ideally.

      Additionally, several components need to be explicitly declared in (sub-)app scope for modules implementing a content editor:

      • info.magnolia.editor.content.blockpicker.BlockTypePicker
      • info.magnolia.editor.content.blockpicker.BlockPickerHelper
      • info.magnolia.editor.content.blockpicker.BlockRegistryContentConnector
      • info.magnolia.editor.content.ContentDefinition

      This is a unfortunate because those types are quite generic and most of the times, standard implementations from content-editor will be used, leading to unnecessary boilerplate configuration.

      After properly defining those components in content-editor, the corresponding entries in article-editor and stories-app can be dropped.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                pmundt Philip Mundt
                ilgun Ilgun Ilgun
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Task DoR