Hi MuthuKumar,Sorry if the word older version hurts you, by older
version i mean from aem 6.3 we are no longer using static template that
you have used in your example that you are showing this is out dated.
Now adobe recommends to use editable templates as it provide more
flexibility to content authors for designing the template. Also as per
vision of adobe slowly they are moving every thing from /etc to /conf
and /content so going forward /etc/* will be deprecated also what i
Hi, Well said by scott, could you please provide more clarity on your
question. Like are you using editable templates for restricting
components using policy, if yes then its configuration is stored under
/conf not /etc/design. Which means you might be using any older version
of aem and using static templates. Please correct me if i am wrong.
Needed below information from your side:-1) How you have created the
component (like using core components or foundation components).2) What
Adobe is recommending its customers to create AEM project structure
using Lazybones instead of traditional Maven archetype 10. As when we
create a aem project using Maven archetype it is not easy to customize,
it provides lots of sample content and packages like test, launcher.
Which might not be required for your project, on contrary lazybones
bones is very interactive , flexible and easy to customize according to
your project need. Adobe consulting Services (ACS) provides a aem multi