Should Experience Fragment template sling:resourceType point to "page" or "xfpage" ? | Community
Skip to main content
A
ArchitAr2
Level 2
February 10, 2025
Solved

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

  • February 10, 2025
  • 3 replies
  • 558 views

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.

Best answer by aanchal-sikka

@architar2 

 

Please use ${appId}/components/xfpage.

WKND might not be as updated as an archtype

3 replies

aanchal-sikka
Community Advisor
aanchal-sikkaCommunity AdvisorAccepted solution
Community Advisor
February 10, 2025

@architar2 

 

Please use ${appId}/components/xfpage.

WKND might not be as updated as an archtype

Aanchal Sikka
    chaudharynick
    chaudharynick
    Level 4
    February 10, 2025

    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
      Community Advisor
      Sudheer_SundalamCommunity Advisor
      Community Advisor
      February 11, 2025

      @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.

        Terms & ConditionsAccessibility statement

        Loading footer...