Add plugins to Content Fragment MultiEditor Markdown Editor | Community
Skip to main content
M
MadhumithaRamachandran
June 14, 2023
Solved

Add plugins to Content Fragment MultiEditor Markdown Editor

  • June 14, 2023
  • 1 reply
  • 1011 views

We have a business requirement where there's a need to add plugins to Markdown editor within the Multitext (RTE) when used in a content fragment. Could you please confirm if this is possible to achieve in AEM 6.4 or even 6.5 version ? If it is possible then request you to please advise on how can we add custom or even out of box plugins to Markdown editor (see attached screen caps) in a similar way it is available in Rich text editor. 

 

Since business users have a specific need to use only Markdown editor (and not rich text) so request you to kindly share the steps on how this can be done (if possible).

 

Adobe Experience Manager 6.5.14.0

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by lukasz-m

Hi @madhumitharamachandran,

In general editor view you are referring to on your screens is represented by this file /libs/dam/cfm/admin/components/authoring/contenteditor/multieditor/render.jsp

As you can see in the repository, above path is granite:InternalArea so you can't overlay this to add your changes (technically it is possible, but it's against Adobe best practices)

So, to achieve your goal you will have to create your own data type. Here is nicely described example (it is a bit different type of component but it will give you an idea how to write your code):

1 reply

lukasz-m
Community Advisor
lukasz-mCommunity AdvisorAccepted solution
Community Advisor
June 20, 2023

Hi @madhumitharamachandran,

In general editor view you are referring to on your screens is represented by this file /libs/dam/cfm/admin/components/authoring/contenteditor/multieditor/render.jsp

As you can see in the repository, above path is granite:InternalArea so you can't overlay this to add your changes (technically it is possible, but it's against Adobe best practices)

So, to achieve your goal you will have to create your own data type. Here is nicely described example (it is a bit different type of component but it will give you an idea how to write your code):

    Terms & ConditionsAccessibility statement

    Loading footer...