How to show intended content in child pages from parent page

[sreenivasula]

Hello All,

            We have a below site structure

                Parent Page--

                           --- Child 1 Page

                          ---- Child 2 Page

Parent page has a parsys component, where author drag and drops components and author the content and tag them using tags (e.g cq:tags) (e.g one component is intended for Child 1 page only( Child 1 page also has certain tags in it (cq:tags) ) and another component for Child 2 page only and few components for both the child pages).

So once author completes authoring and publishes the page parent page, when some one access the child 1 page, it should display only content intended for child1. Similarly if child 2 page is accessed, content intended for child 2 only should be shown. And the components which are intended for both  child pages should display in both the pages.

Could you please let us know how to achieve the above requirement and best practice.

Regards

[stevec2515680]

I am not sure this is support in AEM out of the box. That is - child pages rendering content based on parent page content.  Look like this may have to be a custom solution. 

[sreenivasula]

Thank you Steve for your quick reply. Could you please suggest the best custom approach we can use for this implementation ?

Regards

[leeasling]

I'm pretty sure you can achieve this by switching your parsys to be an iparsys - that will inherit the content down to the child pages, then on the pages you don't want a component, remove it, and the pages you do, keep it.  

[kautuk_sahni · Accepted solution]

Hi 

Agreeing with Lee.

Please read this community article covering Parsys Vs iParsys.

Link:- http://myadobecq.blogspot.in/2014/01/parsys-vs-iparsys.html

//

Paragraph System (parsys)

        The paragraph system (parsys) is a compound component that allows authors to add components of different types to a page and contains all other paragraph components. Each paragraph type is         represented as a component. The paragraph system itself is also a component, which contains the other paragraph components.

        You configure which components users see by making them available to the user in Design mode.

        For example, the content of a product page may contain the following:
        An image of the product (in the form of an image or textimage paragraph)
        The product description (as a text paragraph)
        A table with technical data (as a table paragraph)
        A form users fill out (as a forms begin, forms element, and forms end paragraph)

Inheritance Paragraph System (iparsys)

    The inherited paragraph system is a paragraph system that also allows you to inherit the created paragraphs from the parent. You add paragraphs to iparsys at for example, /content/geometrixx/en/products     and as result, all the subpages of products that also have iparsys with the same name inherit the created paragraphs from the parent. On each level, you can add more paragraphs, which are then inherited by     the children pages. You can also cancel paragraph inheritance at a level at any time.

    Simply, iparsys is a parsys that inherits it's content from the ancestor pages. 

I hope this will help you.

Thanks and Regards

Kautuk Sahni