Component Re-use | Community
Skip to main content
S
Sutty100
Level 4
October 20, 2016
Solved

Component Re-use

  • October 20, 2016
  • 6 replies
  • 2365 views

We have a request from the content authors to make there lives easier by allowing them to create a component once and then simply reference it whereever they want to use it. This would be useful for some marketing banners where they enter things like the heading, subheading, image details, links, tracking ids etc etc. The same banner can be used on multiple category pages in different positions say maybe 10-20 locations.

I was wondering if people have addressed this use case before, I can see Adobe are starting to look at this with content fragments but they are limited to copy at the moment and this is a more complex component. 

    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 edubey

    There is not direct OOTB way to do it, but you can use below method:

    1. Create a separate page Page X where you will author this Component A. (This component will get stored under a node in Page X)

    2. On any page use reference component and select the node component A node of Page X

    When ever you change component A in page X, changes will be reflected everywhere

    6 replies

    smacdonald2008
    smacdonald2008
    Level 10
    October 20, 2016

    We have a request from the content authors to make there lives easier by allowing them to create a component once and then simply reference it whereever they want to use it. 

    All components that you build in AEM are re-useable. You build them as a AEM component developer and place them on the side rail or side kick. An author then drags and drops them on multiple pages. 

    I am not clear what the issue is. 

    V
    Adobe Employee
    vvenkataAdobe Employee
    Adobe Employee
    October 21, 2016

    You can use reference component for this purpose .

    S
    Sutty100Author
    Level 4
    October 21, 2016

    Sorry for not being as clear as I could smiley I meant that they don't want to configure the component every time, simply configure it once e.g. fill in the dialog and then on several pages reference that component so any changes made in the dialog would just be made once and reflected on all pages where that instance of the component is used. 

    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity Manager
    Community Manager
    October 21, 2016

    Hi

    Please refer to this Community Article:- http://blogs.adobe.com/experiencedelivers/experience-management/default-components-in-your-parsys/

    // Make Component part of Template. It is pre-filled template, so when you create a page, it would have pre filled component. So all the pages create by template would have same content. 

    When you make changes to content of template, the changes would get reflected across the pages.

    Reference links:- 

    http://stackoverflow.com/questions/22392147/cq5-preload-a-parsys-with-components

    http://suryakand-shinde.blogspot.in/2015/01/how-to-create-page-with-predefined.html

     

     

    Option 2 could be:- if you want to have it configurable on one page and reuse it everywhere one option would be iparsys, which is an inheriting parsys that traverses up the page hierarchy until it finds a component in it.

    Link:- http://stackoverflow.com/questions/21053131/how-do-we-define-global-properties-in-cq5

     

    I hope this would help you.

     

    Thanks and Regards

    Kautuk Sahni

    Kautuk Sahni
    edubey
    edubeyAccepted solution
    Level 10
    October 21, 2016

    There is not direct OOTB way to do it, but you can use below method:

    1. Create a separate page Page X where you will author this Component A. (This component will get stored under a node in Page X)

    2. On any page use reference component and select the node component A node of Page X

    When ever you change component A in page X, changes will be reflected everywhere

      S
      Sutty100Author
      Level 4
      October 24, 2016

      Thanks for all the replies given us plenty to go on. 

      Terms & ConditionsAccessibility statement

      Loading footer...