Can we use static template created using slingResourceSuperType: cq/cloudserviceconfigs/templates/configpage in AEMaaCS ? | Community
Skip to main content
S
sangrampatil111
Level 3
March 17, 2023
Solved

Can we use static template created using slingResourceSuperType: cq/cloudserviceconfigs/templates/configpage in AEMaaCS ?

  • March 17, 2023
  • 1 reply
  • 561 views

We have static template under /apps/my-project/customcloudservice/templates which is used for AWS cloud configuration. 

 

In BPA(Best Practice Analyzer), it is saying that 

Legacy static templates were detected. They should be modernized.

Can we migrate this template directly to AEMaaCS without changing it to Editable ? 

Please suggest.

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 lukasz-m

Hi @sangrampatil111,

According to official documentation static templates are still supported, with some limitations.

So answering your question, if you are fine with above, yes you can keep your static templates. Of course according to best practices it will be good to plan to fully migrate to editable templates in the end, but it is not a show stopper to move into AEM as a Cloud Service. In terms of configuration use case, I think that instead of editable templates you could consider to use Context-Aware Configuration:

1 reply

lukasz-m
Community Advisor
lukasz-mCommunity AdvisorAccepted solution
Community Advisor
March 18, 2023

Hi @sangrampatil111,

According to official documentation static templates are still supported, with some limitations.

So answering your question, if you are fine with above, yes you can keep your static templates. Of course according to best practices it will be good to plan to fully migrate to editable templates in the end, but it is not a show stopper to move into AEM as a Cloud Service. In terms of configuration use case, I think that instead of editable templates you could consider to use Context-Aware Configuration:

    Terms & ConditionsAccessibility statement

    Loading footer...