You should plan to convert static templates to editable templates. Classic UI is deprecated per official docs.
Static template would work in both Classic/Touch UI in AEM 6.4 but not sure about AEM 6.5 until its formally announced/released. However, per official documentation, you should use Editable templates for any new projects and plan to migrate existing static templates to editable templates and completely switch over to Touch UI (Standard UI).
I agree with you on static template would work in both Classic/Touch UI in AEM 6.4 but not in all cases. for example static template would not work if the component contains any style in it's dialog(for multiple visual variation). we have to go for editable template in order to have style system. Mainly the design is stored in different location.
For static template, design is stored at /etc/designs/<my-site>/jcr:content
For editable template, design is stored at /conf/<your-project>/settings/wcm/policies
The conclusion is, 1. We can not achieve style design with static template in touch UI. 2. Editable template would not support classic UI.(may be because of Classic UI is deprecated per official docs.)
Thanks Scott MacDonald and Arun Patidat for sharing the references.
Created a page with editable template and achieved the style design in touch UI mode, able to see multiple visual variation as well. But the issue is when I open the page in classic mode, I am not seeing anything no parsys, no sidekick and can not edit the component. Is this expected one? Will editable template work only in touch UI mode?
Should we convert my exiting static template into editable template or
Should we keep both static and editable template ?
As per my understanding, at last the page should map anyone one not both of them, cq:template property should either point to editable or static template.
which one to use If we want to support both classic and touch UI. Please suggest.