Getting started with AEM universal Editor for markdown and XML files | Community
Skip to main content
J
JohnBr26
Level 2
December 10, 2024
Solved

Getting started with AEM universal Editor for markdown and XML files

  • December 10, 2024
  • 3 replies
  • 1678 views

Planning to do POC for Markdown and XML files using AEM's new Universal Editor .

 

  1. Will it be a good option to move markdown and XML file to AEM ?
  2. Can someone help me with step by step guide to setup it on local for POC purpose ?
    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 daniel-strmecki

    Hi @johnbr26,

    check out this demo from Adobe: https://www.aem.live/, you can get a demo EDS site with Word documents deployed in 30 mns.

     

    Good luck,

    Daniel

    3 replies

    daniel-strmecki
    Community Advisor and Adobe Champion
    daniel-strmeckiCommunity Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    December 10, 2024

    Hi @johnbr26,

    you can find the instructions to set up Universal Editor (UE) locally here: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/universal-editor/developer-overview

    UE enables WYSIWYG editing experience for any type of front-end. It is usually used for editing HTML pages/AEM Sites. I am not sure what is your use case to edit markdown/XML files and if UE is the right approach. Maybe you can share a bit more details on what you are trying to achieve.

     

    Good luck,

    Daniel

      J
      JohnBr26Author
      Level 2
      December 10, 2024

      We have existing document in Markdown format and XML and final output would be  AEM Sites . What would be  then best route for us to follow ?
       

      daniel-strmecki
      Community Advisor and Adobe Champion
      daniel-strmeckiCommunity Advisor and Adobe Champion
      Community Advisor and Adobe Champion
      December 10, 2024

      Hi @johnbr26,

      that depends on how you want to store your content in the new setup to ensure maintainability, scalability, and ease of use. Typically, AEM stores content in the JCR database. Another alternative is to use Word/Excel documents with EDS. These two options are fully supported by the new Universal Editor. In case you want to store your content in a different format, that is possible but probably more effort.

      I know too little about your project to give you a concrete recommendation. It makes a big difference if you are building a complex enterprise multi-site or a small, short-lived campaign website. Personally, I think to make the best use of AEM, you could migrate your content fully to JCR. To make the site editable you need to build the HTML/JS components anyway, so why store them in a non-standard format?

       

      Good luck,

      Daniel

        Raja_Reddy
        Community Advisor
        Raja_ReddyCommunity Advisor
        Community Advisor
        December 10, 2024

        Hi @johnbr26 

        Authoring page content via components in a global manner has always been a central feature of AEM. This user experience is known today as the Page Editor. This is in contrast to other such experiences within the AEM UI like how you edit content fragments as an example. With AEM as a Cloud Service, the Page Editor is still alive and well but Adobe has begun to move AEM from a monolithic, centralized architecture to a composable, decentralized one. Perhaps one of the first updates to this end was with the aforementioned content fragment experience. The Content Fragment Console is different from other user interfaces in AEM in that it is not a granite-based app comprised of nodes and properties in AEM itself but rather a consumable service built via the Adobe App Builder and then framed. This stated simply is the idea behind composable architecture: allow customers to compose their own experiences based on consumable services/components/etc.

        Adobe has introduced a new editing experience for content called the Universal Editor. At the time of this writing, it doesn't yet have full feature parity with the Page Editor but it's rapidly improving by the day. Whereas the traditional Page Editor can only work with nodes and properties in AEM's JCR repository.

        • AEM Page Structures - Nested cq:Components of cq:Pages, including Experience Fragments
        • AEM Content Fragments - Edit content from Content Fragments as they appear in-context of the experience. Please refer the below article

        https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/universal-editor/getting-started#request-access 

          J
          JohnBr26Author
          Level 2
          December 13, 2024

          Thankyou @daniel-strmecki  and @raja_reddy  for response .

          I believe the best approach is to either convert to a word document and use EDS or convert to DITA and use AEM Guides.
          Could someone provide more details on using word files with EDS, or share any demo recording  where word files are utilised in EDS?

          daniel-strmecki
          Community Advisor and Adobe Champion
          daniel-strmeckiCommunity Advisor and Adobe ChampionAccepted solution
          Community Advisor and Adobe Champion
          December 13, 2024

          Hi @johnbr26,

          check out this demo from Adobe: https://www.aem.live/, you can get a demo EDS site with Word documents deployed in 30 mns.

           

          Good luck,

          Daniel

            kautuk_sahni
            Community Manager
            kautuk_sahniCommunity Manager
            Community Manager
            December 16, 2024

            @johnbr26 Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!

            Kautuk Sahni
            Terms & ConditionsAccessibility statement

            Loading footer...