migrate to EXPERIENCE FRAGMENT STRUCTURE COMPONENT to SITE STRUCTURE COMPONENT

[#1]

Hi all,

i'm facing a challenge to migrate to EXPERIENCE FRAGMENT STRUCTURE COMPONENT to SITE STRUCTURE COMPONENT.

kindly anyone guide me

[karthick1356 · Accepted solution]

Hi @karthick1356,

XF page is created using editable template created out of page component that is inheriting from /libs/cq/experience-fragments/components/xfpage

Site pages are created using editable template created out of page component that is inheriting from core v2 page - core/wcm/components/page/v2/page

If you are trying to include created XF pages as part of site pages, make use of Experience Fragment from General Component Group (has option to include the created XF variation)

Please do let know if you are looking for any specific information in particular.

[karthick1356 · Accepted solution]

Vijayalakshmi_S, there was a page rendering component created for XF Template. my requirement is if can reuse that page rendering component while creating editable template for Site. if so, how to do that?

[Vijayalakshmi_S · Accepted solution]

In terms of usage, it is not a restriction as long as your requirement for your site page is met with XF page rendering component itself.(Inspect the html files as part of your xf page rendering component, if it meets the definition of your site page - use the same. Otherwise, per adobe recommendation, it is to make use of Core Page component for site pages.)

To answer how to do that - it is same as any editable template creation steps - create editable template-type (with desired page rendering component) -> create editable template -> Allow the template path in the desired hierarchy

[#5]

Hi @karthick1356 ,

In we retail demo site we have one demo structure component at /apps/weretail/components/structure/xfpage path so if you want to create the xf editable template, it will be better to copy it from the we retail and paste it in your project path and then do the necessary change as per your requirement like adding client libs, adding extra config pages an all.

Then you need to create a template type in your project's conf path and then create editable template based on the created template type.

Now you are all set to create xf by allowing template path in the /content/experience-fragments/..... path then you can go ahead with that.

Use above created xf with experience fragment core component on page or wherever you want.

Hope this will help.

Umesh Thakur

[karthick1356]

Hi @karthick1356,

Experience Fragments are fully laid out content; a fragment of a web page. So it contains components inside it. If I understand your query correctly, you are wanting to use the components that are used inside the XF as separate site structure components.

To do that, go to the XF path, Ex: /content/experience-fragments/project/XF-name, check the list of components added there. Select the component that you are looking for and get its sling:resourceType --> path and use it elsewhere.

Hope this helps. If not please elaborate on your query.

Thanks,

Kiran Vedantam.

[karthick1356]

Hi KiranVedantam1992, i was trying to migrate page rendering component from component/structure/nameOfComponent. this page rendering component is created for XF. the challenge here i need migrate this page rendering component to site rending componet so that i can create template using that and also page from that template.

[KiranVedantam1992]

So here is your issue as per my understanding. You have a page rendering component, and you want to use it to be added to the template, am I right? What is the issue that you are facing? Are you not able to see the component in the template to add? If yes, check if the page rendering component is in the .hidden group. If it is not the case, check the template policies and add the component in the "allowed components" list. These steps should ideally solve your issue. Thanks, Kiran Vedantam.

[karthick1356]

Hi KiranVedantam1992, i only have page rendering component for experience fragment. i need to create page rendering component site.