Should Experience Fragment template sling:resourceType point to "page" or "xfpage" ?

[ArchitAr2]

Hi,
While working on templates for Experience fragment I noticed something -

• In the WKND site, the sample Experience fragment template's sling:resourceType for initial node points to wknd/components/xfpage, whereas the sling:resourceType for structure node points to wknd/components/page
  

• In contrast, in the archetype package the sling:resourceType for both initial and structure node point to ${appId}/components/xfpage.

Could you please provide some insights into why this difference exists and which approach is recommended.

[aanchal-sikka · Accepted solution]

@ArchitAr2 

Please use ${appId}/components/xfpage.

WKND might not be as updated as an archtype

[chaudharynick]

the resourcetype for the XF template should point to xfpage component -example wknd/components/xfpage.

the difference might be due to some incorrect/outdated code in the wknd project. please follow the archetype pattern only that is keeping both nodes resourcetype as <project>/components/xfpage

[Sudheer_Sundalam]

@ArchitAr2 ,

Yes, as other community members stated, it should point to ${project}/components/xfpage. By pointing it to component/page, it may create problems while trying to create variations of a given XF.